opnsense / core

OPNsense GUI, API and systems backend
https://opnsense.org/
BSD 2-Clause "Simplified" License
3.36k stars 752 forks source link

System: Wizard: causes no internet connection in static IPv4 WAN environment #3873

Closed igpit closed 4 years ago

igpit commented 4 years ago

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

[x] I have searched the existing issues and I'm convinced that mine is new.

Bug decscription Walking through the Wizard, configuring a static IPv4 WAN, still 2 gateways get configured:

  1. The IPv4 "WANGW" corresponding to your static WAN configuration. It will show as offline in System: Gateways: Single.
  2. The IPv6 "WAN_DHCP6" from the default DHCP setting for IPv6 of the interface. It will be online in System: Gateways: Single, and cannot be removed there (of course, comes from interface configuration). Note: Getting state "online" happens even when no IPv6 configuration / DHCP is present.

To Reproduce Reset to defaults. Wizard: Configure static IPv4 WAN, have no DHCP on WAN side. Test ping to some WAN address, fails with "ping: sendto: No route to host"

Expected behavior

  1. Disable IPv6 DHCP
  2. Allow IPv6 setting (e.g. IPv6 Configuration Type: None) in Wizard

Workaround

  1. After running through the wizard, go to Interfaces: WAN, and set "IPv6 Configuration Type: None".
  2. Edit the IPv4 GW, changing nothing, save. The IPv4 GW will now change to state online.
  3. ping works now.

Additional context related to #3874

Environment 19.7.8

fichtner commented 4 years ago

Hi, it seems like the default behaviour. IPv6 is left configured because the wizard never supported it.

fichtner commented 4 years ago

Relevant feature ticket without a contributor https://github.com/opnsense/core/issues/79

igpit commented 4 years ago

added:

Additional context related to #3874

tk-wfischer commented 4 years ago

Hi Franco,

I think I have found the root cause of this issue:

As a short fix/workaround: