Date: Sat, 25 Nov 2000 16:06:23 +0200 From: Tim Priebe <tim@polytechnic.edu.na> To: Troy Settle <troy@psknet.com> Cc: tim@iafrica.com.na, "Jean M. Vandette" <vandj@securenet.net>, freebsd-isp@freebsd.org Subject: Re: Vlan device in FreeBSD 4.2 Message-ID: <3A1FC75F.9BD2D15C@polytechnic.edu.na> References: <GIEHKBHPBGKJPNMBCOHFIEACCAAA.troy@psknet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Troy Settle wrote: > > Would you also call it a bug when your box hangs at boot because you have > /usr/local before /usr in /etc/fstab ? I would call it a bug if it caused a kernel panic. It does not, it behaves properly, by telling you the problem, and asking you what shell you want to run, so you can fix it. > Vlan is akin to a sub interface. You gotta bring up the parent before you > bring up the child. Perhaps ifconfig could have code added to it to check > this and spit out an error message: "hey idiot, you gotta configure the real > interface before the virtual one." > > -Troy At least as recently as 4.0-RELEASE it behaved in a reasonable manner. It configured the "sub interface" without any panic. The vlan in question was not usable, untill the parent interface was brought up. This caused me a little confusion the first time I tried it, but it was much less of a problem than the kernel panics on more recent systems. Better than an "hey idiot" message would be for ifconfig to check if the parent interface is up before bringing up the child, and if not bring it up. This would eliminate the kernel panic, as well as ensuring the vlan works after it is configured. Tim. > ** -----Original Message----- > ** From: owner-freebsd-isp@FreeBSD.ORG > ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Tim Priebe > ** Sent: Wednesday, November 22, 2000 6:18 AM > ** To: Jean M. Vandette > ** Cc: freebsd-isp@freebsd.org > ** Subject: Re: Vlan device in FreeBSD 4.2 > ** > ** > ** It seems someone has introduced a bug to ifconfig, if you do not > ** configure the adapeter before you configure the vlan device, you get a > ** panic. Work around configure the device before you configure the vlan > ** device. > ** > ** Tim. > ** > ** "Jean M. Vandette" wrote: > ** > > ** > Greetings all, > ** > > ** > I've been trying to get Vlan's to work on 4.2 and would like to know > ** > if anyone has gotten this to work and if so how? > ** > > ** > A short setup lesson would be greatly appreciated I've been trying > ** > to get the Vlan's working for a while and still have not succeeded. > ** > Yes I have read the ifconfig man page but still seem to be missing > ** > something, I get a kernel panic 12 whenever I try to bring up the vlan. > ** > > ** > Any help from someone who has got this working would be of great help. > ** > > ** > Thank you in advance > ** > > ** > Jean M. Vandette > ** > > ** > To Unsubscribe: send mail to majordomo@FreeBSD.org > ** > with "unsubscribe freebsd-isp" in the body of the message > ** > ** > ** To Unsubscribe: send mail to majordomo@FreeBSD.org > ** with "unsubscribe freebsd-isp" in the body of the message > ** > ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A1FC75F.9BD2D15C>