Modify

Opened 7 years ago

Last modified 4 years ago

#8219 accepted defect

qos not started correctly when using pppoe

Reported by: wberrier@… Owned by: jow
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Backfire 10.03.1 RC3
Keywords: pppoe qos Cc:

Description

the init system starts qos before the pppoe wan connection is set up.

The qos script that generates firewall commands generates different commands depending on whether the pppoe interface has been set up yet.

Before the interface is set up:

...

iptables -t mangle -A OUTPUT -o eth0.1 -j Default
iptables -t mangle -A FORWARD -o eth0.1 -j Default
iptables -t mangle -A POSTROUTING -o eth0.1 -j Default
iptables -t mangle -A PREROUTING -i eth0.1 -j Default
iptables -t mangle -A PREROUTING -i eth0.1 -j IMQ --todev 0

which is not correct.

When running:

/usr/lib/qos/generate.sh firewall

after the pppoe interface is set up, I get:

...
iptables -t mangle -A OUTPUT -o pppoe-wan -j Default
iptables -t mangle -A FORWARD -o pppoe-wan -j Default
iptables -t mangle -A POSTROUTING -o pppoe-wan -j Default
iptables -t mangle -A PREROUTING -i pppoe-wan -j Default
iptables -t mangle -A PREROUTING -i pppoe-wan -j IMQ --todev 0

In the mean time, I can set up a hotplug event that will restart qos when pppoe comes up.

Attachments (0)

Change History (4)

comment:1 Changed 7 years ago by wberrier@…

This was an image built from the 10.3 branch:

Backfire (10.03, r23966) --------------------------

comment:2 Changed 7 years ago by jow

  • Owner changed from developers to jow
  • Status changed from new to accepted

comment:3 Changed 7 years ago by anonymous

I can confirm that this also happens on latest trunk version (r24896). Have to restart qos after pppoe comes up to let the qos work.

comment:4 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as accepted .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.