Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Dial-up - IMPOSSIBLE!
- To: tlug@example.com
- Subject: Re: tlug: Dial-up - IMPOSSIBLE!
- From: karlmax@example.com (Karl-Max Wagner)
- Date: Sun, 4 Oct 1998 21:02:04 +0000 (GMT)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: <Pine.LNX.3.95.981004121543.8896A-100000@example.com> from "Marc E. Christensen" at Oct 4, 98 12:17:10 pm
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
> Once a dial-up connection is established, from home, I can ping, slogin, > telnet, FTP etc. from the dial-up client to the dial-up server. I cannot, > however, make a connection to any other machine (local or otherwise). > Upon looking at the logs of a machine on the local subnet of the server > diring a ping or other type of connection, I see ICMP redirect requests > coming from the gateway of the subnet. It's as if the packets go out from > the client, through the dial-up server yet the server does not respond to > anything destined for the dial-up client. Very neat observation :-). That's your problem. Gonna explain: if a packet destined for one of your dial-up ports floats along the ethernet to which your dial-up server is connected, the dial-up server should grab it off the net and hand it over to the respective dial-up port. That's what you need but what's not happening at the moment. In order to get that working you have to use proxyARP. In order to do so you have to add additional entries into your kernel routing table. You do this with the following command: arp -s <IP-addr_of_dialup_port> <eth?_HWaddre> pub The HWaddr is the hardware address of your ethernet interface linking you to your LAN ( the stuff you get behind HWaddr when doing an ifconfig ). The other parameter is the IP address of your dial-up port. The pub neans "publish". It MUST be there. It says that the dial-up port IP addresses, and not only, the machine's own address, are linked to the hardware address of the ethernet port. In that way the packets for your dial-up ports are grabbed off the ethernet by means of the HWaddress, and, once inside the gateway machine, are routed to the respective dial-up port ( it is, of course, necessary to provide the proper routes with appropriate "route add .... gw ...." commands. However, this seems to have been done ). That should do it. ================================================================ "It was hell. They knew it. Karl-Max Wagner But they called it karlmax@example.com W-I-N-D-O-Z-E" ================================================================ --------------------------------------------------------------- Next Meeting: 10 October, 12:30 Tokyo Station Yaesu central gate Featuring the IMASY Eng. Team on "IPv6 - The Next Generation IP" Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691 --------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- Re: tlug: Dial-up - IMPOSSIBLE!
- From: Scott Stone <sstone@example.com>
- Re: tlug: Dial-up - IMPOSSIBLE!
- From: "Marc E. Christensen" <marc@example.com>
- References:
- tlug: Dial-up - IMPOSSIBLE!
- From: "Marc E. Christensen" <marc@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: Dial-up - IMPOSSIBLE!
- Next by Date: Re: tlug: Grep for subdirectories?
- Prev by thread: tlug: Dial-up - IMPOSSIBLE!
- Next by thread: Re: tlug: Dial-up - IMPOSSIBLE!
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links