Joined: 13 Aug 2013 Posts: 6865 Location: Romerike, Norway
Posted: Tue Apr 10, 2018 17:40 Post subject:
Set the VPN router in to router mode.
Enter a static route on the main router 10.0.2.0/24 with the wan address of the VPN router as gateway (the address you have not supplied on your diagram).
Set the VPN router in to router mode.
Enter a static route on the main router 10.0.2.0/24 with the wan address of the VPN router as gateway (the address you have not supplied on your diagram).
Thanks for the quick response.. I'll look at setting this up and see if I don't mess up the OpenVPN settings while making the changes.
Joined: 17 Apr 2014 Posts: 135 Location: SF Bay Area
Posted: Wed Apr 11, 2018 8:00 Post subject:
rramstad wrote:
trichard3000 wrote:
Laryllan wrote:
r33492 seems to feature stable wireless.
I got no WLAN disconnects for about a day.
I was having several inconsistent problems with wifi devices (particularly Raspberry Pi, Beagleone) using 34777. The devices would connect to wifi and even get a dhcp address but couldn't be pinged or otherwise communicated with from other wifi clients about 80% of the time. They always could be seen and used by clients on a wired switch that connects back to one of the ports on the n66u.
I rolled back to 33492 and wifi/wired clients all seem to be working properly now. I used dd-wrt.v24-33492_NEWD-2_K3.x-big-RT-N66U.trx
Hope this helps the next person, thanks Laryllan.
Thanks so much for the post.
I also have been having a lot of trouble with clients, particularly wifi but also wired, and kept upgrading to the latest and greatest BS build hoping it would get fixed at some point.
After six or so frustrating weeks, I saw this post.
I rolled back yesterday to 33492 (mega) and things are working much better now.
...
After trying most of 2018 K3X w instability/slow 2.4 performance, and several CFE recovery dances, 33492-big is stable @12hrs. Ahhhhhh.
2.4 NG-mixed HT20 / 5 NA-mixed HT40 are about 20% faster than the other mixed/only modes for streaming to/from a wired client .
Cheers,
update good @23hrs.
update stable at 6 days, nightly sched reboots.
* Best throughput: 126.1/30.0Mb/s, average 114/18Mbps. Different room, 7m distance, 5GHz <-> wired client
* through RT-N66U GbE: 69.1MB/s
* through Netgear GS105: 69.7MB/s
* wifi TX/RX error rates: <0.00003%.
* no router disconnects even for older 2.4GHz clients with tiny brains.
* no router-based failed connects.
Posted: Sat May 19, 2018 3:33 Post subject: Firmware upgrade report - dd-wrt.v24-35916_NEWD-2_K3.x-big
Just a data point here -- r35916 May 11 2018 working well for me so far.
On my RT-N66U, Broadcom BCM5300 chip revision 1:
Ugraded using web GUI "Upgrade Firmware" screen, no reset before or after, everything went fine & all my configuration was preserved post-update. All custom features (virtual Wifi interfaces, VLAN setup, custom IPtables commands, etc.) worked exactly as before under a mid-2017 firmware version.
Up and running fast & stable for 4 hours so far, with 2 ethernet + 3 Wifi clients in a noisy Wifi environment. Will update in 3 to 5 days, then at about the 1-month mark with further notes.
Network is 1 linux box, the other hosts/clients are all recent flavors of Mac OS X / iOS.
Posted: Thu May 24, 2018 14:33 Post subject: Re: Firmware upgrade report - dd-wrt.v24-35916_NEWD-2_K3.x-b
[quote="sampalazno"]Just a data point here -- [b]r35916 May 11 2018 [/b]working well for me so far.
On my RT-N66U, Broadcom BCM5300 chip revision 1:
Ugraded using web GUI "Upgrade Firmware" screen, no reset before or after, everything went fine & all my configuration was preserved post-update. All custom features (virtual Wifi interfaces, VLAN setup, custom IPtables commands, etc.) worked exactly as before under a mid-2017 firmware version.
Up and running fast & stable for 4 hours so far, with 2 ethernet + 3 Wifi clients in a noisy Wifi environment. Will update in 3 to 5 days, then at about the 1-month mark with further notes.
Network is 1 linux box, the other hosts/clients are all recent flavors of Mac OS X / iOS.
Ended up reverting to DD-WRT v3.0-r35531 big (03/26/18) based on recommendation from another thread. r35916 May 11 2018 was dropping devices every once and a while.
Greetings,
I'm trying to get a 2.4GHz guest network set up on my N66U, and am having quite a bit of trouble. I've tried several recent builds, and have been working backwards to find one that works. I am currently on 32170.
In a nutshell, the VAP doesn't seem to be up. When I reboot the router I can see the guest SSID show up for a brief moment if I scan wireless with my phone, but it disappears when the main AP comes up.
Everything else appears to be working fine. If anyone has a working guest network on their N66U, I'd like to know which build you're using.
Greetings,
I'm trying to get a 2.4GHz guest network set up on my N66U, and am having quite a bit of trouble. I've tried several recent builds, and have been working backwards to find one that works. I am currently on 32170.
In a nutshell, the VAP doesn't seem to be up. When I reboot the router I can see the guest SSID show up for a brief moment if I scan wireless with my phone, but it disappears when the main AP comes up.
Everything else appears to be working fine. If anyone has a working guest network on their N66U, I'd like to know which build you're using.
Thank you!
I have a 2.4 guest networking on 33525 (AP, NG mixed, wide HT40 40MHz, and working IPV6) which is mostly usable. 5 GHz is turned off. Some clients experience occasional "hangs" which I can avoid if I switch to BG mixed.
Note all builds after 33525 (i.e. those with the krack fix) will experience wireless hangs that make the unit unusable so I'm avoiding them for the time being...
If you are on a crowded environment, it's better to use 20 Mhz width.
Thanks for the suggestion but I'm pretty much resigned to the fact that broadcom/DD-WRT based systems are not for me (difficult to support
proprietary driver?). Compared to the rock stable "everything just works" atheros/DD-WRT system I used before, no matter what build or settings I choose on this POS something doesn't work quite right.
FWIW
It's been a while since I experimented. There are 11 APs visible: channel 1 (2 APs), 2 (1 AP), 6 (3 APs), and 11 (5 APs). I've tried 20 and 40 MHz width with the same symptoms (one client will consistently drop and re associate). I just tried BG mixed last night and now an android client is dropping whereas it was a windows client that was dropped on NG mixed... perhaps my memory is faulty and it's G only that avoids this for my mix of android, ios, OSX, windows and linux clients.
The symptoms after build 33525 are different. The client (non OS specific) doesn't drop, rather wireless just "hangs" or freezes and the frequency of hangs increases with uptime. Myself and others have posted several times in the forum build reports as long ago as fall 2017 and I think there is at least one trouble ticket. Due to other recent issues with broadcom, I've stopped trying new beta builds for now.
The wireless has been broken on these builds for some time.
Back in April rolling back to 33492 (mega) fixed the problems for me on my RT-N16 and RT-66U.
I had been upgrading every week or two hoping that a newer release would fix the problem, but some posts and one key PM encouraged me strongly to try rolling back, and it instantly fixed all my problems.
IMPORTANT: DO NOT USE K2.6 builds if using CFE v1.0.1.3 (64K nvram) or NEWER!!!
At launch, the RT-N66U was limited to 32k nvram. However, CFE (bootloader) version 1.0.1.3 added 64k nvram support around April 2013, but was not compatible with DD-WRT firmware at that time. For details, see these forum links to historical nvram and 64K implemention discussions: Fractal comments and "RT-N66 CFE Thread"
"This was resolved with DD-WRT K3X builds (kernel 3.x) which extended nvram to 64k, and can be used for any CFE"
Does this mean I can go ahead and safely flash dd-wrt.v24-33525_NEWD-2_K3.x-big-RT-N66U.trx
for 1st time flashing
Does this mean I can go ahead and safely flash dd-wrt.v24-33525_NEWD-2_K3.x-big-RT-N66U.trx
for 1st time flashing
It works for me. FYI flashing via the CFE recovery requires me to be patient and fearless. I have to wait 30+ minutes for the unit to reboot with little or no feed back. Good news is I've always been able to reflash via recovery and restore settings accross builds via a saved nvram despite "abusing" this unit with bad builds that partially brick it.
Per Yngve Berg wrote:
The problem is the AP at channel 2. It interferers with channel 1 and 6. If you can identify it, ask him to move to 1.
Thx, I'm trying fixed channel 11 and 20 MHz width on NG mixed. If the windows client starts dropping tonight, I'll blame windows...
IMPORTANT: DO NOT USE K2.6 builds if using CFE v1.0.1.3 (64K nvram) or NEWER!!!
At launch, the RT-N66U was limited to 32k nvram. However, CFE (bootloader) version 1.0.1.3 added 64k nvram support around April 2013, but was not compatible with DD-WRT firmware at that time. For details, see these forum links to historical nvram and 64K implemention discussions: Fractal comments and "RT-N66 CFE Thread"
"This was resolved with DD-WRT K3X builds (kernel 3.x) which extended nvram to 64k, and can be used for any CFE"
Does this mean I can go ahead and safely flash dd-wrt.v24-33525_NEWD-2_K3.x-big-RT-N66U.trx
for 1st time flashing
Yes. Almost no one needs the k2.6 builds for the rt-n66u. _________________ I am far from a guru, I'm barely a novice.
