1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomato MultiWAN

Discussion in 'Tomato Firmware' started by shibby20, Dec 8, 2015.

  1. brackenhill_mob

    brackenhill_mob Network Newbie Member

    Bug report for v133

    Router: Asus RT-N66U
    ROM: 1.28.0000 MIPSR2-133 K26AC USB AIO-64K
    Issue: All devices on LAN have access to Internet. Cannot ping/ftp/ssh/... between devices other than router.

    This means that my DNLA server cannot be seen by my TV etc.

    NVRAM cleared before and after ROM upgrade.

    Changes made to config:

    SSID and WPA2 AES password
    Logged into my ISP via PPPoE

    HTH
     
  2. willoz88

    willoz88 New Member Member

    @shibby20
    Another problem...:(

    Optware installed with no errors
    pyload installed with no errors
    but pyload won't run and "segmentation fault" error...
     
  3. shibby20

    shibby20 Network Guru Member

    its not tomato issue. Try switch to entware packages.
     
  4. ptrakk

    ptrakk New Member Member

    it would be neat if it had a repository type package manager...
    ----EDIT------------------------------------------------------
    oh it does!!? :D entware..
    --------------------------------------------------------------
    Is the source code available?
     
    Last edited: Mar 4, 2016
  5. tomvbye

    tomvbye New Member Member

    Hi Shibby, in 133 when I put one wlan interface into the wireless Ethernet bridge mode if whatever you modify other setting and click save you will get those: "The field "wl_radio" is invalid. Please report this problem.". Thanks Shibby bring this wonderful firmware to us : )
     
  6. ptrakk

    ptrakk New Member Member

    This doesn't look right? shouldn't the wan be designated to the wan port in VLAN settings? this is the default. also busybox's nc isnt compiled with listening support.
     

    Attached Files:

    Last edited: Mar 4, 2016
  7. shibby20

    shibby20 Network Guru Member

  8. willoz88

    willoz88 New Member Member

    solved with entware
    i thought so, but optware working well with v132
    :confused:
     
  9. Jackos

    Jackos New Member Member

    Hi all and thank you Shibby for these Tomato versions

    Bug report for v133

    Edit : bugs already reported elsewhere..
     
    Last edited: Mar 5, 2016
  10. ptrakk

    ptrakk New Member Member

  11. Connor McCaffrey

    Connor McCaffrey Networkin' Nut Member

    ok my question is if i dont care about dual wan and just running R7000 as AP + NAS should i used 132 or 133 multiwan???
     
  12. WaJoWi

    WaJoWi Connected Client Member

    Hello!

    I am using an Asus RT-N66U with Tomato firmware 1.28.0000 MIPSR2-133 K26 USB AIO 64K.

    I was very happy about the announcement of Muli-WAN. But unfortunately I can not make it to use my USB 3G stick with it. I have deleted NVRAM after flashing and everything re-set.

    Under Windows and also with the firmware from Merlin the stick work fine, unfortunately not with Tomato. What am I doing wrong?

    Here are a few screenshots of my settings (I can't add any pictures):

    My stick under Windows 10

    Option for Internetconnection under Windows

    USB-Support (the stick cannot mounted)

    VLAN is set

    Networksettings

    Overview (cannot connect :mad:)

    In my logfile can I find:
    Code:
    Mar  5 09:59:06 unknown user.notice root: WAN Watchdog - Connection wan2 down - Reconnecting ...
    Mar  5 09:59:07 unknown user.debug kernel: vlan4: del 33:33:00:00:00:01 mcast address from vlan interface
    Mar  5 09:59:07 unknown user.debug kernel: vlan4: del 33:33:00:00:00:01 mcast address from master interface
    Mar  5 09:59:07 unknown user.debug kernel: vlan4: del 01:00:5e:00:00:01 mcast address from vlan interface
    Mar  5 09:59:07 unknown user.debug kernel: vlan4: del 01:00:5e:00:00:01 mcast address from master interface
    Mar  5 09:59:07 unknown user.emerg init[1]: OUT checkConnect, wan2 is disconnected
    Mar  5 09:59:07 unknown user.emerg init[1]: OUT fun mwan_load_balance, mwan_curr=2000
    Mar  5 09:59:07 unknown user.warn kernel: vlan4: Setting MAC address to  d8 50 e6 ac 5b 61.
    Mar  5 09:59:07 unknown user.debug kernel: vlan4: add 01:00:5e:00:00:01 mcast address to master interface
    Mar  5 09:59:07 unknown user.debug kernel: vlan4: add 33:33:00:00:00:01 mcast address to master interface
    Mar  5 09:59:07 unknown daemon.err pppd[10053]: In file /tmp/ppp/wan2_options: unrecognized option '/dev/ttyACM0'
    Mar  5 09:59:07 unknown daemon.info dnsmasq[9823]: exiting on receipt of SIGTERM
    Mar  5 09:59:07 unknown user.debug init[1]: 255: pptp peerdns disabled
    Mar  5 09:59:07 unknown user.notice root: WAN Watchdog - another proces in action for wan2
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: started, version 2.73 cachesize 4096
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset Tomato-helper auth DNSSEC loop-detect no-inotify
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: asynchronous logging enabled, queue limit is 5 messages
    Mar  5 09:59:07 unknown daemon.info dnsmasq-dhcp[10060]: DHCP, IP range 192.168.2.11 -- 192.168.2.19, lease time 1d
    Mar  5 09:59:07 unknown daemon.info dnsmasq-dhcp[10060]: DHCP, IP range 192.168.1.2 -- 192.168.1.51, lease time 1d
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: reading /etc/resolv.dnsmasq
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: using nameserver 8.8.8.8#53
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: using nameserver 208.67.222.222#53
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: read /etc/hosts - 3 addresses
    Mar  5 09:59:07 unknown daemon.info dnsmasq[10060]: read /etc/dnsmasq/hosts/hosts - 22 addresses
    Mar  5 09:59:07 unknown daemon.info dnsmasq-dhcp[10060]: read /etc/dnsmasq/dhcp/dhcp-hosts
    Mar  5 09:59:07 unknown user.notice root: WAN Watchdog - another proces in action for wan2
    Mar  5 09:59:07 unknown user.info kernel: usbcore: registered new interface driver cdc_acm
    Mar  5 09:59:07 unknown user.info kernel: drivers/usb/class/cdc-acm.c: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
    Mar  5 09:59:07 unknown user.info kernel: usbcore: registered new interface driver usbserial
    Mar  5 09:59:07 unknown user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
    Mar  5 09:59:07 unknown user.info kernel: usbcore: registered new interface driver usbserial_generic
    Mar  5 09:59:07 unknown user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
    Mar  5 09:59:07 unknown user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
    Mar  5 09:59:07 unknown user.info kernel: usbcore: registered new interface driver option
    Mar  5 09:59:07 unknown user.info kernel: drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.2
    Mar  5 09:59:07 unknown user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem
    Mar  5 09:59:07 unknown user.info kernel: usbcore: registered new interface driver sierra
    Mar  5 09:59:07 unknown user.info kernel: drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.7.0
    Mar  5 09:59:09 unknown user.notice root: 3G MODEM not found by cdc-acm, option or sierra module. Trying usbserial ...
    Mar  5 09:59:09 unknown user.info kernel: usbcore: deregistering interface driver sierra
    Mar  5 09:59:09 unknown user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial deregistering driver Sierra USB modem
    Mar  5 09:59:09 unknown user.info kernel: usbcore: deregistering interface driver option
    Mar  5 09:59:09 unknown user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial deregistering driver GSM modem (1-port)
    Mar  5 09:59:09 unknown user.info kernel: usbcore: deregistering interface driver usbserial_generic
    Mar  5 09:59:09 unknown user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial deregistering driver generic
    Mar  5 09:59:09 unknown user.info kernel: usbcore: deregistering interface driver usbserial
    Mar  5 09:59:09 unknown user.info kernel: usbcore: deregistering interface driver cdc_acm
    Mar  5 09:59:10 unknown user.notice root: 3G MODEM Signal Strength: -113 dBm
    Mar  5 09:59:42 unknown user.emerg mwanroute[2470]: OUT checkConnect, wan2 is disconnected
    
     
  13. ProZach

    ProZach Reformed Router Member

    Just reporting in with the same QOS issue...

    Says error line 7. I think it's because QOSO only has one rule by the time it gets to the -I QOSO 3 line. If I try to run it manually I get:
    iptables -t mangle -I QOSO 3 -m connmark ! --mark 0/0xff000 -j QOSSIZE
    iptables: Index of insertion too big

    It either needs to be an -A rule or -I QOSO 2


    Code:
    *mangle
    :PREROUTING ACCEPT [0:0]
    :OUTPUT ACCEPT [0:0]
    :QOSO - [0:0]
    -A QOSO -j CONNMARK --restore-mark --mask 0xfff
    :QOSSIZE - [0:0]
    THIS LINE-> -I QOSO 3 -m connmark ! --mark 0/0xff000 -j QOSSIZE
    -A QOSSIZE -m connmark --mark 0x1000/0xff000 -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 10240: -j CONNMARK --set-mark 0x00000/0xFF
    -A QOSO -p udp --dport 53   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p tcp --dport 53   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-mark 0x2/0xFF
    
     
  14. ProZach

    ProZach Reformed Router Member

    Also, trying to debug and get a little further, it also appears that the layer7 iptables match module is not installed...
    It does not exist in /proc/net/ip_tables_matches
     
  15. ptrakk

    ptrakk New Member Member

    You may need to compile modemmanager or libqmi/qmicli for your router to the appropriate linux kernel.
     
  16. ProZach

    ProZach Reformed Router Member

    Further digging on the QoS issue...
    /release/src/router/rc/qos.c - Line 204ish I think needs to be changed to insert at 2 instead of 3. (Or line 2 is missing)
    Also, the layer7 module is included with the build, it's just not loaded before starting QoS. I'm not sure if it typically auto-loads or if you load it manually somewhere and it's not doing it.
    You probably know all this without looking but figured I'd have a look and see if I could be helpful.
    Thanks for all the work on this shibby. Honestly, I would love to figure out how to port your build to my Ubiquiti Edgerouter X.. It's a MIPS box. ;-)
     
    AndreDVJ likes this.
  17. WaJoWi

    WaJoWi Connected Client Member

    Thanks for the reply, but unfortunately I have no idea how I can do that. Is there a tutorial on the net?
     
  18. kanata2004

    kanata2004 New Member Member

    Exact same problem. Two 3G ZTE Modem and one 4G/LTE Huawei Modem, all work with 132, none works with 133.
     
  19. ptrakk

    ptrakk New Member Member

    here is my working iptables file with QOS from a previous firmware..

    Code:
    *mangle
    :PREROUTING ACCEPT [0:0]
    :OUTPUT ACCEPT [0:0]
    :QOSO - [0:0]
    -A QOSO -j CONNMARK --restore-mark --mask 0xff
    -A QOSO -m connmark ! --mark 0/0x0f00 -j RETURN
    :QOSSIZE - [0:0]
    -I QOSO 3 -m connmark ! --mark 0/0xff000 -j QOSSIZE
    -I QOSO 4 -m connmark ! --mark 0/0xff000 -j RETURN
    -A QOSSIZE -m connmark --mark 0x1000/0xff000 -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 10240: -j CONNMARK --set-return 0x00000/0xFF
    -A QOSO -p udp --dport 53   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-return 0x101001/0xFF
    -A QOSO -p tcp --dport 53   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-return 0x101001/0xFF
    -A QOSO -p udp --dport 37   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-return 0x201001/0xFF
    -A QOSO -p tcp --dport 37   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-return 0x201001/0xFF
    -A QOSO -p udp --dport 123   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-return 0x301001/0xFF
    -A QOSO -p udp --dport 3455   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-return 0x401001/0xFF
    -A QOSO -p tcp --dport 3455   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-return 0x401001/0xFF
    -A QOSSIZE -m connmark --mark 0x2000/0xff000 -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 51200: -j CONNMARK --set-return 0x00000/0xFF
    -A QOSO -p udp --dport 9   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:51199 -j CONNMARK --set-return 0x502004/0xFF
    -A QOSO -p tcp --dport 9   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:51199 -j CONNMARK --set-return 0x502004/0xFF
    -A QOSO -p udp -m multiport --ports 135,2101,2103,2105   -j CONNMARK --set-return 0x600104/0xFF
    -A QOSO -p tcp -m multiport --ports 135,2101,2103,2105   -j CONNMARK --set-return 0x600104/0xFF
    -A QOSO -p tcp -m multiport --ports 22,2222   -j CONNMARK --set-return 0x800103/0xFF
    -A QOSO -p tcp -m multiport --dports 23,992   -j CONNMARK --set-return 0x900103/0xFF
    -A QOSO -p tcp -m multiport --sports 80,5938,8080,2222   -j CONNMARK --set-return 0xa00103/0xFF
    -A QOSO -p udp -m multiport --ports 3389   -j CONNMARK --set-return 0xb00103/0xFF
    -A QOSO -p tcp -m multiport --ports 3389   -j CONNMARK --set-return 0xb00103/0xFF
    -A QOSO -p udp -m multiport --ports 1220,6970:7170,8554   -j CONNMARK --set-return 0xc00105/0xFF
    -A QOSO -p tcp -m multiport --ports 1220,6970:7170,8554   -j CONNMARK --set-return 0xc00105/0xFF
    -A QOSO -p udp -m multiport --ports 554,5004,5005   -j CONNMARK --set-return 0xd00105/0xFF
    -A QOSO -p tcp -m multiport --ports 554,5004,5005   -j CONNMARK --set-return 0xd00105/0xFF
    -A QOSO -p udp -m multiport --ports 1755   -j CONNMARK --set-return 0xe00105/0xFF
    -A QOSO -p tcp -m multiport --ports 1755   -j CONNMARK --set-return 0xe00105/0xFF
    -A QOSO -p udp -m multiport --dports 3478,3479,5060:5063   -j CONNMARK --set-return 0xf00102/0xFF
    -A QOSO -p tcp -m multiport --dports 3478,3479,5060:5063   -j CONNMARK --set-return 0xf00102/0xFF
    -A QOSO -p udp -m multiport --sports 53,88,3074   -j CONNMARK --set-return 0x1000102/0xFF
    -A QOSO -p tcp -m multiport --sports 53,88,3074   -j CONNMARK --set-return 0x1000102/0xFF
    -A QOSO -p tcp --dport 1718:1720   -j CONNMARK --set-return 0x1100102/0xFF
    -A QOSO -p udp -m multiport --dports 4380,27000:27050,11031,11235:11335,11999,2300:2400,6073,28800:29100,47624   -j CONNMARK --set-return 0x1200102/0xFF
    -A QOSO -p tcp -m multiport --dports 4380,27000:27050,11031,11235:11335,11999,2300:2400,6073,28800:29100,47624   -j CONNMARK --set-return 0x1200102/0xFF
    -A QOSO -p udp -m multiport --dports 1493,1502,1503,1542,1863,1963,3389,5061,5190:5193,7001   -j CONNMARK --set-return 0x1300106/0xFF
    -A QOSO -p tcp -m multiport --dports 1493,1502,1503,1542,1863,1963,3389,5061,5190:5193,7001   -j CONNMARK --set-return 0x1300106/0xFF
    -A QOSO -p udp -m multiport --dports 1071:1074,1455,1638,1644,5000:5010,5050,5100,5101,5150,8000:8002   -j CONNMARK --set-return 0x1400106/0xFF
    -A QOSO -p tcp -m multiport --dports 1071:1074,1455,1638,1644,5000:5010,5050,5100,5101,5150,8000:8002   -j CONNMARK --set-return 0x1400106/0xFF
    -A QOSO -p udp -m multiport --dports 194,1720,1730:1732,5220:5223,5298,6660:6669,22555   -j CONNMARK --set-return 0x1500106/0xFF
    -A QOSO -p tcp -m multiport --dports 194,1720,1730:1732,5220:5223,5298,6660:6669,22555   -j CONNMARK --set-return 0x1500106/0xFF
    -A QOSO -p udp --dport 19294:19310   -j CONNMARK --set-return 0x1600106/0xFF
    -A QOSO -p tcp --dport 19294:19310   -j CONNMARK --set-return 0x1600106/0xFF
    -A QOSO -p tcp -m multiport --dports 6005,6006   -j CONNMARK --set-return 0x1700106/0xFF
    -A QOSO -p udp -m multiport --ports 6571,6891:6901   -j CONNMARK --set-return 0x1800106/0xFF
    -A QOSO -p tcp -m multiport --ports 6571,6891:6901   -j CONNMARK --set-return 0x1800106/0xFF
    -A QOSO -p udp -m multiport --ports 29613   -j CONNMARK --set-return 0x1900106/0xFF
    -A QOSO -p tcp -m multiport --ports 29613   -j CONNMARK --set-return 0x1900106/0xFF
    -A QOSO -p tcp -m multiport --ports 4244,5242   -j CONNMARK --set-return 0x1a00102/0xFF
    -A QOSO -p udp -m multiport --ports 5243,9785   -j CONNMARK --set-return 0x1b00102/0xFF
    -A QOSO -p udp -m multiport --ports 3478:3497,16384:16387,16393:16402   -j CONNMARK --set-return 0x1c00106/0xFF
    -A QOSSIZE -m connmark --mark 0x3000/0xff000 -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-return 0x00000/0xFF
    -A QOSO -p tcp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:524287 -j CONNMARK --set-return 0x1d03004/0xFF
    -A QOSO -p tcp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-return 0x1e00106/0xFF
    -A QOSO -p udp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:524287 -j CONNMARK --set-return 0x1f03004/0xFF
    -A QOSO -p udp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-return 0x2000106/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-return 0x2100102/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-return 0x2100102/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto youtube-2012 -j CONNMARK --set-return 0x2300105/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto youtube-2012 -j CONNMARK --set-return 0x2300105/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto httpvideo -j CONNMARK --set-return 0x2400105/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto httpvideo -j CONNMARK --set-return 0x2400105/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto flash -j CONNMARK --set-return 0x2500105/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto flash -j CONNMARK --set-return 0x2500105/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtp -j CONNMARK --set-return 0x2600105/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtp -j CONNMARK --set-return 0x2600105/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtmp -j CONNMARK --set-return 0x2700105/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtmp -j CONNMARK --set-return 0x2700105/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto shoutcast -j CONNMARK --set-return 0x2800105/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto shoutcast -j CONNMARK --set-return 0x2800105/0xFF
    -A QOSO  -m layer7 --l7dir /etc/l7-protocols --l7proto rtmpt -j CONNMARK --set-return 0x2900105/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto irc -j CONNMARK --set-return 0x2a00106/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto irc -j CONNMARK --set-return 0x2a00106/0xFF
    -A QOSO -p tcp -m multiport --dports 80,8080   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:524287 -j CONNMARK --set-return 0x2b00004/0xFF
    -A QOSO -p tcp -m multiport --dports 80,8080   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-return 0x2c00008/0xFF
    -A QOSO -p tcp -m multiport --dports 20,21,989,990   -j CONNMARK --set-return 0x2d00008/0xFF
    -A QOSO -p tcp -m multiport --dports 25,587,465,2525   -j CONNMARK --set-return 0x2e00007/0xFF
    -A QOSO -p tcp -m multiport --dports 110,995   -j CONNMARK --set-return 0x2f00007/0xFF
    -A QOSO -p tcp -m multiport --dports 119,563   -j CONNMARK --set-return 0x3000008/0xFF
    -A QOSO -p tcp -m multiport --dports 143,220,585,993   -j CONNMARK --set-return 0x3100007/0xFF
    -A QOSO -p udp --dport 1:65535   -j CONNMARK --set-return 0x3200009/0xFF
    -A QOSO -j CONNMARK --set-return 0xff00009
    -A FORWARD -o vlan1 -j QOSO
    -A OUTPUT -o vlan1 -j QOSO
    -A PREROUTING -i vlan1 -j CONNMARK --restore-mark --mask 0xff
    -A PREROUTING -i vlan1 -j IMQ --todev 0
    -I PREROUTING -i vlan1 -j DSCP --set-dscp 0
    COMMIT
    *nat
    :PREROUTING ACCEPT [0:0]
    :POSTROUTING ACCEPT [0:0]
    :OUTPUT ACCEPT [0:0]
    :WANPREROUTING - [0:0]
    -A PREROUTING -d 192.168.2.2 -j WANPREROUTING
    -A PREROUTING -i vlan1 -d 192.168.1.1/255.255.255.0 -j DROP
    -A WANPREROUTING -p icmp -j DNAT --to-destination 192.168.1.1
    -A POSTROUTING  -o vlan1 -j MASQUERADE
    -A POSTROUTING -o br0 -s 192.168.1.1/255.255.255.0 -d 192.168.1.1/255.255.255.0 -j SNAT --to-source 192.168.1.1
    COMMIT
    *filter
    :INPUT DROP [0:0]
    :OUTPUT ACCEPT [0:0]
    -A INPUT -m state --state INVALID -j DROP
    -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
    -N shlimit
    -A shlimit -m recent --set --name shlimit
    -A shlimit -m recent --update --hitcount 4 --seconds 60 --name shlimit -j DROP
    -A INPUT -p tcp --dport 22 -m state --state NEW -j shlimit
    -A INPUT -i lo -j ACCEPT
    -A INPUT -i br0 -j ACCEPT
    :FORWARD DROP [0:0]
    -A FORWARD -m account --aaddr 192.168.1.0/255.255.255.0 --aname lan
    -A FORWARD -i br0 -o br0 -j ACCEPT
    -A FORWARD -m state --state INVALID -j DROP
    -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
    :L7in - [0:0]
    -A FORWARD -i vlan1 -j L7in
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto youtube-2012 -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto httpvideo -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto flash -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto rtp -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto rtmp -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto shoutcast -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto rtmpt -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto irc -j RETURN
    :wanin - [0:0]
    :wanout - [0:0]
    -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
    -A FORWARD -i vlan1 -j wanin
    -A FORWARD -o vlan1 -j wanout
    -A FORWARD -i br0 -j ACCEPT
    COMMIT
    
     
  20. ptrakk

    ptrakk New Member Member

    and my non-working iptables with QOS enabled in the 133 firmware (a few differences):
    Code:
    *mangle
    :PREROUTING ACCEPT [0:0]
    :OUTPUT ACCEPT [0:0]
    :QOSO - [0:0]
    -A QOSO -j CONNMARK --restore-mark --mask 0xfff
    :QOSSIZE - [0:0]
    -I QOSO 3 -m connmark ! --mark 0/0xff000 -j QOSSIZE
    -A QOSSIZE -m connmark --mark 0x1000/0xff000 -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 10240: -j CONNMARK --set-mark 0x00000/0xFF
    -A QOSO -p udp --dport 53   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p tcp --dport 53   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p udp --dport 37   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p tcp --dport 37   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p udp --dport 123   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p udp --dport 3455   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSO -p tcp --dport 3455   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:10239 -j CONNMARK --set-mark 0x1/0xFF
    -A QOSSIZE -m connmark --mark 0x2000/0xff000 -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 51200: -j CONNMARK --set-mark 0x00000/0xFF
    -A QOSO -p udp --dport 9   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:51199 -j CONNMARK --set-mark 0x4/0xFF
    -A QOSO -p tcp --dport 9   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:51199 -j CONNMARK --set-mark 0x4/0xFF
    -A QOSO -p udp -m multiport --ports 135,2101,2103,2105   -j CONNMARK --set-mark 0x4/0xFF
    -A QOSO -p tcp -m multiport --ports 135,2101,2103,2105   -j CONNMARK --set-mark 0x4/0xFF
    -A QOSO -p tcp -m multiport --ports 22,2222   -j CONNMARK --set-mark 0x3/0xFF
    -A QOSO -p tcp -m multiport --dports 23,992   -j CONNMARK --set-mark 0x3/0xFF
    -A QOSO -p tcp -m multiport --sports 80,5938,8080,2222   -j CONNMARK --set-mark 0x3/0xFF
    -A QOSO -p udp -m multiport --ports 3389   -j CONNMARK --set-mark 0x3/0xFF
    -A QOSO -p tcp -m multiport --ports 3389   -j CONNMARK --set-mark 0x3/0xFF
    -A QOSO -p udp -m multiport --ports 1220,6970:7170,8554   -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp -m multiport --ports 1220,6970:7170,8554   -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp -m multiport --ports 554,5004,5005   -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp -m multiport --ports 554,5004,5005   -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp -m multiport --ports 1755   -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp -m multiport --ports 1755   -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp -m multiport --dports 3478,3479,5060:5063   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p tcp -m multiport --dports 3478,3479,5060:5063   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p udp -m multiport --sports 53,88,3074   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p tcp -m multiport --sports 53,88,3074   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p tcp --dport 1718:1720   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p udp -m multiport --dports 4380,27000:27050,11031,11235:11335,11999,2300:2400,6073,28800:29100,47624   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p tcp -m multiport --dports 4380,27000:27050,11031,11235:11335,11999,2300:2400,6073,28800:29100,47624   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p udp -m multiport --dports 1493,1502,1503,1542,1863,1963,3389,5061,5190:5193,7001   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --dports 1493,1502,1503,1542,1863,1963,3389,5061,5190:5193,7001   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p udp -m multiport --dports 1071:1074,1455,1638,1644,5000:5010,5050,5100,5101,5150,8000:8002   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --dports 1071:1074,1455,1638,1644,5000:5010,5050,5100,5101,5150,8000:8002   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p udp -m multiport --dports 194,1720,1730:1732,5220:5223,5298,6660:6669,22555   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --dports 194,1720,1730:1732,5220:5223,5298,6660:6669,22555   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p udp --dport 19294:19310   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp --dport 19294:19310   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --dports 6005,6006   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p udp -m multiport --ports 6571,6891:6901   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --ports 6571,6891:6901   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p udp -m multiport --ports 29613   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --ports 29613   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --ports 4244,5242   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p udp -m multiport --ports 5243,9785   -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p udp -m multiport --ports 3478:3497,16384:16387,16393:16402   -j CONNMARK --set-mark 0x6/0xFF
    -A QOSSIZE -m connmark --mark 0x3000/0xff000 -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-mark 0x00000/0xFF
    -A QOSO -p tcp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:524287 -j CONNMARK --set-mark 0x4/0xFF
    -A QOSO -p tcp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p udp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:524287 -j CONNMARK --set-mark 0x4/0xFF
    -A QOSO -p udp --dport 443   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j CONNMARK --set-mark 0x2/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto youtube-2012 -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto youtube-2012 -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto httpvideo -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto httpvideo -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto flash -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto flash -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtp -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtp -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtmp -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto rtmp -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto shoutcast -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto shoutcast -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO  -m layer7 --l7dir /etc/l7-protocols --l7proto rtmpt -j CONNMARK --set-mark 0x5/0xFF
    -A QOSO -p udp   -m layer7 --l7dir /etc/l7-protocols --l7proto irc -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp   -m layer7 --l7dir /etc/l7-protocols --l7proto irc -j CONNMARK --set-mark 0x6/0xFF
    -A QOSO -p tcp -m multiport --dports 80,8080   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:524287 -j CONNMARK --set-mark 0x4/0xFF
    -A QOSO -p tcp -m multiport --dports 80,8080   -m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 524288: -j CONNMARK --set-mark 0x8/0xFF
    -A QOSO -p tcp -m multiport --dports 20,21,989,990   -j CONNMARK --set-mark 0x8/0xFF
    -A QOSO -p tcp -m multiport --dports 25,587,465,2525   -j CONNMARK --set-mark 0x7/0xFF
    -A QOSO -p tcp -m multiport --dports 110,995   -j CONNMARK --set-mark 0x7/0xFF
    -A QOSO -p tcp -m multiport --dports 119,563   -j CONNMARK --set-mark 0x8/0xFF
    -A QOSO -p tcp -m multiport --dports 143,220,585,993   -j CONNMARK --set-mark 0x7/0xFF
    -A QOSO -p udp --dport 1:65535   -j CONNMARK --set-mark 0x9/0xFF
    -A QOSO -m connmark --mark 0x0/0xff -j CONNMARK --set-mark 0x9/0xff
    -A FORWARD -o vlan1 -j QOSO
    -A OUTPUT -o vlan1 -j QOSO
    -A PREROUTING -i vlan1 -j CONNMARK --restore-mark --mask 0xfff
    -A PREROUTING -i vlan1 -j IMQ --todev 0
    -I PREROUTING -i vlan1 -j DSCP --set-dscp 0
    COMMIT
    *nat
    :PREROUTING ACCEPT [0:0]
    :POSTROUTING ACCEPT [0:0]
    :OUTPUT ACCEPT [0:0]
    :WANPREROUTING - [0:0]
    -A PREROUTING -d 192.168.2.2 -j WANPREROUTING
    -A PREROUTING -i vlan1 -d 192.168.1.1/255.255.255.0 -j DROP
    -A WANPREROUTING -p icmp -j DNAT --to-destination 192.168.1.1
    -A POSTROUTING  -o vlan1 -j MASQUERADE
    -A POSTROUTING -o br0 -s 192.168.1.1/255.255.255.0 -d 192.168.1.1/255.255.255.0 -j SNAT --to-source 192.168.1.1
    COMMIT
    *filter
    :INPUT DROP [0:0]
    :OUTPUT ACCEPT [0:0]
    -A INPUT -m state --state INVALID -j DROP
    -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
    -N shlimit
    -A shlimit -m recent --set --name shlimit
    -A shlimit -m recent --update --hitcount 4 --seconds 60 --name shlimit -j DROP
    -A INPUT -p tcp --dport 22 -m state --state NEW -j shlimit
    -A INPUT -i lo -j ACCEPT
    -A INPUT -i br0 -j ACCEPT
    -A INPUT -p icmp -m limit --limit 2/second -j ACCEPT
    -A INPUT -p udp --dport 33434:33534 -m limit --limit 10/second -j ACCEPT
    :FORWARD DROP [0:0]
    -A FORWARD -m account --aaddr 192.168.1.0/255.255.255.0 --aname lan
    -A FORWARD -i br0 -o br0 -j ACCEPT
    -A FORWARD -m state --state INVALID -j DROP
    -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
    :L7in - [0:0]
    -A FORWARD -i vlan1 -j L7in
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto skypetoskype -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto youtube-2012 -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto httpvideo -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto flash -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto rtp -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto rtmp -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto shoutcast -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto rtmpt -j RETURN
    -A L7in -m layer7 --l7dir /etc/l7-protocols --l7proto irc -j RETURN
    :wanin - [0:0]
    :wanout - [0:0]
    -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
    -A FORWARD -i vlan1 -j wanin
    -A FORWARD -o vlan1 -j wanout
    -A FORWARD -i br0 -j ACCEPT
    COMMIT
    

    I hope this helps.

    On first glance the Non-Working one is missing lines with return in them:

    -A QOSO -m connmark ! --mark 0/0x0f00 -j RETURN

    -I QOSO 4 -m connmark ! --mark 0/0xff000 -j RETURN
     
  21. willoz88

    willoz88 New Member Member

    @kanata2004 what huawei modem are you tryin?
    I have a3372h with several firmwares and never work at all used as wan2.
    Also trying to use as single wan mode but there are many problems of disconnection on v133.
    with v132 single wan everything works fine...
     
  22. phuklok1

    phuklok1 Network Guru Member

    Great feature.This is really useful in a situation where in addition to the primary wired WAN you can have a backup wireless (client mode) WAN feeding a LAN. Thanks for your continued work on Tomato!
     
    Last edited: Mar 7, 2016
  23. AddRemover

    AddRemover New Member Member

    Hi Shibby! Thanks a lot for your efforts.
    Dual WAN is what I really want in your firmware for a while.
    However, my old Netgear WNR3500L (V1) with 8mb flash won't fit any of 133 build. It's too big :(
    I use 1.28.0000 MIPSR2-132 K26 USB BTgui-VPN
    ps consider to build 134 with size below 7.2 mb
     
  24. remlei

    remlei Networkin' Nut Member

    ^use the VPN build
     
  25. tsynik

    tsynik New Member Member

    About 3G modems: they not autostart, because of at moment when pppd tries to call, there is not (yet) serial device available (/dev/ttyUSB0 etc). Fw still loading drivers, switches USB mode etc. If you press Connect in UI later - it will work ;-)
     
  26. WaJoWi

    WaJoWi Connected Client Member

    Unfortunately it does not work for me if I want to connect manually. :(
     
  27. kanata2004

    kanata2004 New Member Member

    No, it does not work for me. It works with 132 single WAN without manually re-connect.
    Have you tried?
     
  28. Schlotterknie

    Schlotterknie New Member Member

    Since I´ve installed one of these new MultiWAN versions 133 or 134 I have a problem to bypass my permanent VPN connection to a paid VPN provider like I did with older versions. With version 132 and before everything worked perfectly.

    I used to bypass that VPN connection (which is certainly established by my router) with a specific computer of my little network (local IP 192.168.1.12) using this WAN Up script I found somewhere in the net:

    nvram set no_vpn_lst="192.168.1.12"
    nvram commit
    #!/bin/sh
    sleep 30
    NO_VPN_LST=`nvram get no_vpn_lst`
    [ -z "$NO_VPN_LST" ] && exit 0
    WAN_GWAY="0.0.0.0"
    while [ $WAN_GWAY == "0.0.0.0" ]; do
    sleep 3
    WAN_GWAY=`nvram get wan_gateway`
    done
    ip route add default via $WAN_GWAY table 10
    for ipa in $NO_VPN_LST; do
    ip rule add from $ipa table 10
    done
    ip route flush cache
    exit 0


    After I flash version 133 or 134 that computer 192.168.1.12 which actually just should bypass the routers VPN connection can´t connect to the internet anymore.

    I am not an expert so maybe anybody knows how to get that working with v134 again...
     
  29. nmalinoski

    nmalinoski Serious Server Member

    Is there a list of which nvram variables changed and how? It would be nice to have an update script to run (then reboot), rather than having to physically be present to set up the router again from scratch.
     
  30. AddRemover

    AddRemover New Member Member

    VPN build also return "can't fit MTD". So there is no build for my router available.
     
  31. shibby20

    shibby20 Network Guru Member

    for 3500Lv1 i will make new buildtype miniVPN (VPN without dnscrypt and jffs) and this will be the only one image which fit on this router.
     
    AddRemover likes this.
  32. AddRemover

    AddRemover New Member Member

    Thanks Shibby! Will look forward to 134 build.
    I use jffs on my usb-attached drive, so it's ok for me.
     
  33. willoz88

    willoz88 New Member Member

    Not really, some times works form me but not everytime, and when it works the modem disconnects after a little time with no reason without possibility to reconnect manually,only reboot take effect. Waiting v134 for some improvements...
     
  34. remlei

    remlei Networkin' Nut Member

    is there any way to set a default routing in dual wan mode. I want to use all default traffic to WAN1 and some policy routing on WAN2.

    I can set a policy routing to WAN2 but default routing is load balance. In OpenWRT mwan3, there's a some sort of well defined policy routing, which you can control which traffic goes to where.
     
  35. snakeaj

    snakeaj New Member Member

    Hello!

    I am using your software for many years right now!
    WultiWAN was the only feature i always missed.

    I can use WultiWAN now - but no BW Limiter any more :-(

    Is there a possibility to get WultiWAN + BW Limiter? (+ Captive Portal?)

    thank you so much
    alex
     
  36. Sparkix

    Sparkix Connected Client Member

    I have also noticed that -134 on my Asus RT-AC68U, that the VPN routing does not work. I can send everything or nothing over the VPN, but it doesn't listen to the addresses I put in that table.

    Edit: I rebooted the router a few times and it seems to be working now. There must be some technique to getting the initial startup sequence right.
     
    Last edited: Mar 15, 2016
  37. brainz

    brainz Networkin' Nut Member

    Just tried tomato-RT-AC56U-ARM--134-AIO-64K.
    It's missing the Trunk VLAN support override (experimental) option. My ISP requires it.
    I tried setting trunk_vlan_so=1 via ssh, but it's not working.

    Back to v132 now and my internet is working again.
     
  38. tvlz

    tvlz Addicted to LI Member

    Trunk VLAN support is now enabled by default, so the override option was removed.
     
  39. krism75

    krism75 Serious Server Member

    I read I need to erase the nvram, but can I restore a backed-up nvram after upgrade or do I need to change all settings again?
    Can you provide a upgrade tool for this?
     
  40. Samuelheng

    Samuelheng Networkin' Nut Member

    Anyone can confirm v134 fw qos graphs is working ??

    ady tried nvram erase (clean config) on R7000.

    thanks.
     
  41. gkhicks

    gkhicks Network Newbie Member

    Running
    Tomato Firmware 1.28.0000 MIPSR2-133 K26 USB AIO

    ... Router: Asus RT-NT16

    1) Single WAN configured... QOS activation breaks connection to WAN

    Edit: Sorry... meant to say that the connection from LAN to WAN vs. the WAN connection is breaking!

    2) Can't restore prior release with NVRAM erased upon install... PPoE session can't establish... so, is there a known issue with going back to v1.32?

    If there's something I can do to provide debug data... just ask! :)

    Thank you.
     
    Last edited: Mar 13, 2016
  42. sfortis

    sfortis New Member Member

    AC56U, 134: QoS is not breaking the WAN but is not working :) (also after nvram thorough cleanup)
     
  43. sfortis

    sfortis New Member Member

    not working for me.
     
    Samuelheng likes this.
  44. paradoxa

    paradoxa New Member Member

    QoS is broken in any kind of way, it seems that everything gets detected as Default class.
    I also got a AC56U.
     
  45. brianli

    brianli New Member Member

    Hi Shibby,

    Thanks for your great work.
    I just installed the Tomato-R6300v2-ARM-134-AIO-64k to my Netgear R6300v2. However, I don't see any AC mode (Just Auto, A only, N only) under the 5GHz wireless network mode. Is it normal and what is the best settings for it. Thanks in advance.
     
  46. lefting

    lefting New Member Member

    Hi.
    Model Linksys E900 v1.0
    Chipset Broadcom BCM53572 chip rev 1 pkg 8

    Tomato Firmware 1.28.0000 MIPSR2-133 K26 Max

    After flashing the new firmware, deleted configuration and configured a new Dual WAN with static IP and password for WiFi all was ok, until power loss.
    After reboot WAN2 (port LAN1) is disconnected all the time but icon of the port is in connected state and WiFi Radio Disabled, but in the setup it is enabled.
    A sneaky URL has been detected in your content. Please check your content and remove anything that might look like a URL
     
    Last edited: Mar 16, 2016
  47. ryans1

    ryans1 Network Newbie Member

    Hello,

    I have an ASUS RT-N18U and flashed the tomato-RT-N18U-ARM--134-AIO-64K-NOSMP.
    I want to ask if it is an issue that, whenever I change any settings in the advanced wireless section, like transmit power, the PPPoE connection restarts.
    Also, when the PPPoE restart it dials twice, first connection lasts for about 5 seconds, disconnects, and then reconnects again. This happens every time I change a setting of the wireless and save it (and maybe not only in this case).

    Do you think you can check, and maybe fix, this?

    This is a log of my connections from my ISP:
    [​IMG]

    Thank you!
     
    Last edited: Mar 16, 2016
  48. Igorek

    Igorek Serious Server Member

    Found one bug, don't know how to repair it, every time I need to erase nvram.
    On Tomato Firmware 1.28.0000 -134 K26ARM USB VPN-64K after disabling L2TP and set wan port to static it leaves vpn's gateway, but in settings of wan port is local ip.
     

    Attached Files:

    • WAN.jpg
      WAN.jpg
      File size:
      56.2 KB
      Views:
      73
  49. eangulus

    eangulus Network Guru Member

    Just wanted to report some strange issues.

    As a background, I run heaps of the RT-AC66U, 68u etc with tomato in business and home environments.

    Yesterday I install 134 from 132, on my home (7 people, home business and 4 teens) RT-AC68U.

    I erased the NVRAM etc.

    After manually resetting everything up, I came into some issues. PS: the same config on 132 was working perfectly.

    1. I have a script for VPN Client where I route all traffic from selected IP's to the VPN all else is bypassed. Script also bypass only a selection of ports on the VPN directed IP's to bypass also. Solved this issue by checking the Redirect through VPN on Routing Policy Page. Never needed this before, so has something changed?

    2. QoS might be broken. Not sure exactly what's happening yet. Still trying to pin down.

    3. Related to QoS (or not), my pings seems all over the place. very erratic. Also my internet speed seems erratic also. After a reboot of the router, it seems to come good for a while but problems return after a few hours.

    4. Access Restriction isn't really working. I turned off internet access to all IP's except my desktop. THis is so I can get more accurate speed tests. My servers IP is directed over the VPN (with about 6 ports bypassing the VPN), but for some reason, there was still traffic going to the servers IP. It was real traffic to, not just router<->server (torrent traffic to be precise).



    Still uncertain if my problems are really the firmware or just glitches in config. But leaning more to the firmware. Once I finish configuring, I will wait for problems again, and then will switch back to 132 to see if I get same issues.


    If you need any logs etc, just let me know.
     
  50. KyleS

    KyleS Networkin' Nut Member

    You're not alone, I just got owned on 134.
     
  51. eangulus

    eangulus Network Guru Member

    I think the MultiWAN feature should have stayed in beta for a bit longer. To me this is still very much beta. 132 was allot better and much more stable.
     
  52. eangulus

    eangulus Network Guru Member

    One thing I can confirm. on RT-AC68U 134, the option Poll Interval in VPN Client, is only half working. It does the monitoring, and I can see that in the logs. It also correctly detects when the VPN is down. But it never restarts the VPN. I have to stop and start the VPN manually for it to return.
     
  53. eangulus

    eangulus Network Guru Member

    OK can anyone else confirm this. I think I found the problem with QOS.

    All classifications are working ok (mostly). WHen looking at the connection list everything is falling under the correct rules. When I look at the Pie charts thou, I see connections on various classifications. I also see bandwidth accross the classifications for Outbound.

    But Inbound traffic seem to be the problem. All bandwidth is going across the 1 class. Now I checked further, and realised all outbound is being routed over the default class setting. So I had default to crawl, all outbound traffic was on crawl, changed the default to service and all traffic went to service.
     
  54. paradoxa

    paradoxa New Member Member

    Confimed.
     
  55. eangulus

    eangulus Network Guru Member

    Thanks.

    I've given up. Couldn't make 134 usable, so have rolled back to 132 for now. Resetup from scratch with exactly the same settings. Now working perfectly. So definitely issues with 134.

    Now to patiently await 135 so I can try again.
     
  56. JohnK7

    JohnK7 New Member Member

    I have an RT-AC68U as well.
    I can confirm that QoS is not working properly on 134 build so I had to revert back.
    Also, in 132 build I have the issue with the USB3.0 port working with USB2.0 speed.
     
  57. Teddy Boom

    Teddy Boom New Member Member

    For my PPPoE session, I have to put VLAN tag of 35 on the WAN port. This works in release 124, 128 and 132, but doesn't work in 133. Tested on both RT-N53 and RT-N66U.

    Thanks for all the hard work, if any further testing would be helpful just let me know :)
     
  58. irwandi

    irwandi New Member Member

    Bug report for v133

    must setting DNSCrypt Option ( value not re-use on option, must set it every time )
    every time change something on page basic-network.asp

    hope you understand.
    Sorry For Bad English.
     
  59. Igorek

    Igorek Serious Server Member

    DNS is stopped respond, going back to 132. May be because I used "cache-size=2000", and after that is stopped, I removed it, reboot, and still not working.
     
  60. eangulus

    eangulus Network Guru Member

    Actually I noticed that too.

    I noticed that if you put in a cahce-size of any value, the logs showed that DHCPD keeps trying to start but fails.

    Seems that the custom value is conflicting with the built in cache-size=4096 instead of over riding it.
     
  61. jerrm

    jerrm Network Guru Member

    Many dnsmasq directives are like that. Duplicate entries will prevent dnsmasq from starting.

    If @shibby20 moved cache-size from the command line to the conf file it eliminates the ability to tune the option.

    Moving cache-size from command line to config file was discussed at length in http://www.linksysinfo.org/index.php?threads/tomato-arm-builds-w-inbound-qos.71285/

    My opinion on the matter is summed up here: http://www.linksysinfo.org/index.ph...builds-w-inbound-qos.71285/page-2#post-262224

    I'd have to think this is a regression, if @shibby20 changed his mind and wanted to go back to the conf file method, the GUI really needs to be updated.
     
  62. oldskool75

    oldskool75 New Member Member

    Hi
    Hi Shibby,

    Awesome work you do! :)

    Question, not specific to this build...
    I've been trying to set up l2tp/vpn using various guides (the one from dferg in particular (can't currently hyperlink.. sigh)).
    I'm told to download your extras from the v134 ARM (AC68U) release in order to get racoon working.

    But it seems that almost all guides say your extras package comes with the ipsec/aes.ko kernel module, but it doesn't seem to be in any of the tomato versions I've checked (in the ARM ones anyway).

    Do you not provide these for the arm distros?
    (Can you? :) )
     
  63. ierwin

    ierwin Serious Server Member

    Hey Shibby,
    v134 add support for R8000, But I didn't find the download link in K23ARM sub-folder. Where can I download the firmware? Thanks.
     
  64. eangulus

    eangulus Network Guru Member

    Can anyone confirm that QOS is working in 135?
     
  65. ptrakk

    ptrakk New Member Member

    just tried.. it's a negative with a rt-N12. last qos-working version was 130 for me. I'm pretty well versed at linux enabled machines.. I can only investigate it when my roommates are asleep. I just can't manage it with their sleep schedules. I don't wanna hear "WHY IS THE INTERNET DOWN!?" lol.. However, On version 133, it appeared that the /etc/iptables.restore which gets loaded as the /etc/iptables file wasn't being generated right. it didn't give a verbose error, but at least one of the lines in the generated iptables file were breaking it, so it didn't have an /etc/iptables file at all, and there was no routing, i suppose.


    The error was something along the lines of:
    Code:
    user.crit init[1]: Error while loading rules. See /etc/iptables.error file
    The iptables file with an error is saved as: /etc/iptables.error

    Earlier i had posted a working iptables file along side the error version. the erroneous version was missing some lines that had the word "return" in them compared to the working.. post #199 (working /etc/iptables from V.130) and #120 (non-working /etc/iptables.error from V.133) of this thread. there are a few differences in the file. I bet you can diff them.

    EDIT
    ---------------------------------------------
    Here's a diff generated:
    https://www.diffchecker.com/jmunvdx3

    the non working file is missing the line 12:
    -I QOSO 4 -m connmark ! --mark 0/0xff000 -j RETURN

    the nonworking file has the --set-mark parameter
    the working file has the --set-return parameter

    The nonworking file has a mask with 3 F's and the working has 2 F's in the hex address, ie 0xFFF & 0xFF. (line 8 and 91/93)

    May have been a typo in the source code somewhere?
     
    Last edited: Mar 22, 2016
  66. eangulus

    eangulus Network Guru Member

    I'm not that good with Linux to get that much info. Thanks for the effort tho.

    Last working QOS for me is 132. Have tried 134 and it was not applying the rules to incoming traffic. It was applying the default class setting.

    With a house of 7 including 5 kids, the net was unusable without the QOS working.
     
    sfortis likes this.
  67. txnative

    txnative Serious Server Member

    I didn't see a E3200 build in v135 in the K26RT-N folder? I was also curious if Qos was working in this version too, as it didn't in the beta v133 but I see in the previous posts that it may have been answered. I am also using v132 for my E3200 in which it is stable. It is a matter of time to get the bugs out thanks for the hard work Sir
     
  68. WaJoWi

    WaJoWi Connected Client Member

    My 3G Stick now works principally with version 135. If WAN1 fails, the router switched to WAN2 (the stick) and made the connection. But every minute is disconnected and rebuilt. It takes each time less than 10 seconds.

    If WAN1 made available again, although the connection is detected, but the data passed on via WAN2. The connection will be rebuilt every minute also on WAN1. It helped only a reset of the router.

    This is a shame, because I can not use multi-WAN. :-(

    Should work Multi-WAN once, it would also be good if DDNS is not only the IP WAN monitored, but the active WAN port (WAN1 - WAN4). Would that be possible?
     
  69. gkhicks

    gkhicks Network Newbie Member

    Shibby,

    Thanks for your continued work!

    I've loaded v1.35 for my Asus RT-NT16... and the PPoE function for my WAN is still not working (all is OK on v1.32)... so no session can be established to check further. It just indicates "RENEWING"... never connects.

    Thanks.
     
  70. ryans1

    ryans1 Network Newbie Member

    Is there any problem with IPv6 SLAAC module? Because my phone keeps disconnecting from my wifi, and if I look into the logs I keep getting the following messages:

    Code:
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: SLAAC-CONFIRM(br0) <ipv6 address>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: RTR-ADVERT(br0) <ipv6 address>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: DHCPREQUEST(br0) 192.168.1.6 <MAC>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: DHCPACK(br0) 192.168.1.6 <MAC>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: RTR-SOLICIT(br0) <MAC>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: RTR-ADVERT(br0) <ipv6 address>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: SLAAC-CONFIRM(br0) <ipv6 address>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: DHCPREQUEST(br0) 192.168.1.6 <MAC>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: DHCPACK(br0) 192.168.1.6 <MAC>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: RTR-SOLICIT(br0) <MAC>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: RTR-ADVERT(br0) <ipv6 address>
    RT-000000000001 daemon.info dnsmasq-dhcp[23373]: SLAAC-CONFIRM(br0) <ipv6 address>
    Everytime there is a SLAAC-CONFIRM message, my wifi drops and re-connects. If I disable the IPv6 feature, the problem goes away. Is there a problem with dnsmasq or with the firmware?

    Thank you!
     
  71. typhoe

    typhoe New Member Member

    Hi,

    try to enclose your pppoe user and password with simple quote 'user' / 'passwd' in the web page field.
    I encounter the same problem and had chap authentification error in the log with v135 on my RT-AC68U.
    That did the trick.

    Regards.
     
  72. gkhicks

    gkhicks Network Newbie Member

    Thanks, typhoe... but that didn't correct the PPPoE issue... still fails to validate... and leaves state in RENEWING.
     
  73. typhoe

    typhoe New Member Member

    Ok, too bad. It was worth trying, it worked for me.
    Just in case, do you also need to change the VID/Vlan for the WAN?
     
  74. shadowro

    shadowro Serious Server Member

    if upgrading from 132, do we have to erase nvram after upgrade? (I might sound stupid but don't want to break what's working like a charm)
    In changelog, I only see for 133 - Attention: You have to erase nvram after upgrade!!
    thank you.
     
  75. ptrakk

    ptrakk New Member Member

    Jeez, full load! Linux is a lot of practice. I haven't tried 132..


    sometimes when ipv6 is set the device will prefer it over the ipv4. when a device(especially phones) can't access the internet/dns with the ipv6 it will disconnect from the network as an attempt to roam. perhaps the ipv6 isn't set up right? i don't use it and haven't tried setting up ipv6.



    yes. The nvram has different variables between the two systems.. you can back up the nvram by using the 'nvram show' system command. then paste it into notepad or redirect it to a file, then set the values individually using 'nvram set <key> <value>' command .
     
  76. jochen

    jochen Network Guru Member

    Hi,
    since version 133-135 I have the problem that Chromecast is not found by Chromecast Android smartphone app. Looks like broadcasts over wifi don't work. I had to revert to version 132 to get it working again.
     
  77. meazz1

    meazz1 LI Guru Member

    I have installed 135 K26ARM USB AIO in my Asus RT-AC56U router. My ISP is Comcast.
    I had been using 132 K26ARM USB AIO before upgrading to firmware version 135.
    This one is Multiwan supported FW.
    Now here comes my ignorance ( i googled it but didn't understand it).
    1. What is a multiwan firmware and if there is any benefit for me having only one ISP right now?
    2. Under WAN settings, what is a "Wireless Client Mode" with option of "Disable, 2.4 GHz / eth1 & 5 GHz/eth2"?

    I included a screenshot for question #2.

    Screenshot from 2016-03-25 19:04:12.png Screenshot from 2016-03-25 19:04:12.png
     
  78. sfortis

    sfortis New Member Member

    no benefits from 1 ISP. Im wondering why so much developing effort (from Shibby actually) for a feature that less than 1% of the users will utilize.

    i'll stick with single WAN v.132 since after then QoS is broken!
     
    Samuelheng and meazz1 like this.
  79. remlei

    remlei Networkin' Nut Member

    how about stay on v132 for a while till it stabilize, no one forcing you to upgrade anyway and its like youre not taking advantage the new features anyway and there no critical update that you need to be concerned of.

    I still have a router running v121 back then until shibby release a multiwan firmware for RT-N routers, it may prove useful for me for my 2 ISP (1fiber and 1DSL), didnt bother upgrading my firmware back then because theres no updates that I need to be concern of, not even a security update.
     
    Samuelheng likes this.
  80. AndreDVJ

    AndreDVJ Addicted to LI Member

    That's exactly the reason Tomato is open source. Tomato isn't bound to external demand. Shibby's goal is to make his mods feature-rich as possible. More lines of code means it's more prone to break somewhere.
     
  81. TripitakaBC

    TripitakaBC New Member Member

    Need a little help here. I've been using Shibby builds for a good while but I'm not an active 'tinkerer'. I'm building an internet setup for my travel trailer so I can work on the road and I figured that an RT-N66U with the MultiWAN build would do the job nicely. I looked at the MoFi and Cradlepoint offerings but I couldn't see what they offered me over the Asus and MultiWAN. Well, I see what the Cradlepoint offers - dual sim cards with auto-routing and failover between them - but that isn't a priority for me. Anyway, I digress...

    I've got the 135 MultiWAN up and running. I'm using the 5GHz as a wireless client linking to my home network and that bridges over to a different SSID on the 2.4GHz wireless. So far, so good.

    I'm falling flat when trying to get the cellular connection up and running. I'll soon be running some Ubiquiti directional kit that will plug into the WAN port when required (long-range, directional wifi) so I allocated WAN2 for the USB cellular connection. All set up, configured for 4G/LTE but it just sits there and never connects.

    I suspect that the issue may be that I am trying to get it to connect via a cell phone tethered to the USB rather than a 'stick' dongle. Log files suggest that a driver may be required that is missing but I've run out of things to Google to get past it. Any and all help is gratefully received. Phones are both Android, Sony Xperia Z3 and Samsung Galaxy Note 4.

    It may be a setting or it may just not work with cell phones vs dongles but either way, I need to get past it.

    Thanks.
     
  82. Xruptor

    Xruptor Connected Client Member

    I can confirm for RT-N66U that QOS is broken with MultiWAN v 135. The moment you turn it on it kills all the WAN activity and sets it as default for some reason. When you turn off QOS the internet works perfectly fine. I've had to revert back to v132 as QOS is very important in my house.

    Will go back to MultiWAN v135 once this has been addressed. QOS was the only thing that was broken for me, everything else worked perfectly fine.
     
  83. eelstrebor1

    eelstrebor1 Network Newbie Member

    The link from my router brought me here but this doesn't seem to apply to me since I don't need multiWAN support. Anyway, do I have to clear the nvram to install tomato-EA6900-ARM--133-AIO-64K.trx? If so, how do I restore my settings in an automated way or am I gonna have to restore everything manually? If I have to restore the settings manually I won't upgrade even though the upgrade might fix an issue with the openvpn server (doesn't show what clients are attached - /var/log/openvpn-status shows the clients though).
     
  84. Jose C

    Jose C Connected Client Member

    You need to do it manually


    Sent from my iPad using Tapatalk
     
  85. ferdinandpc

    ferdinandpc Connected Client Member

    Hi, I install the v135 in a R7000 and configure the vlan that my ISP need and the wan doesn't connect, it's always renewing. I have to back to v132.
     
    IcyTexx likes this.
  86. theirongiant

    theirongiant Serious Server Member

    With QoS enabled, the following parts are functioning correctly:

    - Measuring the flow of traffic;
    - Classification of traffic;
    - Details, transfer rates, display filtering;
    - Connection Distribution pie chart.

    Things that do not work:

    - Actually shaping the traffic according to the classification & speed rules;
    - When using "zoom graphs," the Bandwidth Distribution charts do not scale correctly and have NaN% everywhere. I'm sure it's a simple oversight.
     
  87. theirongiant

    theirongiant Serious Server Member

    Hey @shibby20 , in lines 41-42 of /www/qos-graphs.asp the following variables are loaded from NVRAM:

    Code:
    <script type='text/javascript'>
    
    // <% nvram("qos_classnames,web_svg,qos_enable,qos_obw,qos_ibw"); %>
    
    //<% qrate(); %>
    

    And here is how the code appears in the browser:

    Code:
    <script type='text/javascript'>
    //
    nvram = {
    'qos_classnames': 'Service VOIP/Game Remote WWW Media HTTPS/Msgr Mail FileXfer P2P/Bulk Crawl',
    'web_svg': '1',
    'qos_enable': '1',
    'qos_obw': '',
    'qos_ibw': '',
    'wl_unit': '0',
    'http_id': 'TIDc1e37de6e9d455a0',
    'web_mx': 'status,bwm',
    'web_pb': ''};
    
    //
    

    I suppose that the NaN% bug in the QoS graph page is caused by variables qos_obw and qos_ibw having null values.
     
    Last edited: Apr 3, 2016
    shibby20 and koitsu like this.
  88. mauriga

    mauriga New Member Member

    I need some help.
    I uptated my 132 (no multiwan) to 135 multiwan version.
    Everything works well except the Transmission download speed (one half than before).

    The problem is my WAN settings. My subnet mask is always 0.0.0.0 I tryed to put it on 255.255.255.0 and save, but it always go back to 0.0.0.0

    Tnx in advance for any suggestion.

    mau----
     
  89. shibby20

    shibby20 Network Guru Member

    this is a bug in v135.

    v136 for ARM router has been released today. Mipsel`s version should be ready for few days.
     
  90. mauriga

    mauriga New Member Member

    Great!
    Coz Im a newbye, have I to erase nvram before or after uptading?

    Tnx

    mau----
     
  91. theirongiant

    theirongiant Serious Server Member

    If you're already running the MultiWAN edition, then no—just upgrade in place. If you're using the standard edition and want to switch to MultiWAN, then YES you have to erase the NVRAM.
     
  92. pegasus123

    pegasus123 Networkin' Nut Member

    is the bug wherein, no conntrack showing under qos fixed? I'm running R7000
     
  93. rogueosb

    rogueosb New Member Member

    Both versions 135 and 136 cause my internet status to stick at "Renewing...". The internet itself works, except no port forwarding works, so my home server is completely inaccessible. Reverting to 134 fixes the issue.
     
  94. shibby20

    shibby20 Network Guru Member

    What is your WAN mode? PPPoE? if so, then try uncheck an option "Use DHCP" under PPPoE configuration. This option should be disabled by default in v136 so probably you didn`t erase nvram after upgrade your router.

    If you have R7000 then you have to erase nvram. Otherwise you can (try to) leave your settings.
     
  95. rogueosb

    rogueosb New Member Member

    That was it, I didn't notice the new option. Everything working fine on v136 now. Thanks!
     
  96. eangulus

    eangulus Network Guru Member

    What about QoS?
     
  97. shibby20

    shibby20 Network Guru Member

    with one WAN should works correct. QoS will not work when WAN Number is bigger than 1.
     
  98. brianli

    brianli New Member Member

    Hi Shibby,
    Thanks for the new build v.136. I just flashed it from v132 of my Linkysis E3200, however, it doesn't work for the PPTP client. I already did the NVRAM erase after the upgrade.
    I flashed back to v132 and everything works back perfectly.
    Just would like to let you know.
     
  99. bionor

    bionor Reformed Router Member

    Hi. I went from 128 to 136 just now and only after upgrading did i read all of the changelog and did not see the requirement to delete NVRAM until after it upgraded. Everything seems to be working, I'm connected to the 'net as u can see, but I have not changed any settings or done any tinkering yet. Can I expect any problems? I'm a bit worried, so any info would be appreciated. I'm on RT-N66U 64 BTW
     
  100. amaury nogueira

    amaury nogueira New Member Member

    Hello Shibby,
    Thanks for the new build v.136. I just flashed it from v132 of my Linkysis E900, however, it doesn't work for the full download. I'm using version 136. I have two wans with 15mb each (= 30mb), but the download speed does not exceed 15mb. What am I doing wrong?
     

Share This Page