Project

General

Profile

Bug #23501

DHCP from secondray NIC overrides the default gateway from network global configuration and affects bridge configurations

Added by Moon-joong Kang over 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Important
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Intel Xeon E3-1231v3
32GB Samsung PC3-12800E (8GB*4EA, Dual-Ch. conf)
Supermicro X10SL7-F

Network conf:
lagg0 : LACP, (1GBase-T, On-board I210AT *2)
ix0 : 10GBase-SR, Intel EXPX9501AFXSR (Con: Intel 82558)

ChangeLog Required:
No

Description

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.

Associated revisions

Revision b3c8678b (diff)
Added by William Grzybowski over 4 years ago

fix(middlewared): do not override default gateway from dhclient Ticket: #23501

Revision b37b0608 (diff)
Added by William Grzybowski over 4 years ago

fix(rc.d): generate etc on startup Ticket: #23501

Revision 21784bb1 (diff)
Added by William Grzybowski over 4 years ago

fix(middlewared): get default dhclient options from sbin/dhclient/clparse.c Ticket: #23501

Revision c4faa719 (diff)
Added by Warren Block about 4 years ago

If default route is set, it will be used rather than the one provided by DHCP. Ticket: #23501

History

#1 Updated by Moon-joong Kang over 4 years ago

  • File debug-nas-20170423002207.txz added

#2 Updated by Bonnie Follweiler over 4 years ago

  • Assignee set to Kris Moore

#3 Avatar?id=14398&size=24x24 Updated by Kris Moore over 4 years ago

  • Assignee changed from Kris Moore to William Grzybowski

Over for investigation

#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.

#6 Updated by William Grzybowski over 4 years ago

  • Status changed from 15 to Screened
  • Seen in changed from 9.10.4 to 9.10.2-U3

#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?

Thanks!

#8 Updated by William Grzybowski about 4 years ago

  • Status changed from 19 to Resolved

#10 Updated by Vaibhav Chauhan about 4 years ago

  • Target version changed from 11.0 to 11.0-RC

#11 Updated by Dru Lavigne almost 4 years ago

  • File deleted (debug-nas-20170423002207.txz)

#12 Updated by Dru Lavigne almost 4 years ago

  • Private changed from Yes to No

Also available in: Atom PDF