Modify

Opened 8 years ago

Closed 7 years ago

Last modified 4 years ago

#7188 closed defect (worksforme)

Nodogsplash traffic shaping not working in Backfire

Reported by: genesis ops Owned by: dingo
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

I've downloaded and installed Nodogsplash and the following packages on both an ar71xx and brcm47xx platform,

ip 
iptables 
iptables-mod-conntrack 
iptables-mod-conntrack-extra 
iptables-mod-extra 
iptables-mod-filter
iptables-mod-imq 
iptables-mod-ipopt 
kmod-ipt-conntrack
kmod-ipt-conntrack-extra 
kmod-ipt-core 
kmod-ipt-extra 
kmod-ipt-filter 
kmod-ipt-imq
kmod-ipt-ipopt 
kmod-ipt-nat
kmod-ipt-queue 
tc
nodogsplash

After installing the Nodogsplash package I edit and uncomment the below lines in /etc/init.d/nodogsplash

echo " Testing required modules"

    do_module_tests "ipt_mac"
    do_module_tests "ipt_mark"
    #if not using traffic control, you can comment out the following lines
    do_module_tests "imq" "numdevs=2"
    do_module_tests "ipt_IMQ"
    do_module_tests "sch_htb"

I then make the /etc/nodogsplash/nodogsplash.conf file look like this,

FirewallRuleSet preauthenticated-users {
        FirewallRule allow udp port 53
        FirewallRule allow tcp port 1:79
        FirewallRule allow tcp port 81:65535
}
FirewallRuleSet authenticated-users {
    FirewallRule allow
}
FirewallRuleSet users-to-router {
    FirewallRule allow udp port 53
    FirewallRule allow tcp port 53
    FirewallRule allow udp port 67
    FirewallRule allow tcp port 20
    FirewallRule allow tcp port 21
    FirewallRule allow tcp port 22
    FirewallRule allow tcp port 23
    FirewallRule allow tcp port 80
    FirewallRule allow tcp port 443
}
GatewayName wifi
ClientIdleTimeout 1440
ClientForceTimeout 1440
AuthenticateImmediately 0
TrafficControl 1
DownloadLimit 1539
UploadLimit 717
MaxClients 75
GatewayInterface  br-lan

I can connect to the routers wifi and the moment I ssh in and start Nodogsplash I'm locked out. It's almost as if iptables freaks out. I can have the same settings above but TrafficControl set to 0 and I can start and have no problems using the package. I of course need to limit the speed of users.

Attachments (0)

Change History (7)

comment:1 Changed 8 years ago by thepeople

  • Owner changed from developers to dingo
  • Status changed from new to assigned

comment:2 Changed 8 years ago by anonymous

I have tested this as well and found the same exact problem. This is on the ar71xx platform using backfire with .32 kernel.

I find that when the following lines are run that's when the lockout occurs,

iptables -t mangle -A ndsINC -j IMQ --todev 0
iptables -t mangle -A ndsOUT -j IMQ --todev 1

comment:3 follow-up: Changed 7 years ago by jow

  • Resolution set to worksforme
  • Status changed from assigned to closed

ip_queue is what kills the traffic here, unload & uninstall it and it should work as epxected.

comment:4 Changed 7 years ago by anonymous

traffic shapping was not working for me. I was getting this error:

"RTNETLINK answers: No such file or directory"

Finally I have solved it by editing the file /etc/init.d/nodogsplash and commenting out the last three lines:

# if not using traffic control,
# you can comment out the following 3 lines:
do_module_tests "imq" "numdevs=2"
do_module_tests "ipt_IMQ"
do_module_tests "sch_htb"

now trafic shapping is working ok.

comment:5 in reply to: ↑ 3 Changed 7 years ago by devopenwrt.9.ohbobva@…

Replying to jow:

ip_queue is what kills the traffic here, unload & uninstall it and it should work as epxected.

Can you provide more details? What specifically do I need to unload and uninstall?

comment:6 Changed 7 years ago by jow

opkg remove kmod-ipt-queue && reboot

comment:7 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 closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


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

 
Note: See TracTickets for help on using tickets.