sotiris.bos
Explorer
- Joined
- Jun 12, 2018
- Messages
- 56
Hello, I am going nuts over this.
FreeNAS 11.2
I have a VLAN set as an interface for FreeNAS. I can access the UI from the VLAN IP and performing traceroute from my computer I can see that it is going through the router (instead of directly connecting like on the LAN) so no problems with the network and VLAN situation.
I am trying to set up a jail that will use the VLAN (vlan200) instead of the LAN.
I have created a new bridge called bridge2 and I have added the VLAN interface to the bridge.
I am using VNET.
I have set up an interface for the jail as follows: vnet0:bridge2
I tried using DHCP (DHCP server is running on the VLAN at 10.0.11.1/24) but the jail cannot reach the router at 10.0.11.1 or any other addresses apart from the FreeNAS VLAN IP.
I tried setting a static IP at 10.0.11.251/24 (is outside the DHCP range) and setting the default router to 10.0.11.1. Jail still can only reach 10.0.11.241 which is the IP of the FreeNAS VLAN interface through the bridge. Cannot reach any other addresses, including 10.0.11.1. I tried it with IPV4 Interface of vlan200, vnet0, bce0.
allow raw sockets is on,
vnet_default_interface under Network Properties was set to either none or vlan200, didn't make a difference.
Can't ping or traceroute anything other than 10.0.11.241 (FreeNAS VLAN IP).
Funny thing is I had it working before but I think that the bridge (bridge2) also included bce0 (default LAN interface) which defeats the purpose of the VLAN.
Help
Edit: Here is the tcpdump for dhcp ran on the router:
Here is the same tcpdump for dhcp ran on the freenas box for bridge2 interface:
Edit.2: Works fine on LAN with bce0 being a DHCP Interface. Does not work on VLAN (vlan200)because it has a statically assigned IP. Does the "DHCP"option on the UI under "Interfaces" actually mean that you can only use one interface for DHCP requests for jails as well, not only for the FreeNAS box itself?
Edit.3:
After setting the bce0 (LAN) interface as static and vlan200 interface as DHCP, here are the tcpdumps for DHCP on both the router and the FreeNAS box. Tried it multiple times, seems like the first DHCP offer makes it through to the bridge2 interface while the next ones don't.
Router:
FreeNAS:
Edit.4: DHCP option seems irrelevant. I have the same behavior as Edit.3 even with vlan200 Interface as static with no DHCP option ticked after a reboot.
FreeNAS 11.2
I have a VLAN set as an interface for FreeNAS. I can access the UI from the VLAN IP and performing traceroute from my computer I can see that it is going through the router (instead of directly connecting like on the LAN) so no problems with the network and VLAN situation.
I am trying to set up a jail that will use the VLAN (vlan200) instead of the LAN.
I have created a new bridge called bridge2 and I have added the VLAN interface to the bridge.
I am using VNET.
I have set up an interface for the jail as follows: vnet0:bridge2
I tried using DHCP (DHCP server is running on the VLAN at 10.0.11.1/24) but the jail cannot reach the router at 10.0.11.1 or any other addresses apart from the FreeNAS VLAN IP.
I tried setting a static IP at 10.0.11.251/24 (is outside the DHCP range) and setting the default router to 10.0.11.1. Jail still can only reach 10.0.11.241 which is the IP of the FreeNAS VLAN interface through the bridge. Cannot reach any other addresses, including 10.0.11.1. I tried it with IPV4 Interface of vlan200, vnet0, bce0.
allow raw sockets is on,
vnet_default_interface under Network Properties was set to either none or vlan200, didn't make a difference.
Can't ping or traceroute anything other than 10.0.11.241 (FreeNAS VLAN IP).
Funny thing is I had it working before but I think that the bridge (bridge2) also included bce0 (default LAN interface) which defeats the purpose of the VLAN.
Help
Edit: Here is the tcpdump for dhcp ran on the router:
Code:
listening on igb2.200, link-type EN10MB (Ethernet), capture size 262144 bytes 17:32:04.392005 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:32:05.394185 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:32:10.444763 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:32:10.445331 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:32:19.464675 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:32:19.465494 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:32:34.469420 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:32:34.470015 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300
Here is the same tcpdump for dhcp ran on the freenas box for bridge2 interface:
Code:
listening on bridge2, link-type EN10MB (Ethernet), capture size 262144 bytes 17:32:04.393857 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:32:10.446557 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:32:19.466480 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:32:34.471162 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300
Edit.2: Works fine on LAN with bce0 being a DHCP Interface. Does not work on VLAN (vlan200)
Edit.3:
After setting the bce0 (LAN) interface as static and vlan200 interface as DHCP, here are the tcpdumps for DHCP on both the router and the FreeNAS box. Tried it multiple times, seems like the first DHCP offer makes it through to the bridge2 interface while the next ones don't.
Router:
Code:
listening on igb2.200, link-type EN10MB (Ethernet), capture size 262144 bytes 17:51:50.126951 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:51:50.127465 IP 10.0.11.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300 17:51:50.127795 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:51:50.128179 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:51:56.237995 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:51:56.238565 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:52:03.305127 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:03.305745 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:52:10.328294 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:10.328977 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:52:21.343562 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:21.344157 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300 17:52:40.380702 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:40.381386 IP 10.0.11.1.67 > 10.0.11.39.68: BOOTP/DHCP, Reply, length 300
FreeNAS:
Code:
listening on bridge2, link-type EN10MB (Ethernet), capture size 262144 bytes 17:51:50.129170 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:51:50.129971 IP 10.0.11.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300 17:51:50.130115 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:51:56.240232 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:03.307409 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:10.330581 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:21.345833 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300 17:52:40.382944 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:ff:60:ae:1b:76, length 300
Edit.4: DHCP option seems irrelevant. I have the same behavior as Edit.3 even with vlan200 Interface as static with no DHCP option ticked after a reboot.
Last edited: