On Apr 20, 2012, at 5:12 PM, Nikos Vassiliadis wrote:
> This is not the correct syntax. From the rc.conf manual page:
Thanks Nikos. Not sure how I came up with the incorrect syntax, but correcting
that fixed my issue.
-Chad___
freebsd-questions@fr
On 4/20/2012 9:54 PM, Chad M Stewart wrote:
cloned_interfaces="vlan4 vlan7"
ifconfig_vlan4="inet 192.168.4.21 netmask 255.255.255.0 vlan 4 vlandev em0"
ifconfig_vlan7="inet 192.168.7.21 netmask 255.255.255.0 vlan 7 vlandev em0"
ifconfig_vlan7="alias 192.168.7.31 netmask 255.255.255.255"
ifconfig_
Those errors are usually from it trying to create interfaces that already
exist. It looks like it created your default route, though. Time to file a
PR because the network boot stuff is not doing the order right.
___
freebsd-questions@freebsd.org mai
On Apr 20, 2012, at 3:00 PM, Mark Felder wrote:
> On Fri, 20 Apr 2012 14:54:46 -0500, Chad M Stewart wrote:
>
>> Anyone have some suggestions how I can fix this?
>
>
> I'm guessing having the default route on a tagged vlan was not tested and the
> default route is attempted before the vlan i
On Fri, 20 Apr 2012 14:54:46 -0500, Chad M Stewart wrote:
Anyone have some suggestions how I can fix this?
I'm guessing having the default route on a tagged vlan was not tested and
the default route is attempted before the vlan interface is all the way
up. After the system is booted up d
I can't figure out why on boot the default route is not being setup correctly.
I'm coming back to FreeBSD, having spent many years using OpenBSD primarily.
The server has 2 NICs, of which em0 is the one being used. I did see
something during boot about not adding the default route but it sc
