Hi all,

I stumbled on this while trying to track down an mbuf leak on a new server.

It seems that routed corrupts the arp table on FreeBSD 6.2 when
there are more than one ip alias on an interface. The behaviour differs
depending on whether routed is enable in rc.d or manually started after
boot. 

How to repeat:
configure multiple aliases on an interface
if routed is not enabled in rc.d
ping all aliases
arp -a shows that each alias has the nics mac
eg
lnat.ips.gov.au (192.168.1.100) at 00:30:1b:ba:bb:01 on bge0 [permanent]
knat.ips.gov.au (192.168.1.101) at 00:30:1b:ba:bb:01 on bge0 [permanent]

run routed and wait a few seconds
run arp -a again, the mac address for all aliases (except the last)
will have changed to a 0 or 128 hex numbers seperated by :'s
eg
lnat.ips.gov.au (192.168.1.100) at 0 [permanent]
knat.ips.gov.au (192.168.1.101) at 00:30:1b:ba:bb:01 on bge0 [permanent]

All aliases are still pingable
A netstat -r shows something like the following for the aliases

192.168.1.100   192.168.1.100   UHLW    1       30      lo0 =>
192.168.1.100/32 link#1         UC      0       0       bge0
192.168.1.101   00:30:1b:ba:bb:01 UHLW  1       16      lo0 =>
192.168.1.101/32 link#1         UC      0       0       bge0

If routed is enabled in rc.d and the system rebooted only the last
alias shows with arp -a . 

A netstat -r shows something like the following for the aliases

192.168.1.100   192.168.1.100   UH      1       30      bge0 =>
192.168.1.100/32 link#1         UC      0       0       bge0
192.168.1.101   00:30:1b:ba:bb:01 UHLW  1       16      lo0 =>
192.168.1.101/32 link#1         UC      0       0       bge0

Only the primary ip and the last alias are pingable.

I have tried this on several machines running 6.2- stable with similar results.

Can anyone confirm this behaviour.

Cheers
Colin
-- 

--
Colin Yuile ([EMAIL PROTECTED])





_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to