On a completely unrelated note, there are known problems trying to tag and utilize vlan1 (and present it to a BSD system). Google "seklecki openbsd vlan".
It has to do with vlan 1 being the base vlan on trunk lines. It sucks big time -- especially since Dell managed switched dont let you change the default administrative VLAN. But after many moons, I was able migrate my administrative VLANs & subnet to a VLAN other than 1 ~BAS On Wed, 2007-10-17 at 16:59 +0200, Frans Haarman wrote: > Hello, > > Several times I have noticed my vlan not getting an IP when I use > vlan 1 vlandev bge0 10.3.3.1 255.255.255.252 10.3.3.3 > > It works everytime when I use: > vlan 1 vlandev bge0 > 10.3.3.1 255.255.255.252 10.3.3.3 > > It seems the interface must be created first before the assining IP can be > done ? > This makes sense to me! I think it might be worth mentioning in > hostname.ifman page! > > > > > > > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
