Bug #3394

« Previous | Next »

PPPoE backup connection restart failure

Added by Filippo Carletti about 5 years ago. Updated about 5 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:nethserver-firewall-base
Target version:v6.7
Security class: Resolution:
Affected version:v6.7 NEEDINFO:No

Description

When a PPPoE connection is used in a multiwan setup, if the link goes down and up again, traffic is no longer sent to the pppoe connection.
Workaround: shorewall restart

Associated revisions

Revision 1f58ad6b
Added by Filippo Carletti about 5 years ago

PPPoE multiwan: reset routing tables on up/down. Refs #3394

Revision b87189c7
Added by Filippo Carletti about 5 years ago

PPPoE multiwan: reset routing tables on up/down. Refs #3394

History

#1 Updated by Filippo Carletti about 5 years ago

  • Status changed from NEW to TRIAGED
  • Assignee set to Filippo Carletti
  • % Done changed from 0 to 20

To restore the correct routing tables after a connection failure we can restart shorewall in the ip-up event.

#2 Updated by Filippo Carletti about 5 years ago

  • Status changed from TRIAGED to ON_DEV
  • % Done changed from 20 to 30

#3 Updated by Filippo Carletti about 5 years ago

  • Status changed from ON_DEV to MODIFIED
  • Assignee deleted (Filippo Carletti)
  • % Done changed from 30 to 60

#4 Updated by Filippo Carletti about 5 years ago

In nethserver-testing:
nethserver-firewall-base-2.10.4-1.3.g1f58ad6.ns6.noarch.rpm
nethserver-firewall-base-ui-2.10.4-1.3.g1f58ad6.ns6.noarch.rpm

Test case
  • Configure a machine with a red interface
  • Add a PPPoE connection
  • Configure multiwan between PPPoE
  • Simulate a PPPoE fault:
    kill -9 of the pppoe porcess
  • Check the route table for PPPoE provider is empty
    ip ro sh ta pppoe_provider_name
  • Wait that pppoe comes back and check the provider table is correct
    ip ro sh ta pppoe_provider_name

#5 Updated by Filippo Carletti about 5 years ago

  • Status changed from MODIFIED to ON_QA
  • % Done changed from 60 to 70

#6 Updated by Giacomo Sanchietti about 5 years ago

  • Status changed from ON_QA to VERIFIED
  • % Done changed from 70 to 90

Tested on the field.

#7 Updated by Giacomo Sanchietti about 5 years ago

  • Status changed from VERIFIED to CLOSED
  • % Done changed from 90 to 100
Released in 6.7/nethserver-updates:
  • nethserver-firewall-base-2.10.5-1.ns6.noarch.rpm
  • nethserver-firewall-base-ui-2.10.5-1.ns6.noarch.rpm

Also available in: Atom PDF