/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting!
/* ALSO: Don't quote this header. It makes you look lame :-) */
Floore Timothy E DLPC wrote:
> I've been a happy IP-masq user for almost 2 years now. Well, until 2 days
> ago. My linux box died, hardware problem. Either the scsi card or the
> harddrive, not completely sure which.
>
> The masq box was an old 486 VLBus/ISA system I had, and I happened to have
> another one shoved in a corner. Same basic setup, 486dx2/66, 16MB ram, 500MB
> hd (this one ide, not scsi), and a cdrom conencted to a soundblaster card
> instead of a scsi cdrom. I moved the ethernet cards form the old box to the
> new one, both nics are identical NE2000 clone cards, ISA interface, 10mbit.
>
> I got linux (RedHat v5.2, kernel 2.0.36, same as I had on the old box. Yes,
> I should probably grab the 2.0.38 sources and upgrade.) installed on the box
> with no problems. It recognizes both cards, shows them in 'ifconfig'.
>
> eth0 is given an IP address by dhcp from my cablemodem isp, and it is
> getting its IP address correctly. Didn't even have to call the isp since I
> was using the same nic, they didn't have to change a MAC address in their
> dhcp server. I can get to the outside world, browse the internet, all that
> stuff from the linux box.
>
> eth1 is 192.168.0.1 and is connected to the internal house network. This is
> where my problem is. I can ping 192.168.0.1 (the linux box IP) from the
> linux box, but cannot ping any other machines on the internal house lan, for
> example "ping 192.168.0.10" gives 100% packet loss. The green light on the
> back of the nic is lit, just like eth0, and the light on the hub is also
> lit, like all the other nics. Other machines on the house lan can (still)
> ping each other, but cannot ping the linux box, get a timeout trying. The
> other machines in the house are all win98 or win98se boxes.
>
> I thought I'd had a difficulty related to this the last time I set up a
> linux masq box (April 1999, about 20 months ago, I don't remember much and
> didn't take notes.. oops) so I recompiled the kernel with the ne2000 driver
> built-in, rather than as a loadable module. Installed the kernel, and put
> append = "ether=10,0x300,eth0 ether=5,0x280,eth1"
> in the lilo.conf before running lilo to install the kernel. The kernel
> detects both cards on bootup (seems to detect them earlier in the boot
> process than with the driver as a loadable module), and still does dhcp on
> eth0 correctly. Other than detecting the card, it seems to ignore eth1 on
> bootup, which seems right for a manual-config static-IP nic.
>
> I am guessing here that I have a routing problem.
>
> >From the tests in the IP Masq HOWTO, I pass 5.1 with the windows box pinging
> itself. I pass 5.2 with the linux box pinging itself. I pass 5.3 with the
> linux box pinging the outside world. DNS even works.
>
> I stop at "5.4 Testing local PC to Linux connectivity" I checked the things
> mentioned in "If this fails" and none of those seem to be my problem. Green
> light on the back of the linux box nic, green light on the back of the masq
> client machine, green light on the hub, and the masq clients can ping each
> other. I didn't check the client config, because I didn't change it from
> before the old linux masq server died, and set up the new linux box with the
> same internal IP, 192.168.0.1, so they should still point to it as the
> gateway.
>
> My route table shows this:
> Destination Gateway Netmask Flag Use Interface
> 24.214.x.129 0.0.0.0 255.255.255.255 UH 2 eth0
> 192.168.0.1 0.0.0.0 255.255.255.255 UH 0 eth1
> 24.214.x.128 0.0.0.0 255.255.255.128 U 1 eth0
> 192.168.0.0 0.0.0.0 255.255.255.0 U 3 eth1
> 120.0.0.0 0.0.0.0 255.0.0.0 U 2 lo
> 0.0.0.0 24.214.x.129 0.0.0.0 UG 4 eth0
>
> I added the host entry for 192.168.0.1 myself with "route add -host
> 192.168.0.1 eth1" thinking that it might have needed that. Didn't help.
>
> I've been reading through the NET HOWTO, do I need to do something like
> this?
> route add -net 192.168.0.0 netmask 255.255.255.0 eth1
> It looks like there is already a line there for that, the 4th line in the
> route table above.
>
> I'm kind of guessing I'm missing somethign that will seem simple in
> hindsight. Anyone want to point out things to check?
it looks ok. have you tried running tcpdump when you try the ping to
see what happens. it might tell you something useful. also use traceroute.
raf
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ --
THIS INCLUDES UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
