Date: Fri, 09 Dec 2011 11:10:53 +0100 From: Johan Hendriks <joh.hendriks@gmail.com> To: Brett Glass <brett@lariat.net>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Two problems still present in RC3 Message-ID: <4EE1DEAD.2040108@gmail.com> In-Reply-To: <201112090913.CAA03333@lariat.net> References: <201112090913.CAA03333@lariat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Brett Glass schreef:
> The interfaces SEEM to be configured correctly, but the messages --
> which must be coming from scripts called by /etc/netstart -- are
> troubling.
Same thing happens with lagg0
If i use this config, after a reboot all is fine
ifconfig_em0="up"
ifconfig_em1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport em0 laggport em1 192.168.100.1/24"
After a /etc/netstart, i get the following:
ifconfig: create: bad value.
devd already running? (pid=1767).
Setting hostuuid: 9abf4e13-9a77-b31d-9a77-b31d9fbfee13.
Setting hostid: 0xf505f6a8.
ifconfig: create: bad value
ifconfig: SIOCSLAGGPORT: Device busy
Starting Network: lo0 em0 em1 bge0 pflog0 pfsync0 lagg0.
<snip>
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC>
ether 00:1b:21:d4:77:fb
inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255
inet6 fe80::21b:21ff:fed4:77fb%lagg0 prefixlen 64 scopeid 0xf
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
laggproto lacp
laggport: em1 flags=0<>
laggport: em0 flags=0<>
add net default: gateway 192.168.1.254
To get rid off the bad value notice, i need the following in /etc/rc.conf
comment cloned_interfaces and add create to ifconfig.
ifconfig_em0="up"
ifconfig_em1="up"
#cloned_interfaces="lagg0"
ifconfig_lagg0="create laggproto lacp laggport em0 laggport em1
192.168.100.1/24"
This way no error, but i do not know if the lagg interface works that way!
I got some issues with the setting the ipaddress and so on, i do not
remeber it exactly! it happend last week.
The machine was a production machine, and can not be offline for too long.
So i changed things back to the first config and rebooted the machine.
That way everything is fine.
But /etc/netstart does not works for the lagg0 interface.
regards,
Johan Hendriks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EE1DEAD.2040108>