Firmware Version
DD-WRT v3.0-r40672 std (08/16/19)
Kernel Version
Linux 4.9.189 #1227 SMP Fri Aug 16 15:20:47 CEST 2019 armv7l _________________ WRT1900ACSv2
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sat Aug 17, 2019 23:10 Post subject:
gufus wrote:
MAC Address60:38:E0:B7:F8:E2
Chipset 88W8964 802.11ac
RadioRadio is On
ModeWDS Station
NetworkAC/N-Mixed
SSIDgypsynet_5g
Channel157 + 155 (5785 MHz VHT80)
Busy Time9874 ms
Active Time268241 ms
Channel Quality97%
TX Power30 dBm
Rate1300 Mb/s
ACK TimingN/A
Encryption - Interface ath0Enabled, WPA2-PSK
Connected Clients1
Running in 5g WDS Station mode
Setting up a Virtual Interface does not work
I PM'd you regarding the vap problem. Virtual Interface will only work on Channel 100 for a WDS/client interface. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55723
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55723 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55723 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55723
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55723
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun Aug 18, 2019 0:04 Post subject:
gufus wrote:
WENED wrote:
gufus wrote:
MAC
Setting up a Virtual Interface does not work
I PM'd you regarding the vap problem. Virtual Interface will only work on Channel 100 for a WDS/client interface.
I couldn't get up Channel 100 5g WDS Station mode
As you can see from my profile I run a few different wrt's and have no problem with using channel 100.
The only reason I can see for your inability to use chan 100 would be your area as there are a few Countries which restrict the use. As for North America and most of the world 100-144 are available with DFS and/or TPC which restricts power output to 23db.
https://en.wikipedia.org/wiki/List_of_WLAN_channels
I admit that in my application I prefer to use 149 (UU+6) as I run a remote in my barn 500' away but in the house I can use 100 (UUU+14) on 160Mhz since it only has to travel about 20' through a couple of walls.
Please explain why you cannot get ch 100 , if you prefer PM me to keep your response confidential. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55723
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55723 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55723 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55723
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55723
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Joined: 04 Aug 2012 Posts: 612 Location: behind the screen
Posted: Sun Aug 18, 2019 4:37 Post subject:
WENED wrote:
gufus wrote:
WENED wrote:
gufus wrote:
MAC
Setting up a Virtual Interface does not work
I PM'd you regarding the vap problem. Virtual Interface will only work on Channel 100 for a WDS/client interface.
I couldn't get up Channel 100 5g WDS Station mode
As you can see from my profile I run a few different wrt's and have no problem with using channel 100.
The only reason I can see for your inability to use chan 100 would be your area as there are a few Countries which restrict the use. As for North America and most of the world 100-144 are available with DFS and/or TPC which restricts power output to 23db.
https://en.wikipedia.org/wiki/List_of_WLAN_channels
I admit that in my application I prefer to use 149 (UU+6) as I run a remote in my barn 500' away but in the house I can use 100 (UUU+14) on 160Mhz since it only has to travel about 20' through a couple of walls.
Please explain why you cannot get ch 100 , if you prefer PM me to keep your response confidential.
Channel 100 is DFS in CA, my country
I use openwrt 4 my WDS AP and a 1900ac, just will not setup Channel 100 _________________ WRT3200ACM openwrt 18.06.5
WRT3200ACM dd-wrt r41791
WRT54GL dd-wrt r21676
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun Aug 18, 2019 5:07 Post subject:
gufus wrote:
WENED wrote:
gufus wrote:
WENED wrote:
gufus wrote:
MAC
Setting up a Virtual Interface does not work
I PM'd you regarding the vap problem. Virtual Interface will only work on Channel 100 for a WDS/client interface.
I couldn't get up Channel 100 5g WDS Station mode
As you can see from my profile I run a few different wrt's and have no problem with using channel 100.
The only reason I can see for your inability to use chan 100 would be your area as there are a few Countries which restrict the use. As for North America and most of the world 100-144 are available with DFS and/or TPC which restricts power output to 23db.
https://en.wikipedia.org/wiki/List_of_WLAN_channels
I admit that in my application I prefer to use 149 (UU+6) as I run a remote in my barn 500' away but in the house I can use 100 (UUU+14) on 160Mhz since it only has to travel about 20' through a couple of walls.
Please explain why you cannot get ch 100 , if you prefer PM me to keep your response confidential.
Channel 100 is DFS in CA, my country
I use openwrt 4 my WDS AP and a 1900ac, just will not setup Channel 100
I too am in Canada as you can see in my profile.
Both the 1900 and 3200 are DFS enabled which means you can use Ch 100 (UU+6) @ 80Mhz and it will reduce power to 23db.
If you look at the Wikipedia page for wifi it indicates that for Canada this is acceptable as long as the router is DFS capable, which it is.
I double checked on my 1900's and had no problem running CH 100 WDS AP.
If openwrt is preventing selection, it is a bug in openwrt because the 1900 is fully capable with DD-WRT. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55723
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55723 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55723 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55723
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55723
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Upgraded WRT1200AC v1 from r40634 to r40672 using Waterfox 56.2.12 (64 bit) running on Linux Mint 19.1 OS. Usual yellows in syslog.
Ran command "ubootenv set boot_part 2" before update. Successfull update and reboot. No issues
Kernel Version Linux 4.9.189 #1227 SMP Fri Aug 16 15:20:47 CEST 2019 armv7l
Aug 18 06:43:27 router daemon.notice openvpn[1731]: OpenVPN 2.4.7 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug 16 2019
Aug 18 06:43:27 router daemon.notice openvpn[1731]: library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.09
Edit - Lost WAN connection at around 4 hrs up-time for about 2 minutes after which it came back on-line. Reverted to r40634 which has not had any issues except a one time garbled GUI.
Last edited by Monza on Sun Aug 18, 2019 19:47; edited 1 time in total
Aug 18 16:59:34 Black Shark daemon.info smartd[6824]: Device: /dev/sda [SAT], opened
Aug 18 16:59:34 Black Shark daemon.info smartd[6824]: Device: /dev/sda [SAT], WDC WD40EURD-14TSBY0, S/N:WD-WCC4E0ERZK5X, WWN:5-0014ee-20e396777, FW:80.00A80, 4.00 TB
Aug 18 16:59:34 Black Shark daemon.info smartd[6824]: Device: /dev/sda [SAT], not found in smartd database.
Aug 18 16:59:34 Black Shark daemon.info smartd[6824]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Aug 18 16:59:34 Black Shark daemon.info smartd[6824]: Device: /dev/sdb [SAT], opened
Aug 18 16:59:34 Black Shark daemon.info smartd[6824]: Device: /dev/sdb [SAT], WDC WD30EZRX-00D8PB0, S/N:WD-WMC4N0J09AD4, WWN:5-0014ee-65ac7333c, FW:80.00A80, 3.00 TB
Aug 18 16:59:34 Black Shark daemon.info smartd[6824]: Device: /dev/sdb [SAT], found in smartd database: Western Digital Green
Aug 18 16:59:35 Black Shark daemon.info smartd[6824]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Aug 18 16:59:35 Black Shark daemon.info smartd[6824]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Aug 18 16:59:35 Black Shark daemon.crit smartd[6824]: Device: /dev/sda [SAT], 81 Currently unreadable (pending) sectors
Ran command "ubootenv set boot_part 2" before update. Successfull update and reboot. No issues
Does it mean this update still doesn't fit on the first partition? Is this ever going to be fixed, or it will work only for 3200 from now on with both partitions?