On Mon, Jan 04, 2016 at 09:35:04AM -0700, Darren S. wrote: > I have a router on the end of a 802.1q trunk port that I'd like to > netboot for install, but this is only possible if I can PXE boot using > the correct VLAN to reach the PXE server. Some PXE boot ROMs support > this (mine does not currently) and I was going to try it from a booted > bsd.rd on the host, but looks like I only have options for physical > interfaces to select from on an Autoinstall:
Try IPXE rom, iirc it does support vlan, even trunk/bond. > Welcome to the OpenBSD/amd64 5.8 installation program. > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a > Available network interfaces are: re0 re1 re2 athn0. > Which network interface should be used for the initial DHCP request? > (or 'done') [re0] > DHCPDISCOVER on re0 - interval 3 > DHCPDISCOVER on re0 - interval 5 > DHCPDISCOVER on re0 - interval 13 > DHCPDISCOVER on re0 - interval 19 > DHCPDISCOVER on re0 - interval 13 > DHCPDISCOVER on re0 - interval 8 > No acceptable DHCPOFFERS received. > No working leases in persistent database - sleeping. > Could not determine next-server. > Could not determine auto mode. > Response file location? > > With additional work I may be able to switch around network > configurations to support a native VLAN (and then reconfigure > post-install) but this isn't ideal. Is it feasible for the autoinstall > support to handle the same VLAN features for booting as is available > later in the installation for network configuration? IIUC install has no way to know you want to use tagged vlan. You need to dedicate separate iface for booting or use custom install script inside ramdisk. I would redesign your network to have dedicated port based vlan for netbooting... j.
