Bug #2463

system_gateways_edit.php rejects correct configurations with dynamic or vpn interfaces

Added by Matt Corallo 12 months ago. Updated about 1 month ago.

Status:Resolved Start date:05/29/2012
Priority:Normal Due date:
Assignee:Seth Mos % Done:

0%

Category:Gateways
Target version:2.1
Affected version:2.1 Affected Architecture:

Description

eg. Gateway of dynamic makes the "Monitor IP" setting reject everything as having a "different Address Family"
Additionally, not sure if this is related but, checking the "Disable Gateway Monitoring" box on a openvpn client default route has no effect (despite being saved in the configuration file), causing OpenVPN clients to never work as nothing ever gets routed through the interface.

edit-gw.png - Configuration of the Gateway (72.1 kB) Thomas Gruber, 04/15/2013 02:44 am

edit-save-route.png - The error appears when saving a route (64.4 kB) Thomas Gruber, 04/15/2013 02:44 am

config-kerberos.farriah.tuxpower.org-20130415093334.xml Magnifier - configuration of the pfSense (crudely hand-censored) (22.3 kB) Thomas Gruber, 04/15/2013 02:44 am

Associated revisions

Revision c1d36d26
Added by Seth Mos 12 months ago

Finally give in and sprout a Internet Protocol drop down on the gateways edit screen.
With added validation and multiple detection parts to work when the value is not set yet.
Redmine ticket #2463

Revision e02caf4a
Added by Seth Mos 12 months ago

Actually save the IPprotocol variable into the config, otherwise it stil won't work.
People will likely need to edit and save their gateways now if they have double entries.
e.g. both manual and automatically added entries, these will dissapear as soon as you save.
If we know if the gateway or monitor is ipv4 or ipv6 we can autodetect which prevents this.
Because we don't know what address family the gateway on a dual stack interface belongs to we better not guess, and let the user figure it out. Often, a edit and save is the fastest.
For upgrading from 2.0 we could mark all gateways as being ipv4 which prevents half of the issues.
Redmine ticket #2463

Revision 31bdb9e5
Added by Seth Mos 12 months ago

Make sure to get the real interface in case we get passed a friendly interface
Redmine ticket #2463

History

#1 Updated by Seth Mos 12 months ago

  • Category set to Gateways
  • Assignee set to Seth Mos

Confirmed

#2 Updated by Seth Mos 12 months ago

  • Status changed from New to Feedback

Code checked in, I finally gave in and added a drop down for the internet protocol. There is just too much that could otherwise go wrong.

I found another few glaring errors that would have otherwise caused issues, when all gateways are dynamic on a dual stack system the v4 gateway dissapeared when adding a manual monitor IP override on the v6 entry.

#3 Updated by Seth Mos 12 months ago

I just checked in more code, and the fix that allows you to actually save the ipprotocol value.

So edit and save the gateway and it should resolve itself. The Double entries that is.

#4 Updated by Chris Buechler 6 months ago

  • Status changed from Feedback to Resolved

#5 Updated by Thomas Gruber about 1 month ago

The issue still happens to me on:
2.1-BETA1 (amd64)
built on Fri Apr 12 16:46:36 EDT 2013
FreeBSD 8.3-RELEASE-p7

I already removed and readded the dynamic GW and the route (therefore the GW appears twice in the config). This did not fix it in my case.

Maybe a bit of confusion will arise when reading the config so to explain just briefly:
Please note that i am doing Point-to-Point Routing. This means i am using /32 Netmasks on interface IPs and Routes.

Also available in: Atom PDF