Bug #2332

gateways always renamed to "dynamic". Implement proper IPv6 support

Added by Seth Mos about 1 year ago. Updated 2 months ago.

Status:New Start date:04/01/2012
Priority:Normal Due date:
Assignee:- % Done:

90%

Category:Gateways
Target version:2.1 Estimated time:1.50 hour
Affected version:2.1 Affected Architecture:

Description

When a dynamic IPv6 type is specified all gateways will be tagged "dynamic".

Trying to modify an existing static v4 gateway is impossible and always changed to "dynamic".
The config.xml shows that it appears that just the description is changed to dynamic.

Resolve this by implementing address families in the gateway edit page "ipproto" inet/inet6.
Compare these when performing the dynamic check.
Do not allow changing address families after a entry is made. Allow deletion.

Associated revisions

Revision c3ce2ece
Added by Seth Mos about 1 year ago

Add upgrade code that updates the dynamic gateway names to their new format new $if_$type.
Redmine Ticket #2332. I've tested a simple upgrade with 3 dynamic Wans with varying names and that appears to have succeeded. Needs more testing.

History

#1 Updated by Seth Mos about 1 year ago

Ok, so I now name the dynamic gateways by their config type, Jim uncovered a few corner cases and I'll look into whatever config upgrade code would be required so that gateway groups still work.

#2 Updated by Seth Mos about 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 90
  • Estimated time set to 1.50
  • Affected version set to 2.1

Upgrade code checked in that I tested by upgrading a 2.0 vm with 3 dynamic wans, it upgraded accordingly but might need more variations to be certain.

#3 Updated by Jim P about 1 year ago

This seems mostly OK but I discovered one case the other day that is still problematic.

If you have a PPPoE interface, and a custom gateway for that PPPoE interface (In my case, a custom name and custom loss/delay timings), it's possible when the PPPoE link is reconnecting for the dynamic counterpart (e.g. OPT1_PPPOE) to show up as well as the custom one, so it would appear for a short time that there were two gateways on the interface.

#4 Updated by Renato Botelho 2 months ago

  • Status changed from Feedback to New

Also available in: Atom PDF