DHCP VLAN - strange networking behavior

[Harlem]

I'm just setting up my very first FreeNAS and struggling to setup my network:

I want interface igb3 connected to some VLANs and setup a switchport as trunk with tagged 10, 20 and 80. I want to set the IP addresses manually:

vlan10: 191.168.11.91
vlan20: 191.168.12.91
vlan80: 191.168.17.91

So I setup three vlans with parent igb3, un-checked DHCP and the addresses above, confirmed and ....

1) the console shows only a (unwanted) DHCP address for the parent interface igb3
2) all vlans disappered from the console
3) but funny enough: the vlans are existent in ifconfig and I can login under that addresses, and ...
4) every VLAN got an extra DHCP-address although I have unchecked DHCP

Has anybody an idea whats going wrong here?

 

[Elliot Dierksen]

What is the IP address you got from DHCP? Is it in the untagged VLAN, and what is the untagged VLAN for your switch port?

 

[Harlem]

What is the IP address you got from DHCP? Is it in the untagged VLAN, and what is the untagged VLAN for your switch port?

Depends on:

At first, I've tried a trunk with untagged VLAN 1, tagged 10, 20, 80, DHCP off. I've got in every VLAN (1, 10, 20, 80) my defined IP address and a free DHCP address in the DHCP-Range 192.168.xx.100 - 150.

Second, I've tried for testing purposes a general port with tagged 10, 20, 80, where 10 set PVID. I've configured an empty parent interface, DHCP off with a VLAN vlan80 DHCP off, as well. Similar results: The console shows after confirming the parent interface with DHCP ON, IP Adress in DHCP space (192.168.10.105) and NO VLAN. But ifconfig shows vlan80 with two addresses: The given address and a DHCP address:

Code:

igb3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: Management
        options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether ac:1f:6b:98:38:27
        hwaddr ac:1f:6b:98:38:27
        inet 192.168.10.105 netmask 0xffffff00 broadcast 192.168.10.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
vlan80: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: HAB
        options=600303<RXCSUM,TXCSUM,TSO4,TSO6,RXCSUM_IPV6,TXCSUM_IPV6>
        ether ac:1f:6b:98:38:27
        inet 192.168.17.91 netmask 0xffffff00 broadcast 192.168.17.255
        inet 192.168.17.108 netmask 0xffffff00 broadcast 192.168.17.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        vlan: 80 vlanpcp: 0 parent interface: igb3
        groups: vlan

 

[Elliot Dierksen]

The parent interface is going to be whatever VLAN is untagged for that trunk. That means it should be a VLAN that you want to use. I don't know that there is any way you could not use the parent interface. Here is my network config.

lagg1 is an LACP LAG (of i350 interfaces). The parent lagg1 is the untagged vlan, and the vlan1 interface is tagged for VLAN 1. I think you would have to do something similar to that.

 

[Harlem]

I see what you mean, but I think, that something in my configuration goes totally wrong. I've suspended my efforts to implement a vlan on igb3 in order to get my primary port igb2 up and running with a fixed IP address. That fails too: After confirming DHCP=no with a fixed IP Address the system comes back with two IP Addresses: The given one and a DHCP address, too. And DHCP is marked ON again. Grrng...

 

[Harlem]

@Elliot Dierksen: Thank you for your help. Problem solved.
I setup'd the NICs again on the console with DHCP off and fixed IP address. Then I could setup the VLANs in the web GUI. Everything works fine, after reboot too.