Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sat Jun 10, 2017 9:31 Post subject:
then fix your config. vpn is known to be working with this build. but i dont know which vpn services you refer to. openvpn? mmh i dont know.
consider that openvpn has some small config syntax changes in newer versions which may be the root cause of your problem. but i can't tell you much without knowing your config. so please post your config (without any keys etc.) and i may be able to help you _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
then fix your config. vpn is known to be working with this build. but i dont know which vpn services you refer to. openvpn? mmh i dont know.
consider that openvpn has some small config syntax changes in newer versions which may be the root cause of your problem. but i can't tell you much without knowing your config. so please post your config (without any keys etc.) and i may be able to help you
Yeah it's OpenVPN I'll post my configs once I get a chance too.
Today after 7 days up on Kong v3.0-r32170M kongal (06/02/17), my router stopped working, all my computers lost their DHCP assignment and were unable to re-cover them, my hard wired pc was getting self-assigned ip of 169.xxx.xxx.xxx (instead of the usual 192.168.1.xxx). Hard wired connection to the router didn't work either. I had to manually reboot the router...
pre release for testing. i changed alot within the embedded webserver. i hope there are no crashbugs within it. but overall it should be faster than ever before
How do you flash it from DD-WRT Kong? .bin upload only?
pre release for testing. i changed alot within the embedded webserver. i hope there are no crashbugs within it. but overall it should be faster than ever before
How do you flash it from DD-WRT Kong? .bin upload only?
I just flashed to the 6/9/2017 version Brainslayer just posted on the last page on my R9000, and it works great. Feels faster than the 6/3/2017 Kong version I was just on.
I just flashed to the 6/9/2017 version Brainslayer just posted on the last page on my R9000, and it works great. Feels faster than the 6/3/2017 Kong version I was just on.
Is BS using the same improvements like Kong, e.g. crypto dev?
Is Kong making his builds based on latest BS builds?
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Wed Jun 14, 2017 10:47 Post subject:
ahm i introduced the cryptodev support, not kong.
for all kernel based crypto its always enabled.
but userspace openvpn you can set "nvram set use_crypto=1;nvram commit" then openvpn will use hw crypto, but since the crypto driver is only working in kernel space it may also decrease the performance due the kernel/userspace memory transfer and context switch overhead
and yes, kong uses the same sources but may have done local modifications. but he contributes back them. _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
ahm i introduced the cryptodev support, not kong.
for all kernel based crypto its always enabled.
but userspace openvpn you can set "nvram set use_crypto=1;nvram commit" then openvpn will use hw crypto, but since the crypto driver is only working in kernel space it may also decrease the performance due the kernel/userspace memory transfer and context switch overhead
and yes, kong uses the same sources but may have done local modifications. but he contributes back them.
So would you recommend using crypto or not? Im trying to use vpn using Kongs mod to see if the firmware had something to do with vpn not working on my device.
ahm i introduced the cryptodev support, not kong.
for all kernel based crypto its always enabled.
but userspace openvpn you can set "nvram set use_crypto=1;nvram commit" then openvpn will use hw crypto, but since the crypto driver is only working in kernel space it may also decrease the performance due the kernel/userspace memory transfer and context switch overhead
and yes, kong uses the same sources but may have done local modifications. but he contributes back them.
So would you recommend using crypto or not? Im trying to use vpn using Kongs mod to see if the firmware had something to do with vpn not working on my device.
ahm i introduced the cryptodev support, not kong.
for all kernel based crypto its always enabled.
but userspace openvpn you can set "nvram set use_crypto=1;nvram commit" then openvpn will use hw crypto, but since the crypto driver is only working in kernel space it may also decrease the performance due the kernel/userspace memory transfer and context switch overhead
and yes, kong uses the same sources but may have done local modifications. but he contributes back them.
So would you recommend using crypto or not? Im trying to use vpn using Kongs mod to see if the firmware had something to do with vpn not working on my device.
I know one setting that will cause issues with some vpn providers, will probably add an experimental fix soon.
How would I edit the calibration data or Overclock this router I'm really curious lol. Also is there a way to get Tx above 30?
Posted: Sat Jun 17, 2017 0:39 Post subject: Re: vlan on r9000
navigates wrote:
I tried setting up vlan on the UI for port 20 as well and it didn't work. Has any one been successful with vlan tagging with dd-wrt on the r9000 / x10?
I respond this post because I'm desperate (like others users of R9000 with DD-WRT).
From my point of view one of the basic features of DD-WRT not working me. This feature is VLAN assignment for WAN Interface. My ISP (Movistar) use pppoe and vlan tag, like most FTTH/FTTP ISP in the world.
The parameters just for Internet connection are easy:
User:adslppp@telefonicanetpa
Pass:adslppp
And tag number 6 priority 1
Like comment for the other users (http://www.dd-wrt.com/phpBB2/viewtopic.php?t=305025 pages 24-25), If you check the GUI the VLAN 2 is the WAN Interface, but on the shell the information are diferent (Show VLAN1)
I change a few times the firmware, from standard to Kong and vice versa and I using now the last KONG Version (v3.0 r-32170M kongal) but still diferences over the GUI and the Shell
So I configure with the GUI the PPPoE user and tag 6 over VLAN 2 (See the picture on the attachement)
After this I use this configuration (I apply differents configuration this is last one)
swconfig dev switch0 vlan 2 set vid 6
swconfig dev switch0 vlan 2 set ports '0 5t'
swconfig dev switch0 vlan 1 set ports '0t 1 2 4t 6t'
swconfig dev switch0 set apply
vconfig add eth0 6
ifconfig vlan6 up
brctl addif br1 vlan6
And nothing, after spent two weeks with many changes, I'll return to stock firmware . (Unfortunately many user of this post return to stock, because DD-WRT not working correctly.....)
Posted: Sun Jun 18, 2017 22:37 Post subject: Maybe this is a DDWRT bug?
My ISP switched to native IPV6 recently so it works great now on my stock firmware.
Anyways, I bypass my ATT gateway device by using a VLAN switch. Once my ATT RG is authorized, I switch the VLAN to my router which has the MAC address of the ATT RG cloned. My R9000's WAN is in DHCP so it automatically gets the IP address and works great. No more ATT weird firewall issues (even in DMZ+/passthrough) and my ping time has dropped to 0.
Figured I'd try DDWRT again so I loaded up BrainSlayers newest build, copied my MAC address of the RG, and then tried to do the same thing and get it to grab the IP via DHCP.
It doesn't work. For some reason, on DDWRT, when I repeat the same process, it can't grab an IP on the WAN port. I have the MAC copied and everything. It just doesn't work. Anyways, I'm back on the latest stock firmware....by the way, is it possible to update the DDWRT-to-stock firmware to the most recent Netgear firmware?