#853 closed defect (fixed)
pure vlan interface not brought up
| Reported by: | jgreco | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Backend | Version: | 8.0.1-RC2 |
| Keywords: | Cc: |
Description
In 8r8022:
Short summary: a parent interface used only for vlans is not correctly provisioned. Any interface that has vlan interfaces as children needs to be configured as "up" by the OS.
Longer description:
Bringing up a new FreeNAS on an HP N36L with only one ethernet.
From the console, added vlan interfaces with bge0 as parent.
Configured switching environment to make port tagged.
Deleted the DHCP-provided IPv4 config for bge0.
Added default route.
Upon reboot, bge0 was not in "UP" state. This rendered both vlan interfaces unusable. An "ifconfig bge0 up" fixed this.
The default route was also not installed. I would have thought that that would have been installed since the vlan interface it pointed to was up, but I haven't investigated further. It is showing in the web GUI as the configured IPv4 default interface.
Change History (3)
comment:1 Changed 20 months ago by jpaetzel
comment:2 Changed 20 months ago by delphij
- Resolution set to fixed
- Status changed from new to closed
Resolved as r8045.
comment:3 Changed 20 months ago by jgreco
Wicked fast turnaround guys. Keep up the great work.
This is fallout from handling tagged and untagged traffic. We are fixing it now. As a workaround, you can create the parent interface as an unconfigured interface (no DHCP, no ip config) and it will be issued the ifconfig up at boot.
We are fixing the system to do this automagically.