> Eugene Sevinian wrote: > > > > On Tue, 20 May 1997, Jens B. Jorgensen wrote: > > > > > I think the difficulty is on the Win95 end at this > > > point. When you bring up the connection from the Win95 end can you > > > ping the IP of the Linux box (the IP for the dialup)? > > > > > > > Ping to linux machine's IP gives reasonable results. The same with > > w95 pseudo IP address. However ping doesn't see any other machines in LAN. > > The result is: > > > > Request timing out. > > Request timing out. > > Request timing out. > > > > It seems DNS is not guilty at all. I also run winipcfg which proved that > > w95 recognized this stuff corectly. > > > > Ok, here's a question. Did you recompile your kernel or anything? > If you did recompile, did you enable IP forwarding? I ask because > it looks like the problem is that packets aren't getting past your > linux box. Since you can ping the linux side, the link is just > fine. If you have the same kernel which came with the dist. then > I *think* it has IP forwarding enabled (I'm not sure about this, > since I didn't compile that kernel myself). You may be able to > discover if it's enabled by looking at some /proc/?? file, but I'm > not too sure. Anyone else have a thought?
I think if /proc/net/ip_forward exists, then it's enabled in the kernel. cat this file on my router shows: root# cat /proc/net/ip_forward IP firewall forward rules, default 4 IP forwarding is enabled on my machine (and it's a router for my LAN) so if your output is similar, then you should be enabled too. An easy way to check what's happening with IP traffic is "tcpdump". This is an optional package which you will have to install separately if you haven't already done so. On the Linux box, run "tcpdump -i eth0" on one screen and "tcpdump -i ppp0" on another. Then, run a continuous ping from a client (your Win95 box) and see what happens on each screen. A big problem I once had that I first thought was forwarding was actually a routing problem. (I wasn't using IP_Masq.) ICMP (Pings) were coming in on eth0 and going out on the ppp0, but nothing was coming back. My ISP didn't have a route back to my client (which they said _was_ configured! I proved them wrong).... (Note - this shouldn't be your problem *if* you're using IP_Masq. Later, Kevin Traas Systems Analyst Edmondson Roper CA http://www.eroper.bc.ca -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .