Re: ifconfig_lo0_alias0 does not work any more on 9-CURRENT - solved

[ Available lists | Index of freebsd-current | Month of Dec 2009 | Week of 9 Dec 2009 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Vladislav V. Prodan <universite@ukr.net>
Date
9 Dec 2009 20:16:17
Subject
Re: ifconfig_lo0_alias0 does not work any more on 9-CURRENT - solved
Message-ID
4B200584.7050506@ukr.net


[ Hide this part ]
Vladimir Grebenschikov writes:
> Hi

> Looks like now it is required to add 'inet ' prefix to ifconfig lines,
> for os <= 8.0 it was not required, although

> corrected line:
> ifconfig_lo0_alias0="inet 127.0.0.2/32"

And I on the contrary
not work:
ifconfig_re0="inet 10.0.0.1 netmask 255.255.255.0"
work:
ifconfig_re0_alias0="inet 192.168.0.1 netmask 255.255.255.0"




>> After upgrade RELENG_8 -> 9-CURRENT following line in rc.con does not
>> work any more for me. (after boot no alias address on loop-back
>> interface).

>> ifconfig_lo0_alias0="127.0.0.2/32"

>> console output while is usual, without errors, but does not shows
>> required address:

>> ---
>> Starting Network: lo0 em0.
>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>> options=3<RXCSUM,TXCSUM>
>> inet 127.0.0.1 netmask 0xff000000
>> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>> options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
>> ether 00:15:58:82:36:1a
>> media: Ethernet autoselect
>> status: no carrier
>> ---

>> Any ideas what the reason of such behaviour ?







Elapsed time: 0.155 seconds