maverickws
Cadet
- Joined
- Sep 10, 2020
- Messages
- 4
Hi there,
I am sorry I am new to this forum, first time FreeNAS user.
I am looking to test and use FreeNAS as NFS storage for VM disks.
The server has the following specs:
After installing FreeNAS I proceeded to setup the network part to try to setup the VLAN's.
Aside from finding several bugs to finally be able to setup the vlan, the vlans can't have MTU lower than 1492 and only one interface can have DHCP. So for now I am going to focus on these two bugs: DHCP and MTU.
I have read about the DHCP issue here: https://www.ixsystems.com/community/threads/multiple-interfaces-with-dhcp.58365/
I honestly don't understand what is so hard to get about the use of DHCP in several interfaces and why is this an issue. We use pfSense as firewall which is also FreeBSD based, the network performance with a plenitude of multi-dhcp-services all kinds of network configs, links, whatever. So it's not an underlying system issue.
I managed to add the VLAN with a manual IP address. I can ping destinations within that /24 network.
I added a static route for network/24 go through gateway for that network, I lost access to the FreeNAS and had to access via console to change the default route, because the default route was changed to that of the static route?!?!?!
Is FreeNAS ignorant of Classless Inter-Domain Routing?
I have 2 VLAN's for this server, each on its /24 network. It gets an IP from that network, a gateway TO THAT NETWORK, and period. It looks like we're talking about implementing some quantic solution that has never been seen before?!?
DHCP on multiple interfaces:
We too use ARP binding to provide IP addressing. But not only. We have a redundant firewall setup using CARP, in case one firewall dies we have failover. The DHCP server provides DHCP option 26 to ensure all clients use MTU 1400 as per our spec, and provides other options of our specifications. FreeNAS doesn't even allow to select MTU under 1492, its hardcoded, I am required to add a post-init command. I find this extremely limited and definitely having an hard time to enjoy FreeNAS.
Another, even on the simpler interface config where you just have to get your addressing from DHCP (only one interface, nothing else), you can't get the IPv6 from the DHCP server. Even on console, you select DHCP for IPv4 and then you have to manually put the IPv6.
Right now I am stuck on the part that I can't send traffic to the private data network /24 and adding a static route changes the default route cutting me off. I have to go on console and add default route to the outside again. There are two private networks to assign to this server, the administration network and the data network. How can this be achieved?
I truly appreciate some comments, and if anyone knows some more fit-to-purpose open-source software fit to small company usage that doesn't come with this retrograde limitations, we would immensely appreciate.
[mod note: integrated a correction -JG]
I am sorry I am new to this forum, first time FreeNAS user.
I am looking to test and use FreeNAS as NFS storage for VM disks.
The server has the following specs:
- Intel Xeon E3-1246V3
- 4x RAM 8192 MB DDR3
- 1x 240GB SDD
- 2x HDD SATA 2TB Enterprise
- Realtek 8111/8168/8411 Gigabit Ethernet
- Version: FreeNAS-11.3-U4.1
After installing FreeNAS I proceeded to setup the network part to try to setup the VLAN's.
Aside from finding several bugs to finally be able to setup the vlan, the vlans can't have MTU lower than 1492 and only one interface can have DHCP. So for now I am going to focus on these two bugs: DHCP and MTU.
I have read about the DHCP issue here: https://www.ixsystems.com/community/threads/multiple-interfaces-with-dhcp.58365/
I honestly don't understand what is so hard to get about the use of DHCP in several interfaces and why is this an issue. We use pfSense as firewall which is also FreeBSD based, the network performance with a plenitude of multi-dhcp-services all kinds of network configs, links, whatever. So it's not an underlying system issue.
I managed to add the VLAN with a manual IP address. I can ping destinations within that /24 network.
I added a static route for network/24 go through gateway for that network, I lost access to the FreeNAS and had to access via console to change the default route, because the default route was changed to that of the static route?!?!?!
Is FreeNAS ignorant of Classless Inter-Domain Routing?
I have 2 VLAN's for this server, each on its /24 network. It gets an IP from that network, a gateway TO THAT NETWORK, and period. It looks like we're talking about implementing some quantic solution that has never been seen before?!?
DHCP on multiple interfaces:
We too use ARP binding to provide IP addressing. But not only. We have a redundant firewall setup using CARP, in case one firewall dies we have failover. The DHCP server provides DHCP option 26 to ensure all clients use MTU 1400 as per our spec, and provides other options of our specifications. FreeNAS doesn't even allow to select MTU under 1492, its hardcoded, I am required to add a post-init command. I find this extremely limited and definitely having an hard time to enjoy FreeNAS.
Another, even on the simpler interface config where you just have to get your addressing from DHCP (only one interface, nothing else), you can't get the IPv6 from the DHCP server. Even on console, you select DHCP for IPv4 and then you have to manually put the IPv6.
Right now I am stuck on the part that I can't send traffic to the private data network /24 and adding a static route changes the default route cutting me off. I have to go on console and add default route to the outside again. There are two private networks to assign to this server, the administration network and the data network. How can this be achieved?
I truly appreciate some comments, and if anyone knows some more fit-to-purpose open-source software fit to small company usage that doesn't come with this retrograde limitations, we would immensely appreciate.
[mod note: integrated a correction -JG]
Last edited by a moderator: