I wrote: > The ping just hangs and does nothing. I haven't timed how long it > hangs, but I know it hangs for more than a minute. > > So, I'm getting further, but I still can't get through to the internet > yet...
Some more info...I did an "ip route" on my working March image and the non-working new image. ======================== Old (working) route*: 192.168.1.1 dev eth1 scope link 123.45.67.90 dev eth0 scope link 123.45.67.88/29 dev eth0 proto kernel scope link src 123.45.67.90 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.1 127.0.0.0/8 dev lo scope link default via 123.45.67.89 dev eth0 New (non-working) route*: 123.45.67.88 dev eth0 scope link 123.45.67.90 dev eth0 scope link 192.168.1.0 dev eth1 scope link 192.168.1.1 dev eth1 scope link 192.0.0.0/8 dev eth1 proto kernel scope link src 192.168.1.1 127.0.0.0/8 dev lo scope link 192.0.0.0/3 dev eth0 proto kernel scope link src 123.45.67.90 Default via 123.45.67.89 dev eth0 ======================== Ipmask also appears to be returning a different number than my working image was setup with. When I do an "ip addr" on my working image, I get eth0 with inet 123.45.67.90/29. On the non-working image, I get eth0 with inet 123.45.67.90/3. I haven't done any custom tweaking of my routing path. This is the route that the network script laid out with each image. It's also the only thing keeping me from using the latest development image of Oxygen, so any help would be *greatly* appreciated! :) Thanks! - Sean T. *IPs changed to protect the innocent _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
