On Tuesday 28 February 2006 05:30, Harry Putnam wrote: > It all cleared up after a reboot. I didn't mention I made a domain > name switch preceding the reported problem too. I suspect my > nameserver cache hadn't had time to clear up (I have pretty long Time > To Live values set). Although I really don't now if that would be an > issue. That's great! Too bad you didn't get to the bottom of it, but fixed is better than broken.
> ip route > 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.2 > 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.4 > 127.0.0.0/8 dev lo scope link > default via 192.168.0.20 dev eth0 This is proper. Only one gateway and it's through the eth0 device. > arp -a > fw.local.lan (192.168.0.20) at 00:09:5B:01:2F:E4 [ether] on eth0 > fwobsd.local.lan (192.168.0.19) at 00:10:B5:91:85:88 [ether] on eth0 It's interesting here that you don't see anything on 192.168.1.0/24. Perhaps nothing is connected to that interface right now? Congrats on the problem being fixed. -- Zac Slade [EMAIL PROTECTED] ICQ:1415282 YM:krakrjak AIM:ttyp99 -- gentoo-user@gentoo.org mailing list
