Date: Wed, 2 Jul 2008 15:46:45 -0400 From: Ross <westr@connection.ca> To: Vince Hoffman <jhary@unsane.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re[2]: FB7.0 - ifconfig clone error - "SIOCIFCREATE2: Invalid argument" Message-ID: <658785581.20080702154645@connection.ca> In-Reply-To: <486BD80A.2000902@unsane.co.uk> References: <19710256683.20080702131816@connection.ca> <486BD80A.2000902@unsane.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
VH> what command are you using exactly? it certainly works here.
The standard ones! Which has gotten me confused greatly.
Using yours as an example:
-=
[root@controller ~]# ifconfig bce0.5 create
ifconfig: SIOCIFCREATE2: Invalid argument
[root@controller ~]#
and playing a bit:
[root@controller ~]# ifconfig bce0.5 create vlandev bce0
ifconfig: must specify a tag for vlan create
[root@controller ~]# ifconfig bce0.5 create vlandev bce0 vlan 5
ifconfig: SIOCIFCREATE2: Invalid argument
[root@controller ~]# ifconfig bce0
bce0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
ether 00:1e:0b:c7:e1:d0
inet w.x.y.z netmask 0xffffff00 broadcast w.x.y.z
media: Ethernet autoselect (1000baseSX <full-duplex>)
status: active
[root@controller ~]#
-=
I'm wondering if it's because of the bce driver or something along
those lines, and ioctl isn't able to pick up the root device or
something.
The annoying part is that these are new servers/network cards on these
boxes, so I don't have an equivalent FB6.x setup to test against.
(Other boxes running 6.x are working just fine).
R.
--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?658785581.20080702154645>