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

Wireless and Multicast

Discussion in 'Tomato Firmware' started by Zodler, Nov 19, 2012.

  1. Zodler

    Zodler Serious Server Member

    I have a headache! My wireless suddenly over night stopped working.

    I have a new Linksys E2000 with tomato-E2000-NVRAM60K-1.28.7500.4MIPSR2Toastman-RT-Std firmware. Everything worked well until now.

    I have an iPad 2 and iPhone 4S. Since this morning they can't join the network. It worked for 2 weeks.

    I tried everything I can think of. I restarted the router and my ipad/iphone. I tried to forget the network and re-enter the password. Sometimes it says its connected but no data can come in. I don't know how to debug this. Is my new 2 weeks old router dying? I also tried different manual channels (I am in France). I really don't know what has happened during the night! How can I pin point where the problem is? Should I change the router?

    [​IMG]
     
  2. koitsu

    koitsu Network Guru Member

    Multiple things:

    1. Did you adjust any settings, at any time (even prior to 2 weeks ago), in Advanced -> Wireless, Advanced -> Miscellaneous, or Basic -> Wireless Filter? If so, what did you adjust?

    2. From Tools -> System please run the command dmesg and copy-paste the results here (and please put them in a {code} block (use brackets not braces)). Wireless driver errors will show up in this log, and knowing how to discern what's an error vs. what's normal requires familiarity with the messages.

    3. Reboot your devices. I know not ideal, but please do it anyway. Then continue on.

    4. Perform a network/SSID scan on one of your devices. Do they see the SSID of your network? If so, then the wireless chip in the router is still functional to some degree.

    5. Change Channel Width to 20MHz and attempt device reconnects.

    6. If #5 doesn't work, keep Channel Width at 20MHz and choose Channel -> Scan and find a channel number that has the least number of APs associated with it. Then change the pulldown to select that Channel number, then attempt device reconnects.

    7. If #6 doesn't work, keep Channel Width at 20MHz and the Channel you chose from #5, and disable Security. I know this isn't ideal, but it's a temporary test. Then attempt device reconnects (devices will also need to be reconfigured to not use WPA2).

    If none of this improves anything, you might try the same Toastman build but for RT-N (different/newer wireless driver, but still considered experimental). You will need to perform a thorough NVRAM clear after changing the firmware (Administration -> Configuration -> Restore Default Config -> Erase all data in NVRAM (thorough)). To restore all of your router settings, do not use the Restore Configuration option; instead you should write down all of the settings you change from factory defaults (I tend to put them all in a .txt file), and re-apply them manually. (The reason for this is that Restore Configuration will re-introduce any NVRAM variables/contents which may be somehow corrupt or bad).

    If you do change firmwares, repeat the above testing starting with #7 and work backwards through the steps (i.e. start with no security + 20MHz + static channel, then if that works, enable WPA2 Enterprise + AES, keep 20MHz + static channel, etc. etc...). Take notes in case you think you may have missed something along the way.

    If you get to the point where you've got everything working again and you want to change Channel Width back to 40MHz -- please don't. We've been discussing the horrid situation with wireless today (40MHz vs. 20MHz, 2.4GHz vs 5GHz, etc.) in a different thread and you're welcome to read it (from the post I linked downward). It's somewhat technical, but what to take away from it is to please not use 40MHz. I know that limits your bandwidth and I'm sorry, but if you're in a dense area where lots of other APs in the 2.4GHz band are seen, I wouldn't be surprised by your issue. (There's also a good chance you're crapping all over other peoples' wireless in the process.) The specific article I'm referring to is this. Too Lazy ; Don't Want To Read? Keep 20MHz.

    If none of this solves the problem, sure, replace the router. There are confirmed reports of the E2000 and E3000 series routers overheating (one fellow confirmed this by turning the router upside down (ventilation holes are on the bottom) and pointing a desk fan at it), so keep that in mind too.
     
  3. Zodler

    Zodler Serious Server Member

    Ok I have been able to pin point when the problem starts. It's with my ADSL TV.
    http://www.linksysinfo.org/index.php?threads/neuf-trio-3d-modem-help-with-qos.53591/#post-206849

    I use a switch to input my ADSL TV and Internet into the WAN of my Linksys E2000. After days I found out that it's because of ADSL TV.

    Whenever my ADSL TV is on, my wireless doesn't work anymore. My iphone and ipad don't connect to the network and if they do, no data is able to transfer. If I turn off the TV, after few seconds they are able to connect and transfer data again!

    I have enabled IGMPproxy in Advanced->Firewall for the TV to work. This is a major problem for me. I need both of them to work at the same time!
     
  4. bmupton

    bmupton Serious Server Member

    So you go:
    ISP Modem LAN port
    |
    Switch -------- ADSL TV
    |
    --------------- WAN Linksys E2000 LAN -------- Wireless Devices

    ?

    If that's the case, I don't think you'd need IGMPProxy on the E2000. Or do you have the TV connected to a LAN port of the E2000? If so, try moving it from behind the E2000 like my above diagram and disable IGMPProxy.

    I had IPTV at home for the longest time, and I *could not* put my TV set top boxes behind my E3000...they simply refused to work, so I used the above solution. In my case though, the IPTV boxes and my LAN didn't have any reason to talk to one another, so this worked fine for me.
     
  5. Zodler

    Zodler Serious Server Member

    [​IMG]

    Red and Blue -> switch -> WAN E2000. Internet and ADSL TV is on the same modem. I have to enable IGMPProxy. TV will not work without it.

    One of the Lan of E2000 goes to a TV receiver of course. I can connect the RED directly to TV receiver or connect to the switch but I want the TV pass through WAN so that QOS can control it.
     
  6. Zodler

    Zodler Serious Server Member

  7. bmupton

    bmupton Serious Server Member

    Now I see what you're trying to accomplish...

    I never did get mine to work like that, and mine was even simpler..My IPTV and my Internet line were separate, so QoS wasn't as issue for me.

    Sorry mate!
     
  8. koitsu

    koitsu Network Guru Member

  9. Zodler

    Zodler Serious Server Member

    I just tried shibby's firmware again tomato-E2000-NVRAM60K-1.28.RT-MIPSR2-102-Max
    just to be sure and the same wifi problem is there too.

    I would like to solve this and keep igmpproxy enabled. The whole point of this is to pass the TV through WAN and let QOS manage things. If I disable igmpproxy, it makes no sense for me to use tomato, because depending on if my TV is on or off, my Internet speed will be different and QOS will be useless.
     
  10. Zodler

    Zodler Serious Server Member

    Since my LANs work, I was thinking of getting some wireless device that I can connect with wire to a LAN port of my E2000. Any suggestions?
     
  11. Zodler

    Zodler Serious Server Member

    Code:
    Linux version 2.6.22.19 (root@tomato) (gcc version 4.2.4) #15 Wed Aug 15 12:05:30 ICT 2012
    CPU revision is: 00019740
    Found a 8MB ST compatible serial flash
    Determined physical RAM map:
    memory: 02000000 @ 00000000 (usable)
    Entering add_active_range(0, 0, 8192) 0 entries of 256 used
    Zone PFN ranges:
      Normal          0 ->    8192
      HighMem      8192 ->    8192
    early_node_map[1] active PFN ranges
        0:        0 ->    8192
    On node 0 totalpages: 8192
      Normal zone: 0 pages used for memmap
      Normal zone: 0 pages reserved
      Normal zone: 8192 pages, LIFO batch:1
      HighMem zone: 0 pages used for memmap
    Built 1 zonelists.  Total pages: 8192
    Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
    Primary data cache 32kB, 4-way, linesize 32 bytes.
    Synthesized TLB refill handler (20 instructions).
    Synthesized TLB load handler fastpath (32 instructions).
    Synthesized TLB store handler fastpath (32 instructions).
    Synthesized TLB modify handler fastpath (31 instructions).
    PID hash table entries: 256 (order: 8, 1024 bytes)
    CPU: BCM4716 rev 1 pkg 9 at 354 MHz
    Using 177.000 MHz high precision timer.
    console [ttyS0] enabled
    Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
    Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
    Memory: 28636k/32768k available (33k kernel code, 4116k reserved, 2669k data, 124k init, 0k highmem)
    Calibrating delay loop... 176.53 BogoMIPS (lpj=882688)
    Mount-cache hash table entries: 512
    NET: Registered protocol family 16
    PCI: Using membase 8000000
    PCI: Disabled
    PCI: Fixing up bus 0
    PCI: Fixing up bus 1
    NET: Registered protocol family 2
    Time: MIPS clocksource has been installed.
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 1024 (order: 1, 8192 bytes)
    TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
    TCP: Hash tables configured (established 1024 bind 1024)
    TCP reno registered
    squashfs: version 3.0 (2006/03/15) Phillip Lougher
    io scheduler noop registered (default)
    HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
    N_HDLC line discipline registered.
    Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
    serial8250: ttyS0 at MMIO 0xb8000300 (irq = 8) is a 16550A
    PPP generic driver version 2.4.2
    MPPE/MPPC encryption/compression module registered
    NET: Registered protocol family 24
    PPPoL2TP kernel driver, V0.17
    PPTP driver version 0.8.5
    pflash: found no supported devices
    Creating 5 MTD partitions on "sflash":
    0x00000000-0x00040000 : "pmon"
    0x00040000-0x007f0000 : "linux"
    0x00123c00-0x00450000 : "rootfs"
    0x00450000-0x007f0000 : "jffs2"
    0x007f0000-0x00800000 : "nvram"
    u32 classifier
        OLD policer on 
    Netfilter messages via NETLINK v0.30.
    nf_conntrack version 0.5.0 (512 buckets, 4096 max)
    ip_tables: (C) 2000-2006 Netfilter Core Team
    ipt_account 0.1.21 : Piotr Gasidlo <quaker@barbara.eu.org>, http://www.barbara.eu.org/~quaker/ipt_account/
    net/ipv4/netfilter/tomato_ct.c [Aug 15 2012 12:00:48]
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    ip6_tables: (C) 2000-2006 Netfilter Core Team
    NET: Registered protocol family 17
    802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
    All bugs added by David S. Miller <davem@redhat.com>
    VFS: Mounted root (squashfs filesystem) readonly.
    Freeing unused kernel memory: 124k freed
    Warning: unable to open an initial console.
    emf: module license 'Proprietary' taints kernel.
    PCI: Setting latency timer of device 0000:00:02.0 to 64
    eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.10.147.0
    PCI: Setting latency timer of device 0000:00:01.0 to 64
    eth1: Broadcom BCM4328 802.11 Wireless Controller 5.10.147.0
    Algorithmics/MIPS FPU Emulator v1.5
    vlan1: add 33:33:00:00:00:01 mcast address to master interface
    vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    vlan1: dev_set_allmulti(master, 1)
    vlan1: dev_set_promiscuity(master, 1)
    device eth0 entered promiscuous mode
    device vlan1 entered promiscuous mode
    device eth1 entered promiscuous mode
    br0: port 2(eth1) entering forwarding state
    br0: port 1(vlan1) entering forwarding state
    vlan2: Setting MAC address to  58 6d 8f 02 ae 93.
    vlan2: add 33:33:00:00:00:01 mcast address to master interface
    vlan2: add 01:00:5e:00:00:01 mcast address to master interface
    IMQ starting with 3 devices...
    IMQ driver loaded successfully.
        Hooking IMQ after NAT on PREROUTING.
        Hooking IMQ before NAT on POSTROUTING.
    vlan2: del 01:00:5e:00:00:01 mcast address from vlan interface
    vlan2: del 01:00:5e:00:00:01 mcast address from master interface
    vlan2: del 33:33:00:00:00:01 mcast address from vlan interface
    vlan2: del 33:33:00:00:00:01 mcast address from master interface
    br0: port 2(eth1) entering disabled state
    br0: port 1(vlan1) entering disabled state
    vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
    vlan1: del 01:00:5e:00:00:01 mcast address from master interface
    vlan1: del 33:33:00:00:00:01 mcast address from vlan interface
    vlan1: del 33:33:00:00:00:01 mcast address from master interface
    device vlan1 left promiscuous mode
    br0: port 1(vlan1) entering disabled state
    device eth1 left promiscuous mode
    br0: port 2(eth1) entering disabled state
    vlan1: add 33:33:00:00:00:01 mcast address to master interface
    vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    device eth1 entered promiscuous mode
    br0: port 2(eth1) entering forwarding state
    br0: port 1(vlan1) entering forwarding state
    vlan2: Setting MAC address to  58 6d 8f 02 ae 93.
    vlan2: add 33:33:00:00:00:01 mcast address to master interface
    vlan2: add 01:00:5e:00:00:01 mcast address to master interface
    vlan2: del 01:00:5e:00:00:01 mcast address from vlan interface
    vlan2: del 01:00:5e:00:00:01 mcast address from master interface
    vlan2: del 33:33:00:00:00:01 mcast address from vlan interface
    vlan2: del 33:33:00:00:00:01 mcast address from master interface
    br0: port 2(eth1) entering disabled state
    br0: port 1(vlan1) entering disabled state
    vlan1: dev_set_promiscuity(master, 1)
    vlan1: dev_set_allmulti(master, 1)
    vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
    vlan1: del 01:00:5e:00:00:01 mcast address from master interface
    vlan1: del 33:33:00:00:00:01 mcast address from vlan interface
    vlan1: del 33:33:00:00:00:01 mcast address from master interface
    device vlan1 left promiscuous mode
    br0: port 1(vlan1) entering disabled state
    device eth1 left promiscuous mode
    br0: port 2(eth1) entering disabled state
    vlan1: add 33:33:00:00:00:01 mcast address to master interface
    vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    device eth1 entered promiscuous mode
    br0: port 2(eth1) entering forwarding state
    br0: port 1(vlan1) entering forwarding state
    vlan2: Setting MAC address to  58 6d 8f 02 ae 93.
    vlan2: add 33:33:00:00:00:01 mcast address to master interface
    vlan2: add 01:00:5e:00:00:01 mcast address to master interface
    vlan2: del 01:00:5e:00:00:01 mcast address from vlan interface
    vlan2: del 01:00:5e:00:00:01 mcast address from master interface
    vlan2: del 33:33:00:00:00:01 mcast address from vlan interface
    vlan2: del 33:33:00:00:00:01 mcast address from master interface
    br0: port 2(eth1) entering disabled state
    br0: port 1(vlan1) entering disabled state
    vlan1: dev_set_promiscuity(master, 1)
    vlan1: dev_set_allmulti(master, 1)
    vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
    vlan1: del 01:00:5e:00:00:01 mcast address from master interface
    vlan1: del 33:33:00:00:00:01 mcast address from vlan interface
    vlan1: del 33:33:00:00:00:01 mcast address from master interface
    device vlan1 left promiscuous mode
    br0: port 1(vlan1) entering disabled state
    device eth1 left promiscuous mode
    br0: port 2(eth1) entering disabled state
    vlan1: add 33:33:00:00:00:01 mcast address to master interface
    vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    device eth1 entered promiscuous mode
    br0: port 2(eth1) entering forwarding state
    br0: port 1(vlan1) entering forwarding state
    vlan2: Setting MAC address to  58 6d 8f 02 ae 93.
    vlan2: add 33:33:00:00:00:01 mcast address to master interface
    vlan2: add 01:00:5e:00:00:01 mcast address to master interface
    vlan2: dev_set_allmulti(master, 1)
    vlan2: add 01:00:5e:08:00:83 mcast address to master interface
    vlan2: del 01:00:5e:08:00:83 mcast address from master interface
    vlan2: add 01:00:5e:08:00:83 mcast address to master interface
    vlan2: del 01:00:5e:08:00:83 mcast address from master interface
    vlan2: add 01:00:5e:08:00:83 mcast address to master interface
    vlan2: del 01:00:5e:08:00:83 mcast address from master interface
    vlan2: dev_set_allmulti(master, -1)
    vlan2: dev_set_allmulti(master, 1)
    vlan2: add 01:00:5e:08:00:83 mcast address to master interface
    vlan2: del 01:00:5e:08:00:83 mcast address from master interface
    vlan2: dev_set_allmulti(master, -1)
    vlan2: dev_set_allmulti(master, 1)
    vlan2: add 01:00:5e:08:00:83 mcast address to master interface
    vlan2: del 01:00:5e:08:00:83 mcast address from master interface
    vlan2: add 01:00:5e:08:00:83 mcast address to master interface
     
  12. Zodler

    Zodler Serious Server Member

    Interesting. I just tried another firmware. No tomato. I just tried dd-wrt and I get the exact same problem.

    In dd-wrt I have to disable Filter Multicast for the ADSL TV to work. When its on, I have the same wireless non-connection as tomato!!!? How come? Are they both based on the same source code?

    Can an admin change the title of this topic to "Wireless and Multicast" now that we know the cause?
     
  13. Zodler

    Zodler Serious Server Member

  14. Ken Anderson

    Ken Anderson Serious Server Member

    I had the same issue with RT-N16, apple TV and BluRay player . After spending several hours and trying different firmwares, if eventually began to notice that my router would have wifi issues when either apple TV or BluRay player were on. I had the router right next to both.
    I was able to see wifi, but unable to join or do anything with it.

    I moved the router a few feet away from both devices.
    There must be some radio interference being emitted from both.
     
  15. Zodler

    Zodler Serious Server Member

    Is it possible to execute these under tomato?
    insmod ebtables
    insmod ebtable_filter
    insmod ebt_pkttype
    ebtables -A FORWARD -o eth1 --pkttype-type multicast -j DROP
    ebtables -A OUTPUT -o eth1 --pkttype-type multicast -j DROP
     
  16. koitsu

    koitsu Network Guru Member

    You probably don't need to run the insmod commands -- using said features should automatically load the relevant modules (equivalent to modprobe). lsmod will show you what's loaded. Be aware that some things may be compiled in to the kernel statically thus won't show up in lsmod.

    ebtables, ebtable_filer, and ebt_pkttype are all supported modules under TomatoUSB (meaning you will find them as part of netfilter under /lib/modules/2.6.22.19/kernel/net/bridge/netfilter). No idea if they're compiled in statically, but given their existence on the filesystem, I would say they're dynamic.

    Good luck.
     
  17. Zodler

    Zodler Serious Server Member

    Wow, what an adventure. After a full week working on this and trying many things I finally got it to work on tomato. I had put dd-wrt and was working on it for a few days. I was able to achieve this on dd-wrt with 2 methods but I didn't like dd-wrt and was looking for a way to come back to tomato. I like all the graphs and looks of tomato and I got a QOS configured that worked nicely on it.

    As it turns out the solution on tomato is even easier. You go to Advanced->Wireless and you see Multicast Rate set to Auto. If you change it to 9Mbps for example, now your wireless works even with IPTV on! I have no idea what it does!

    Now that's not all. I have found out an even simpler solution on tomato. In the same page without touching Multicast Rate (set to Auto), you go to Wireless Multicast Forwarding. It is Disabled, you enable it and your wireless starts to work.

    However this must be a bug. They have reversed the values in Wireless Multicast Forwarding. Disabled means its actually on and that's why wireless gets flooded and doesn't work. Enabled means its off and no Multicast is sent to Wireless. I think this should be reported to whoever develops this.
     
  18. Monk E. Boy

    Monk E. Boy Network Guru Member

    What probably happened is either that function changed at one point, or someone misinterpreted what it meant and flipped the meaning around in the text. A lot (most?) of the driver's functionality is poorly documented by Broadcom, at least for people who haven't signed an NDA

    From your description it sounds like that setting either enables or disables a filter for multicast traffic (you're effectively disabling/enabling multicast traffic over wireless). Setting a rate limits the amount of multicast traffic sent over the wireless link, instead of blocking it with the filter.

    Good job figuring this out.
     
  19. koitsu

    koitsu Network Guru Member

    I'd like to review the code to see what this setting in the GUI actually does on the system itself. I see no wireless multicast forwarding options within wl itself (I do see multicast options, but not forwarding-related), so I'm inclined to think this is a Linux kernel setting and/or something relating to igmpproxy. But I'd need to review the code to see if the option is truly mislabelled or if it's just an interpretation issue.
     
  20. koitsu

    koitsu Network Guru Member

    The GUI feature Wireless Multicast Forwarding correlates with the NVRAM variable wl_wmf_bss_enable. The values for this variable are 0 and 1, where 0 means disabled (and is the default value) and 1 means enabled.

    Relevant code bits:

    release/src-rt/router/nvram/defaults.c
    release/src-rt/router/httpd/tomato.c
    release/src-rt/router/www/advanced-wireless.asp
    release/src/router/nvram/defaults.c
    release/src/router/httpd/tomato.c
    release/src/router/www/advanced-wireless.asp

    The problem is that I can't find any other references to this NVRAM variable anywhere in the code, which means this is a special variable within the binary-blob Broadcom wireless driver which has no source code. Sure enough:

    Code:
    root@gw:/lib/modules/2.6.22.19/kernel/drivers/net# strings wl.ko | grep wmf_bss_enable
    wmf_bss_enable
    
    Please note that there's no wl_ at the start -- I'll get to that in a moment.

    It looks like this setting was discussed back in 2011 here:

    http://www.linksysinfo.org/index.php?threads/new-victek-releases.33910/page-13#post-173575
    http://www.linksysinfo.org/index.ph...ases-up-to-1-28-7492.34549/page-5#post-173396

    Based on this, I am of the opinion that the variable is in fact named correctly -- a value of 0 = Disabled, and a value of 1 = Enabled. Proof of this fact is in those threads, where one user was able to get IPTV working just fine after he set the value to 1. But keep reading -- there is something interesting about this situation and the NVRAM variable in question. Here it comes:

    Code:
    root@gw:/tmp/home/root# nvram show | grep wmf_bss
    wl0_wmf_bss_enable=0
    wl_wmf_bss_enable=0
    
    So here we have two NVRAM variables. If I had to guess what this is about, it would be that the one named wl0 refers to the per-unit/per-interface setting (i.e. wireless unit 0), while the wl_ one refers to all wireless interfaces globally. Looking at release/src-rt/router/www/advanced-wireless.asp I can see the following code:

    Code:
    117         var u = wl_unit(uidx);
    ...
    130         createFieldTable('', [
    ...
    199         { title: 'Wireless Multicast Forwarding', name: 'wl'+u+'_wmf_bss_enable', type: 'select', options: [['0','Disable *'],['    1','Enable']],
    200                 value: nvram['wl'+u+'_wmf_bss_enable'] }
    201         ]);
    
    So the GUI adjusts wl0_wmf_bss_enable, not wl_wmf_bss_enable.

    The users who report success in getting IPTV working were setting the non-unit variable manually, i.e.:

    Code:
    nvram set wl_wmf_bss_enable=1
    nvram commit
    
    So possibly the problem here is that there's a logic inversion issue in the driver of some sort (i.e. two variables doing the same thing, effectively, where certain combinations of values (0+0, 0+1, 1+0, 1+1) cause the feature to get disabled or enabled incorrectly). Again we don't know because it's a binary blob driver.

    There's really nothing we can do about this other than try to harass Asus or Broadcom or someone about it and ask for an explanation.

    While I'm here: can someone please explain to me why the wlX unit nomenclature in NVRAM is needed? Are there actually routers out there which have multiple wireless units in them (i.e. wl0 and wl1 exist on the same router)?
     
    PBandJ likes this.
  21. Zodler

    Zodler Serious Server Member

    By the way, for your information I tried Wireless Multicast Forwarding on 2 routers, Linksys E2000 and Asus RT-N66U and both needed to be set to enabled to do the opposite!
     
  22. koitsu

    koitsu Network Guru Member

    I believe you, but as of this time I have to disagree with the belief that the option description is reversed (0=enabled, 1=disabled), because there's proof otherwise in those 2 threads (especially the 2nd, with actual screenshots).

    So the bottom line is that Disabled works for some people, while Enabled works for others. That's all we know at this point.

    Welcome to closed-source drivers.
     
  23. Zodler

    Zodler Serious Server Member

    The guy you referenced, typed it directly in the system. I used the GUI. Maybe its the GUI?
     
  24. koitsu

    koitsu Network Guru Member

Share This Page