On the ifconfig, they are different (eth0 is 255.255.0.0, and eht1 is 255.255.255.0). I don't know how to change this from the netstat....
You will probably need to change this on your DHCP setup on your DSL router that eth0 gts its address from.
Baiscly, the netmash tells the ethernet interface what range of addresses a network can support, so when eth0 comes up with a netmash of 255.255.0.0 it actually puts itself int eh same network as eth1, which it's not really and so the linux box gets terribly confused about what interface it should send its packets out of.
If you change the netmask of the DSL router to 255.255.255.0 then you are seperating out the networks such that
eth0 - belongs to network 192.168.0.0 - 192.168.0.255 eth1 - belongs to network 192.168.1.0 - 192.168.1.255
currently you have
eth0 - belongs to network 192.168.0.0 - 192.168.255.255 eth1 - belongs to network 192.168.1.0 - 192.168.1.255
and as you can see in the second instance the address space overlaps (which is a big no-no)
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
this is a network that is used as an IPv4 auto-config last resport network, that is, if there is no static ip assigned to the interface and it cant find a DHCP server to gain an IP, it will allocate an IP out of this range. generally if a machine gets an IP in this range there is "something wrong" or the interface is simply not configured.
Don't even know where the 168.254.0.0 is coming from....that's not anywhere near the class of either my cable or dsl connection.
As above, this is not a bad thing, just a side effect of setting the interface to DHCP and not getting an IP from the DHCP server. (it probably adds it by default)
That did it. Thank you!
-- By-Tor.com It's all about the Rush http://www.by-tor.com
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
