OpenWrt Forum Archive

Topic: davidc502 1900ac 3200acm builds

The content of this topic has been archived between 26 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path 'soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'
        option country 'US'
        option channel '157'
        option htmode 'VHT40'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option macaddr 'DOYOUNEEDTHIS?'
        option ssid 'NOTSHOWN'
        option wds '1'
        option encryption 'psk2+ccmp'
        option key 'NOTSHOWN'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
        option htmode 'HT20'
        option country 'US'
        option channel '10'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option macaddr 'DOYOUNEEDTHIS?'
        option ssid 'NOTSHOWN'
        option wds '1'
        option encryption 'psk2+ccmp'
        option key 'NOTSHOWN'


The contents of /etc/config/wireless after configuration.  The router stayed up maybe 3-4 minutes before it rebooted on its own.  So it's definitely config related.  I'll try to change to channel 36 like you say, also is there anything wrong with my 2.4Ghz settings?  Thanks for your help with this, I really think something minor is causing it to go into a rolling reboot and I just need to pinpoint it.

My procedure is that after it reboots (via crash) it doesn't come back up.  So I power off via the switch, then unplug power, wait for about 1 minute, plug it in and power back up.  It comes up after that.

(Last edited by rahul1023 on 4 Jun 2017, 19:04)

davidc502 wrote:
ValCher wrote:
starcms wrote:

radio2 is actually meant to be used for radar detection (DFS).  You should leave it off.

Then how do you configure Radio2 in 'monitor' mode?

This could be wrong, but my understanding is that even when disabled, radar can still be detected with it.

Suppose that chip 8887 is turned on and configured to monitor the radar signal, then there must be some feedback from chip 8964. This can be communicated through an external subprogramme because it is a different interfaces.
Is there a subroutine?

Actually, that's my screw up... He has the acs, and not acm, so Radio2 will not exist.

@rahul1023

wds is showing enabled on both radios. The mode should be "access point" unless you're going from wifi router to wifi router.

Ok switched to channel 36, LEDE stayed up 21minutes and 46 seconds, it rebooted again.  I was hopeful this time, but I think there is still a problem somewhere in there.  Anything I can check for logs?

Yes correct, my plan is to use WDS for the netgear which will be the WDS Client running Openwrt.  Trying to increase Wifi Coverage upstairs.

(Last edited by rahul1023 on 4 Jun 2017, 19:29)

rahul1023 wrote:

Ok switched to channel 36, LEDE stayed up 21minutes and 46 seconds, it rebooted again.  I was hopeful this time, but I think there is still a problem somewhere in there.  Anything I can check for logs?

Yes correct, my plan is to use WDS for the netgear which will be the WDS Client running Openwrt.  Trying to increase Wifi Coverage upstairs.

What happens when wds is disabled?  Are you still having the issue?

@rahul1023

Looking through some of the documentation about wds, it isn't going to work with Netgear. WDS is a non standard and each vender has a different way of implementing it. To maintain compatibility with WDS, you have to running the same hardware and software.. Meaning for it to work you would need two 1900acsV2's running the same version of LEDE.

Maybe someone else has been able to get different brands and software working? Or is there some other detail that perhaps I'm missing about this WDS implementation?

*EDIT*

There may be a way for the ACS to be in AccessPoint mode, but yet configure the Linksys to connect to the ACS as a client.

(Last edited by davidc502 on 4 Jun 2017, 19:41)

I'll shut off WDS, I can always rework that later.  My goal right now is to get the router to stay up.  I am going to change it to Access Point for both radios, then report back on how long before it reboots.

OK This time after unplugging, it switched partitions on its own and booted up with the linksys firmware.  How do I switch back to LEDE?

(Last edited by rahul1023 on 4 Jun 2017, 19:47)

rahul1023 wrote:

OK This time after unplugging, it switched partitions on its own and booted up with the linksys firmware.  How do I switch back to LEDE?

This command switches bootable partition:

fw_setenv boot_part x
reboot

x - should be 1 or 2, in your case it looks that you still have OEM firmware intact on primary partition, so it will be 2

davidc502 wrote:
ValCher wrote:
starcms wrote:

radio2 is actually meant to be used for radar detection (DFS).  You should leave it off.

Then how do you configure Radio2 in 'monitor' mode?

This could be wrong, but my understanding is that even when disabled, radar can still be detected with it.

This is my understanding as well

d4niel_p wrote:
rahul1023 wrote:

OK This time after unplugging, it switched partitions on its own and booted up with the linksys firmware.  How do I switch back to LEDE?

This command switches bootable partition:

fw_setenv boot_part x
reboot

x - should be 1 or 2, in your case it looks that you still have OEM firmware intact on primary partition, so it will be 2

You can only use that command from LEDE via SSH, not from the stock Linksys firmware.  You can switch back to LEDE on the other partition by turning the router off and on 4 or 5 times.  Turn it on, wait for the power led to turn on, then turn off, then repeat.

Or you could try flashing @david's build again from the Linksys firmware, not modify any settings, and see if that helps resolve your rebooting issues.  Then start changing one thing at a time to see what is causing the reboots.

(Last edited by starcms on 4 Jun 2017, 22:27)

davidc502 wrote:

Maybe someone else has been able to get different brands and software working? Or is there some other detail that perhaps I'm missing about this WDS implementation?

@davidc502,

I don't think WDS will work with other router brands.
I tried using WDS between my Linksys WRT1900ACSV1 as server and a Netgear R6300V2 as client, but no luck. sad
The R6300V2 showed the WDS link defined, but signal was always 0 db and no connection was made to the WRT1900ACS.
In the end I switched to using the old client-bridge configuration, which is working fine.

Adri.

Someone was able to set up openvpn client?,

The configuration it's working on tomato:

imgur.com/2gFtabz
imgur.com/OWAfQrg
imgur.com/lGmrACP

Files from OpenVPN Server:

Intelliholding-Aguilucho.ovpn:

client
resolv-retry 20
keepalive 10 60
nobind
mute-replay-warnings
ns-cert-type server
comp-lzo
max-routes 500
verb 1
persist-key
persist-tun
explicit-exit-notify 1
dev tun
proto udp
port 1194
cipher AES-128-CBC
cert keys/Intelliholding-Aguilucho-epizarro.crt
key keys/Intelliholding-Aguilucho-epizarro.key
ca keys/Intelliholding-Aguilucho-epizarro-ca.crt
remote xxx.xxx.xxx.xxx 1194 # public address 
remote xxx.xxx.xxx.xxx 1194 # static WAN 1

Intelliholding-Aguilucho-epizarro.crt

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 848396178 (0x32917f92)
        Signature Algorithm: md5WithRSAEncryption
        Issuer: CN=certificateAuthority, C=CO, ST=ST, L=L, O=O, OU=OU/dnQualifier=certificateAuthority
        Validity
            Not Before: Feb  9 21:47:00 2015 GMT
            Not After : Feb  6 21:47:00 2025 GMT
        Subject: C=CO, ST=ST, O=O, OU=OU, CN=epizarro/dnQualifier=client-epizarro
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
            RSA Public Key: (2048 bit)
                Modulus (2048 bit):
                    00:cb:08:75:9a:5c:3b:ae:2a:c0:ec:75:06:38:2b:
                    97:22:a2:68:b1:cb:a3:e2:69:f0:37:76:af:da:f9:
                    88:ec:8a:23:e6:c7:91:ef:8e:6c:4d:ab:87:4b:3d:
                    9d:9f:25:8a:a9:68:ee:8f:1d:1f:4e:21:66:6f:59:
                    02:af:81:30:d8:8a:c2:cc:b4:6d:0f:81:49:7b:74:
                    64:45:a2:ca:56:0c:78:14:e4:1a:24:0b:59:92:08:
                    5c:6c:08:a9:9d:15:59:ed:0f:de:4a:7c:a9:c4:79:
                    dd:21:3e:95:e1:48:e4:db:35:b1:c4:43:79:d2:29:
                    62:ba:b0:82:3b:68:76:65:cb:4f:73:59:5d:54:a9:
                    ce:12:b8:b3:d3:c0:aa:b0:e0:c6:c6:e3:73:28:e3:
                    b9:2b:65:e8:f6:93:ed:9d:96:f6:6d:6f:32:8b:03:
                    e3:42:13:43:9c:ce:1f:48:ec:0d:8b:32:2a:cb:71:
                    b4:9e:df:1b:9b:25:08:58:52:44:2b:bb:5a:92:81:
                    b0:74:66:78:4c:0e:5f:b8:1d:b1:a2:4a:df:34:89:
                    bb:2d:ad:c7:fa:c2:19:88:c0:2d:8a:50:95:9f:9b:
                    52:ae:b2:71:5a:4f:6d:d5:bd:a9:02:fd:95:4f:0a:
                    2d:bf:57:0a:0a:6d:0b:62:6f:b0:54:46:0b:9f:b2:
                    89:5b
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: 
                CA:FALSE
            Netscape Cert Type: 
                SSL Client
            Netscape Comment: 
                OpenSSL Generated Certificate
            X509v3 Subject Key Identifier: 
                BF:77:04:00:5E:08:CB:D4:71:F0:FB:76:2A:16:98:91:DF:80:B6:E0
            X509v3 Authority Key Identifier: 
                keyid:8B:25:67:35:59:BD:88:D6:0A:76:38:4F:B1:64:0B:F6:C5:83:92:80
                DirName:/CN=certificateAuthority/C=CO/ST=ST/L=L/O=O/OU=OU/dnQualifier=certificateAuthority
                serial:BB:C9:7E:07:73:5D:2F:37

    Signature Algorithm: md5WithRSAEncryption
        64:6e:8f:b2:5e:f7:67:61:9c:c0:51:18:e0:62:0c:e6:86:c7:
        0c:2e:63:07:bf:70:24:af:f0:17:3e:49:25:e4:b5:2b:1d:ac:
        b3:7b:16:e6:1e:c2:42:62:46:09:08:1c:62:97:e9:2f:d7:1a:
        8e:c9:e7:e3:78:f7:a7:b2:ca:d6:42:b4:16:75:5d:21:d9:e1:
        61:43:29:d3:94:5e:00:0e:52:e2:44:5a:32:69:da:e9:7b:4f:
        12:2d:7c:ce:a6:29:67:76:0f:4e:3e:c1:b9:58:ef:b9:45:f1:
        88:d7:e5:45:0c:12:86:3f:86:19:cf:d4:e9:10:11:71:7d:8d:
        49:bc:63:0f:d5:6a:3b:40:46:b3:7d:9a:93:62:1f:7d:c8:84:
        7b:52:b6:26:1e:18:4a:e1:e2:1e:44:c5:de:86:78:16:ea:2c:
        03:86:61:19:0c:4b:52:1a:47:50:b2:35:a3:0c:02:bb:f9:cc:
        85:01:05:10:4f:9d:69:cd:bc:16:36:9c:ab:7d:e0:73:43:cb:
        2c:16:75:75:a0:0e:a3:5c:ac:92:ee:c6:c9:a4:03:0c:cd:62:
        d4:3e:ac:35:07:2a:32:93:88:d5:3e:b4:fe:c9:c8:60:0b:e7:
        5a:b4:fe:ff:54:b7:c7:6b:47:86:0d:0b:b3:6e:f1:6b:3e:68:
        bd:97:00:e8
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

From Intelliholding-Aguilucho-epizarro.crt, I trunk all except certificate (2nd attemp):

-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

Intelliholding-Aguilucho-epizarro.key

-----BEGIN RSA PRIVATE KEY-----
...
-----END RSA PRIVATE KEY-----

Intelliholding-Aguilucho-epizarro-ca.crt

-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

Logs from LEDE build

Mon Jun  5 13:25:14 2017 daemon.err openvpn(CostaBrothers)[13235]: OpenSSL: error:14090086:lib(20):func(144):reason(134)
Mon Jun  5 13:25:14 2017 daemon.err openvpn(CostaBrothers)[13235]: TLS_ERROR: BIO read tls_read_plaintext error
Mon Jun  5 13:25:14 2017 daemon.err openvpn(CostaBrothers)[13235]: TLS Error: TLS object -> incoming plaintext read error
Mon Jun  5 13:25:14 2017 daemon.err openvpn(CostaBrothers)[13235]: TLS Error: TLS handshake failed
Mon Jun  5 13:25:14 2017 daemon.notice openvpn(CostaBrothers)[13235]: SIGUSR1[soft,tls-error] received, process restarting
Mon Jun  5 13:25:14 2017 daemon.notice openvpn(CostaBrothers)[13235]: Restart pause, 5 second(s)
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xxx:1194
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: Socket Buffers: R=[163840->163840] S=[163840->163840]
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: UDP link local: (not bound)
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: UDP link remote: [AF_INET]xxx.xxx.xxx.xxx:1194
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: TLS: Initial packet from [AF_INET]200.75.7.65:1194, sid=778c6e0a 64ffb152
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: VERIFY OK: depth=1, CN=certificateAuthority, C=CO, ST=ST, L=L, O=O, OU=OU, dnQualifier=certificateAuthority
Mon Jun  5 13:25:19 2017 daemon.err openvpn(CostaBrothers)[13235]: Certificate does not have key usage extension
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: VERIFY KU ERROR
Mon Jun  5 13:25:19 2017 daemon.err openvpn(CostaBrothers)[13235]: OpenSSL: error:14090086:lib(20):func(144):reason(134)
Mon Jun  5 13:25:19 2017 daemon.err openvpn(CostaBrothers)[13235]: TLS_ERROR: BIO read tls_read_plaintext error
Mon Jun  5 13:25:19 2017 daemon.err openvpn(CostaBrothers)[13235]: TLS Error: TLS object -> incoming plaintext read error
Mon Jun  5 13:25:19 2017 daemon.err openvpn(CostaBrothers)[13235]: TLS Error: TLS handshake failed
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: SIGUSR1[soft,tls-error] received, process restarting
Mon Jun  5 13:25:19 2017 daemon.notice openvpn(CostaBrothers)[13235]: Restart pause, 5 second(s)

OpenVPN Conf in my LEDE router:

config openvpn 'CostaBrothers'
        option float '1'
        option client '1'
        option comp_lzo 'yes'
        option dev 'tap'
        option reneg_sec '0'
        option verb '3'
        option persist_key '1'
        option nobind '1'
        list remote 'xxx.xxx.xxx.xxx'
        option key '/etc/luci-uploads/cbid.openvpn.CostaBrothers.key'
        option ca '/etc/luci-uploads/cbid.openvpn.CostaBrothers.ca'
        option cert '/etc/luci-uploads/cbid.openvpn.CostaBrothers.cert'
        option cipher 'AES-128-CBC'
        option ns_cert_type 'server'
        option proto 'udp'
        option resolv_retry '20'
        option keepalive '10 60'
        option explicit_exit_notify '1'

Supported ciphers and HMAC

root@LEDE:/etc/config# openvpn --show-digests
MD5 128 bit digest size
RSA-MD5 128 bit digest size
SHA1 160 bit digest size
RSA-SHA1 160 bit digest size
DSA-SHA1-old 160 bit digest size
DSA-SHA1 160 bit digest size
RSA-SHA1-2 160 bit digest size
DSA 160 bit digest size
RIPEMD160 160 bit digest size
RSA-RIPEMD160 160 bit digest size
MD4 128 bit digest size
RSA-MD4 128 bit digest size
ecdsa-with-SHA1 160 bit digest size
RSA-SHA256 256 bit digest size
RSA-SHA384 384 bit digest size
RSA-SHA512 512 bit digest size
RSA-SHA224 224 bit digest size
SHA256 256 bit digest size
SHA384 384 bit digest size
SHA512 512 bit digest size
SHA224 224 bit digest size
root@LEDE:/etc/config# openvpn --show-ciphers
AES-128-CBC  (128 bit key, 128 bit block)
AES-128-CFB  (128 bit key, 128 bit block, TLS client/server mode only)
AES-128-CFB1  (128 bit key, 128 bit block, TLS client/server mode only)
AES-128-CFB8  (128 bit key, 128 bit block, TLS client/server mode only)
AES-128-GCM  (128 bit key, 128 bit block, TLS client/server mode only)
AES-128-OFB  (128 bit key, 128 bit block, TLS client/server mode only)
AES-192-CBC  (192 bit key, 128 bit block)
AES-192-CFB  (192 bit key, 128 bit block, TLS client/server mode only)
AES-192-CFB1  (192 bit key, 128 bit block, TLS client/server mode only)
AES-192-CFB8  (192 bit key, 128 bit block, TLS client/server mode only)
AES-192-GCM  (192 bit key, 128 bit block, TLS client/server mode only)
AES-192-OFB  (192 bit key, 128 bit block, TLS client/server mode only)
AES-256-CBC  (256 bit key, 128 bit block)
AES-256-CFB  (256 bit key, 128 bit block, TLS client/server mode only)
AES-256-CFB1  (256 bit key, 128 bit block, TLS client/server mode only)
AES-256-CFB8  (256 bit key, 128 bit block, TLS client/server mode only)
AES-256-GCM  (256 bit key, 128 bit block, TLS client/server mode only)
AES-256-OFB  (256 bit key, 128 bit block, TLS client/server mode only)

The following ciphers have a block size of less than 128 bits,
and are therefore deprecated.  Do not use unless you have to.

BF-CBC  (128 bit key by default, 64 bit block)
BF-CFB  (128 bit key by default, 64 bit block, TLS client/server mode only)
BF-OFB  (128 bit key by default, 64 bit block, TLS client/server mode only)
CAST5-CBC  (128 bit key by default, 64 bit block)
CAST5-CFB  (128 bit key by default, 64 bit block, TLS client/server mode only)
CAST5-OFB  (128 bit key by default, 64 bit block, TLS client/server mode only)
DES-CBC  (64 bit key, 64 bit block)
DES-CFB  (64 bit key, 64 bit block, TLS client/server mode only)
DES-CFB1  (64 bit key, 64 bit block, TLS client/server mode only)
DES-CFB8  (64 bit key, 64 bit block, TLS client/server mode only)
DES-EDE-CBC  (128 bit key, 64 bit block)
DES-EDE-CFB  (128 bit key, 64 bit block, TLS client/server mode only)
DES-EDE-OFB  (128 bit key, 64 bit block, TLS client/server mode only)
DES-EDE3-CBC  (192 bit key, 64 bit block)
DES-EDE3-CFB  (192 bit key, 64 bit block, TLS client/server mode only)
DES-EDE3-CFB1  (192 bit key, 64 bit block, TLS client/server mode only)
DES-EDE3-CFB8  (192 bit key, 64 bit block, TLS client/server mode only)
DES-EDE3-OFB  (192 bit key, 64 bit block, TLS client/server mode only)
DES-OFB  (64 bit key, 64 bit block, TLS client/server mode only)
DESX-CBC  (192 bit key, 64 bit block)
RC2-40-CBC  (40 bit key by default, 64 bit block)
RC2-64-CBC  (64 bit key by default, 64 bit block)
RC2-CBC  (128 bit key by default, 64 bit block)
RC2-CFB  (128 bit key by default, 64 bit block, TLS client/server mode only)
RC2-OFB  (128 bit key by default, 64 bit block, TLS client/server mode only)

UPDATE

The certificates are MD5 based as they are not changed on upgrade to prevent breaking existing VPNs. So I need to allow MD5 certs in LEDE openssl config.

There is a similar issue (maybe the same) with REHL Distros but you can enable:

Environment="OPENSSL_ENABLE_MD5_VERIFY=1 NSS_HASH_ALG_SUPPORT=+MD5"

UPDATE2

I give up, just change MD5 to SH1 from server

(Last edited by eliaspizarro on 7 Jun 2017, 23:50)

My dns crypt is not starting on boot. Any one know why?
As a workaround I put this in /etc/rc.local.

# Sleep for 2 minutes for other things to load
 
sleep 120
 
# Restart dnscrypt-proxy - in case it has not started
 
/etc/init.d/dnscrypt-proxy stop
 
sleep 10
 
/etc/init.d/dnscrypt-proxy start

(Last edited by tapper on 5 Jun 2017, 00:12)

tapper wrote:

My dns crypt is not starting on boot. Any one know why?
As a workaround I put this in /etc/rc.local.

# Sleep for 2 minutes for other things to load
 
sleep 120
 
# Restart dnscrypt-proxy - in case it has not started
 
/etc/init.d/dnscrypt-proxy stop
 
sleep 10
 
/etc/init.d/dnscrypt-proxy start

The version in the latest build has a bug in it.  It is most likely what is causing your problem.  Easiest fix it to uninstall it and install https://davidc502sis.dynamic-dns.net/sn … _vfpv3.ipk (the version from david's previous build).

The issue will be fixed in @david's next build.  It was a bug in dnscrypt-proxy version 1.9.5-2.

(Last edited by starcms on 5 Jun 2017, 01:12)

@david, now I can personally also report issues with wpad (full version).  On my laptop (Killer 1525 802.11ac 2x2 wifi card), when booting up or resuming from sleep, I've had to try to manually disconnect and reconnect a few times before it would properly authenticate and connect fully. I switched to wpad-mini and the problem hasn't reoccurred for the past 36 hours or so.  And it had never occured before wpad (full version) was introduced in most recent build.

Maybe if wpad does add 802.11r, the mwlwifi drivers has a bug and 802.11r doesn't work properly?  That is a completely wild guess based on pretty much nothing wink  I just do know that wpad uses RADIUS even when only set to wpa/wpa2-psk (which seems to be unnecessary for any reason).  Glad to see you are changing back to wpad-mini on next release.

(Last edited by starcms on 5 Jun 2017, 01:35)

I updated to 1.9.5-4 and am still having issues.

tapper wrote:

I updated to 1.9.5-4 and am still having issues.

I'm using 1.9.5-4 right now and it works perfectly.  Starts on boot just like it should.  Maybe try disabling and re-enabling the start-up script?

No issues with dnscrypt starting at boot here either.

Don't shoot me for asking, but it is "enabled" from command line?

root@lede:~# opkg list-installed |grep dnscrypt*
dnscrypt-proxy - 1.9.5-2

davidc502 wrote:

No issues with dnscrypt starting at boot here either.

Don't shoot me for asking, but it is "enabled" from command line?

root@lede:~# opkg list-installed |grep dnscrypt*
dnscrypt-proxy - 1.9.5-2

In case those of you who use dnscrypt haven't been following the thread, there is a bug in version 1.9.5-2 (the version that @david is running, shown above, which is the version included in the latest build).

The bug it in the init.d file and causes dnscrypt to silently crash upon startup.

I posted a fix a few pages back for the init.d file to fix the issue (all you have to do is change two words).  If you want to use the version that came included in the latest build (most likely because it has plugin support enabled and the versions from the LEDE repo do not), just look for my post with the fix.

Another solution is to install an older version from @david's repo for a previous build.  Finally, you can install the latest version 1.9.5-4 from the LEDE repo, but it lacks plugin support.  If you don't use any of the dnscrypt plugins, then this would work fine also.

starcms wrote:

@david, now I can personally also report issues with wpad (full version).  On my laptop (Killer 1525 802.11ac 2x2 wifi card), when booting up or resuming from sleep, I've had to try to manually disconnect and reconnect a few times before it would properly authenticate and connect fully. I switched to wpad-mini and the problem hasn't reoccurred for the past 36 hours or so.  And it had never occured before wpad (full version) was introduced in most recent build.
....

Killer (in fact - Atheros) have a quite buggy drivers, i have this issue (and others) as well before.
What to do:
1. Install latest STANDALONE drivers (not packaged with filter/app)
2. In power scheme, set Wireless adapter power settings to Maximum performance (better) or Low power save (works too, but ping time will be longer a bit.

(Last edited by T-Troll on 5 Jun 2017, 09:16)

T-Troll wrote:
starcms wrote:

@david, now I can personally also report issues with wpad (full version).  On my laptop (Killer 1525 802.11ac 2x2 wifi card), when booting up or resuming from sleep, I've had to try to manually disconnect and reconnect a few times before it would properly authenticate and connect fully. I switched to wpad-mini and the problem hasn't reoccurred for the past 36 hours or so.  And it had never occured before wpad (full version) was introduced in most recent build.
....

Killer (in fact - Atheros) have a quite buggy drivers, i have this issue (and others) as well before.
What to do:
1. Install latest STANDALONE drivers (not packaged with filter/app)
2. In power scheme, set Wireless adapter power settings to Maximum performance (better) or Low power save (works too, but ping time will be longer a bit.

Did both of those a long time ago smile

Can't stand stupid bloat apps, etc, anyway; and can't stand windows killing my wifi speeds when I'm not plugged in either.

I've never had any issues before, and no longer since I removed wpad and installed wpad-mini.

I have a wrt1900ac v1 and have found that I have the reboot issue with the 4.9 kernel. I then went to the 4.4 kernel and things seemed to work fine but when I went to install packages like ipset, there was a dependency for the 4.9 kernel. Is this something that can be or already has been fixed?

starcms wrote:
puppinoo wrote:

Hi again,
A quick question I forgot to ask before.
I'm keeping the radio2 turned off cause I read (here or somewhere else, I don't remember) that its the client mode antenna and actually client mode doesn't work on 3200 so keeping it turned off is preferable.
Is that right or I should turn it on?

Thanks.

radio2 is actually meant to be used for radar detection (DFS).  You should leave it off.

Thanks a lot for advice.
Sorry if I go offtopic but since I dunno when I'll upgrade cause this davidc build seems to works fine I read about the wpad issue. Can I just unistall the full version and install the mini without reconfigure anything or additional operations are needed to make it work?

Thanks and regards.

puppinoo wrote:
starcms wrote:
puppinoo wrote:

Hi again,
A quick question I forgot to ask before.
I'm keeping the radio2 turned off cause I read (here or somewhere else, I don't remember) that its the client mode antenna and actually client mode doesn't work on 3200 so keeping it turned off is preferable.
Is that right or I should turn it on?

Thanks.

radio2 is actually meant to be used for radar detection (DFS).  You should leave it off.

Thanks a lot for advice.
Sorry if I go offtopic but since I dunno when I'll upgrade cause this davidc build seems to works fine I read about the wpad issue. Can I just unistall the full version and install the mini without reconfigure anything or additional operations are needed to make it work?

Thanks and regards.

Yes, just do:

opkg update
opkg remove wpad
opkg install wpad-mini
reboot

That's it.  No reconfiguration of anything needed.  And that's not off topic at all.

(Last edited by starcms on 6 Jun 2017, 03:55)