I guess the only thing it could be is the verbosity setting of logging on the server side.
Adding a specific logging setting:
Code:
verb 3
Should work. The default is 1, which isn't much. 3-5 are usually good enough. Verb 6 and above is for debug purposes and outputs a lot of info. _________________ James
Main router:
Netgear R7000 overclocked to 1.2GHz - DD-WRT v3.0-r35965M kongac
IPv6 6in4 (HE.net), OpenVPN (with PBR and split tunnelling), Entware, dnsmasq with ipset
I guess the only thing it could be is the verbosity setting of logging on the server side.
Adding a specific logging setting:
Code:
verb 3
Should work. The default is 1, which isn't much. 3-5 are usually good enough. Verb 6 and above is for debug purposes and outputs a lot of info.
Yes the vpn clients are able to access the internet, ping the LAN clients and the LAN clients are able to ping the vpn clients or see each others shares.
The verb clause is already set to 5.
I wonder if it is the version that I am using that simply does not have this feature. I was looking at another dd-wrt vpn server I have and this is how it looks without a client connected. Can you see in the status area the headings just waiting there to receive information on connected clients, unlike the first ones which does not have those headings at all?
Interesting now that you showed me this I went and checked my own OpenVPN setup and found that I no longer have client logs in the status section either. My laptop is currently connected from my workplace so it should be there.
I remember it being present on 14929 but haven't really noticed it disappearing. The server log which is cut off still lists connections with client keys so its fine really.
openvpn_status.jpg
Description:
Filesize:
84.04 KB
Viewed:
10751 Time(s)
_________________ James
Main router:
Netgear R7000 overclocked to 1.2GHz - DD-WRT v3.0-r35965M kongac
IPv6 6in4 (HE.net), OpenVPN (with PBR and split tunnelling), Entware, dnsmasq with ipset
Interesting now that you showed me this I went and checked my own OpenVPN setup and found that I no longer have client logs in the status section either. My laptop is currently connected from my workplace so it should be there.
I remember it being present on 14929 but haven't really noticed it disappearing. The server log which is cut off still lists connections with client keys so its fine really.
Thanks. I was just pondering on going back to 14929. What version are you currently running? I am on 17201. Can't remember why I had selected this version but at the time it was important.
The ones with the headings I posted last hails back before 14929. It is a v12548 NEWD from eko.
I'm running 18730 this is special build for certain routers. (Kong Builds).
I found 14929 was very solid and worked great. Only downside was for me uPnP didn't seem work very well, QoS is broken but apart from that everything else is golden.
14929 is the recommended, so might be a good idea. I don't exactly know whats happened with the logs, but I might investigate further when I'm back at home later. _________________ James
Main router:
Netgear R7000 overclocked to 1.2GHz - DD-WRT v3.0-r35965M kongac
IPv6 6in4 (HE.net), OpenVPN (with PBR and split tunnelling), Entware, dnsmasq with ipset
I'm running 18730 this is special build for certain routers. (Kong Builds).
Just an informational update. I downgraded to 14929 and the missing client status from 17201 and your build it seems as well is there in 14929 as you remembered. So someone tweaked it after 14929. My only remorse is that 17201 was running openvpn 2.2.0 while this is stuck on 2.1.1
Connection tracking (I hope I have the right term)
-m conntrack --ctstate and -m state --state is broken and will not work at all in 14929.
That's another thing that is not working in this build.
the up script for openvpn also forcefully injects an iptable rule for tun0 and leaves it wide open which in my opinion does not make sense. It uses -I so it overrides any INPUT rule you put in the firewall commands window since openvpn starts after those rules have been added to the iptables. The only way to get rid of it is to delete it in the startup window where those commands seem to run only after all services have been started.
Interesting now that you showed me this I went and checked my own OpenVPN setup and found that I no longer have client logs in the status section either.
James you may be interested in this. I am here mucking about in the filesystem to see where they are hard-coding the firewall and port for openvpn in earlier version before 17201.
Excellent catch! Just changed the port to 5002 in my server.conf and the status section came back again!
Great find! This should be noted on the OpenVPN Wiki because before I remember it working with management on 5001. While only a cosmetic issue, its still note worthy for anyone using newer builds. _________________ James
Main router:
Netgear R7000 overclocked to 1.2GHz - DD-WRT v3.0-r35965M kongac
IPv6 6in4 (HE.net), OpenVPN (with PBR and split tunnelling), Entware, dnsmasq with ipset
Posted: Thu Sep 27, 2012 0:18 Post subject: Enable OpenVPN cause my 2.4Hz WLAN stop working
I am using 14929 on WRT610N V2 router. Everytime I apply OpenVPN, my 2.4 GHz wireless channel stop working. Simply disable OpenVPN won't recover 2.4Ghz wireless. I have to restore the previous backup settings(before OpenVPN enabled), but 5Ghz is ok. What should I do for trouble-shooting? I also have PPTP Server enabled, can they co-exist?