DHCP from secondray NIC overrides the default gateway from network global configuration and affects bridge configurations
Intel Xeon E3-1231v3
32GB Samsung PC3-12800E (8GB*4EA, Dual-Ch. conf)
lagg0 : LACP, (1GBase-T, On-board I210AT *2)
ix0 : 10GBase-SR, Intel EXPX9501AFXSR (Con: Intel 82558)
I have 2 interfaces at my FreeNAS setup, lagg0 and ix0.
IPv4 Def. GW from Network > Global conf. follows lagg0's. Also my jails' static IPs are set for lagg0's IP address subnet, which set automatically by FreeNAS when they're created.
But when I added the interface ix0 and set its config to DHCP and reset, FreeNAS's bridge for jails are attached to ix0, not lagg0. Of course, jails can't access outside at this situation, cause the bridge is attached with the wrong interface.
I found def. GW of the FreeNAS machine changed to ix0's from lagg0's. It seems DHCP at ix0 overrided FreeNAS host's def. GW to the GW from DHCP conf. I think because of this the bridge was attached to ix0, not lagg0. When I switch ix0's config to static one and reboot the machine, the bridge is correctly attached to lagg0 and everything works.
#4 Updated by William Grzybowski over 4 years ago
- Status changed from Unscreened to 15
- Priority changed from No priority to Important
- Target version set to 11.0
What do you think make most sense here?
Discard the default gateway from DHCP if there is a gateway configured in Network -> Global Configuration?
#5 Updated by Moon-joong Kang over 4 years ago
- Seen in changed from Unspecified to 9.10.4
- Hardware Configuration updated (diff)
In my opinion, I think following the global configuration is the best.
The def gw from global conf is explicitly set by the user and the user will expect the machine's def gw will be so.
In contrary to this, the user will usually expect the DHCP conf from Network > Interfaces will be rather limited to the applied NIC.
In sense of user's explicitness, I think the former is stronger than the latter.
Also, the the UI's def gw value is set and allowing it to be overridden by DHCP, this will cause the UI's value and actual value to not match.
Unless there is some kind of clear warning or notification, in sense of consistency between the actual conf and the conf showing on the UI, the former is better, too.
#7 Updated by William Grzybowski over 4 years ago
- Status changed from Screened to 19
A fix has been committed to ignore default gateway from DHCP client in case there is a default gateway already defined in Network - Global Configuration.
Can you try tomorrow's nightly and report back, please?