em device on 4.x: ifconfig alias issue

Marc G. Fournier scrappy at hub.org
Sat Mar 25 04:42:41 UTC 2006


'k, I thought I had this licked, but apparently I'm still missign 
something ...

When I alias a new IP onto an em device running on a 4-STABLE server (I'm 
in the process of moving to 6.x, haven't gotten to this server yet), for 
some reason, it isn't seeing appropriate 'arp' messages, so the upstream 
switches and such aren't getting the information ....

All the local server can ping the IP, but, for instance, the Cisco 2950 
that all the servers are plugged into can't:

#ping 200.46.208.96

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 200.46.208.96, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

but, the another IP on the server does ping:

#ping 200.46.204.172

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 200.46.204.172, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms


I've tried 'arp -s' on the server where the IP *was* running on, but that 
isn't working, altho ping'ng from any of the servers does work:

# ping 200.46.208.96
PING 200.46.208.96 (200.46.208.96): 56 data bytes
64 bytes from 200.46.208.96: icmp_seq=0 ttl=64 time=0.507 ms
64 bytes from 200.46.208.96: icmp_seq=1 ttl=64 time=0.217 ms
64 bytes from 200.46.208.96: icmp_seq=2 ttl=64 time=0.229 ms
^C
--- 200.46.208.96 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.217/0.318/0.507/0.134 ms

Is there something else that I can do on the FreeBSD side to get this to 
work? :(  Some way of forcing the appropriate arp packets to be sent out 
... ?



----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664


More information about the freebsd-questions mailing list