so I am officially stumped by this. heres the setup
I believe the distro is slackware (as i had to restart network services with /etc/rc.d/rc.inet1). anyways, two nics on the linux box.
eth0->192.168.117.50/24
eth1->30.0.0.50/24
only have 2 hosts, one for each network and the hosts connect to separate switches that in turn connect to the linux box.
the only routes on the linux box are the default ones for the interfaces and i turned on ipv4 forwarding with sysctl -w net.ipv4.ip_forward=1.
why i'm stumped is because of the output from the pings. pinging from eth0 to eth1 and vice versa yields destination unreachables. pings from the hosts to their gateway(either eth0 or eth1) are successful but the host in the 30.0.0.0 network can ping through the 30.0.0.50 interface and get a reply from the 192.168.117.50 interface, but thats as far as it can ping (can not ping the host in the 192.168.117.0 network) while the 192.168.117.50 interface get destination unreachable when initiating a ping from it to the host on the 30.0.0.0 network. the host in the 192.168.117.0 network can only ping the gateway (192.168.117.50).
these ping results are just strange and are driving me crazy as to wtf is going on.
I believe the distro is slackware (as i had to restart network services with /etc/rc.d/rc.inet1). anyways, two nics on the linux box.
eth0->192.168.117.50/24
eth1->30.0.0.50/24
only have 2 hosts, one for each network and the hosts connect to separate switches that in turn connect to the linux box.
the only routes on the linux box are the default ones for the interfaces and i turned on ipv4 forwarding with sysctl -w net.ipv4.ip_forward=1.
why i'm stumped is because of the output from the pings. pinging from eth0 to eth1 and vice versa yields destination unreachables. pings from the hosts to their gateway(either eth0 or eth1) are successful but the host in the 30.0.0.0 network can ping through the 30.0.0.50 interface and get a reply from the 192.168.117.50 interface, but thats as far as it can ping (can not ping the host in the 192.168.117.0 network) while the 192.168.117.50 interface get destination unreachable when initiating a ping from it to the host on the 30.0.0.0 network. the host in the 192.168.117.0 network can only ping the gateway (192.168.117.50).
these ping results are just strange and are driving me crazy as to wtf is going on.
sounds like the interfaces could be physically plugged into the wrong networks.
i think you might be right. correct me if i'm wrong but should eth0 normally be the onboard nic? if that is the case then yes, the interfaces would be plugged into the wrong networks.
i'll have to give this a shot in the morning. *crosses fingers*
i'll have to give this a shot in the morning. *crosses fingers*
welp that wasn't it.
also found out that the firewalls on my new xp hosts were the reason behind the linux box being unable to ping them.
i think the problem is the nic on the 192.168.117.0 network on the linux box. get no lights on it 90% of the time. ifconfig shows a fair amount of collisions (510). so i think that nic is shot. the box has another nic, but i can't seem to get that to work either :(
also found out that the firewalls on my new xp hosts were the reason behind the linux box being unable to ping them.
i think the problem is the nic on the 192.168.117.0 network on the linux box. get no lights on it 90% of the time. ifconfig shows a fair amount of collisions (510). so i think that nic is shot. the box has another nic, but i can't seem to get that to work either :(
i deserve to be hit smacked in the face. it was the firewalls all along. i finally got the nic i thought to be dead, to work and BAM! everything worked fine.
i hate myself sometimes.
i hate myself sometimes.