aliases not working in em0

[Steve Bertrand]

Steve Bertrand wrote:
> Patrick M. Hausen wrote:
>> Hello,
>>
>> On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote:
>>
>>> ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0"
>>> ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255"
>> I don't know if this can be the cause of your problem, but
>> the /32 netmask for aliases has been deprecated quite a while
>> ago.
> 
> For how long? On a 7.0-R box, it works ok with a /32 prefix len:
> 
> %ifconfig
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
>         ether 00:0f:b5:80:53:85
>         inet 208.70.104.210 netmask 0xffffff00 broadcast 255.255.255.192
>         inet 208.70.104.211 netmask 0xffffff00 broadcast 255.255.255.255
>         inet6 2607:f118::b6 prefixlen 64
>         inet6 2607:f118::b7 prefixlen 64
>         media: Ethernet autoselect (1000baseTX <full-duplex>)
>         status: active
> 
> %ping 208.70.104.211
> PING 208.70.104.211 (208.70.104.211): 56 data bytes
> 64 bytes from 208.70.104.211: icmp_seq=0 ttl=64 time=0.079 ms
> ^C
> 
> I'll try it on one of my 7.1 boxes to see if I can reproduce the OP's issue.

Interestingly enough, it does work here:

vm# uname -a
FreeBSD ww3.eagle.ca 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan  1
14:37:25 UTC 2009
root at logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

vm# ifconfig le0
le0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 00:0c:29:31:e7:11
        inet6 fe80::20c:29ff:fe31:e711%le0 prefixlen 64 scopeid 0x1
        inet 208.70.104.27 netmask 0xffffff80 broadcast 208.70.104.127
        inet 208.70.104.29 netmask 0xffffffff broadcast 208.70.104.29

...and from another box:

pearl# ping 208.70.104.29
PING 208.70.104.29 (208.70.104.29): 56 data bytes
64 bytes from 208.70.104.29: icmp_seq=0 ttl=63 time=1.275 ms
^C

Wendell, what does #netstat -rn say? Also, if you run tcpdump listening
on the alias IP address, do you see the ingress traffic from the remote
workstations? ie:

# tcpdump -n -i em0 host 192.168.112.181

Steve