Thanks for your feedback. I agree that separating the networks and isolating the build network thus eliminating the need for VLAN tagging is the ideal scenario. Unfortunately, influencing those changes are beyond my sphere of influence in this particular case.
At the end of the day, our solution was to replace pxeboot.bs with Grub2pxe. I have a blog post detailing the scenario at https://hostileadmin.wordpress.com/2012/05/04/pxe-booting-into-a-freebsd-installation/ On Wed, Mar 14, 2012 at 9:30 AM, Erik Nørgaard <norga...@locolomo.org> wrote: > Hi > > > On 14/03/2012 11:44, Rick Miller wrote: >> >> I thought I would follow up on this as a couple individuals expressed >> an interest in it... >> >> We have isolated the configuration in which this occurs under. It >> occurs during the execution of pxeboot.bs on brocade switches with >> vlan tagging enabled. > > > You might save yourself time and money buying a cheap switch and doing your > jumpstart install on a separate closed network completely isolated from the > rest of your networks, without VLAN tagging required. > > If you have lots of nodes to install it makes sense to maintain your own > repository of freebsd and packages, and it's good practice to keep your > preproduction systems separate from production, so there is no need for > network access. > > > BR, Erik > > -- > M: +34 666 334 818 > T: +34 915 211 157 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Take care Rick Miller _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
