Beiträge von orpheus

You're right as always tekkb, my fault all the way thanks for opening my mind

I was keeping the router's default DHCP (192.168.0.x/24) and in the same time manually forcing the Open VPN AS to provide the same 192.168.0.x/24 for the clients, instead of just creating a link between the router's LAN IP pool and the VPN IP pool.

In case others might experience similar issues, just read here: http://openvpn.net/index.php/o…tation/howto.html#vpntype:

The best solution is to avoid using 10.0.0.0/24 or 192.168.0.0/24 as private LAN network addresses. Instead, use something that has a lower probability of being used in a WiFi cafe, airport, or hotel where you might expect to connect from remotely. The best candidates are subnets in the middle of the vast 10.0.0.0/8 netblock (for example 10.66.77.0/24).

The topic can be closed.

Thanks for the suggestions guys!

I finally have 2 days off work, so I will try to get to the bottom of this. I will try to use wireshark and see what I can find out, it will be a new challenge for me

Here is what I managed to find out so far:

- I am able to constantly ping the router's DHCP IP address, but when trying to access it via http it works but only intermittently (a couple of minutes it's reachable, a couple not) - no timeouts on ping - very strange

- if I set the DNS servers (either 8.8.8.8 or 8.8.4.4) manually on the router or on the PC, the internet works without interruption, but only the router's settings page remains intermittently not accessible

- somehow, the OMV box cannot access the internet intermittently, even if I manually set up the DNS servers - I did some apt-get update via ssh with putty and sometimes it worked, but sometimes it got errors like:
Err http://security.debian.org wheezy/updates Release.gpg
Something wicked happened resolving 'security.debian.org:http' (-5 - No address associated with hostname)

I will keep you updated after trying wireshark and also removing some OMV plugins one by one. I suspect one of them, but not sure which

=========================================================================================================

Found the guilty bastard !!! It's the OpenVPN AS plugin - if the server is set to OSI layer 3 with NAT it somehow manages to create chaos on the router's hardware NAT. If I stop the server, or switch to layer 2, everything is working fine.

What I found out with wireshark - a lot of - [TCP Spurious Retransmission] 52768→80 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=4 SACK_PERM=1 when I couldn't connect via http to the router.

I still don't understand why it happens intermittently - I guess it has something to do with the NAT refresh rate on the router, don't know exactly how NAT works.

Hello all,

I have an issue with my OMV NAS similar with this Internet connection dies when OMV box is attached
But the solution posted there is not an option for me. I have also searched for similar posts on the forum but couldn't find any.

The details are:

- 1 router connected directly to the ISP and some computers connected to it, both wireless and cable, including the NAS.

- after a few minutes from the startup of the NAS system, the internet stops working on all the devices connected to the router via wireless, then after a few minutes it works again and so on. I've already tried restarting the router, NAS, PC etc. On cable it's stable.

- issue: communication with router's DHCP gets blocked, and since the router's DHCP acts like DNS for the connected computers, the internet becomes unreacheable. Also, it means I cannot access the router's web interface for configuration. But what's even strange is that both DHCP and let's say google.com respond to ping even when I can't access the pages.

- a workaround that I found for the internet access, is to manually set up the DNS for the connection to 8.8.8.8 or 8.8.4.4, but that still doesn't solve the fact that I can't access the router's web interface.

- at first I thought it was related to the minidlna service because I stopped it and it appeared to be working, but apparently it was only a matter of timing, I stopped it when the loop was back on the "now it's working" time.

- also I saw that the Transmission client is not able to connect to trakers - this is permanent, it's not having the working/not working loop.

Any thoughts on this? Maybe a known issue? Please let me know if you need more details. Thanks!

Regards

Hello tekkb,

First of all I will start by saying that I am new to OMV and had a lot of trouble installing and configuring it in the past 2 weeks on my NAS system.
It was all mainly my fault for not gathering all the info before starting this NAS building project - I was installing it on USB stick so it got corrupted, then I read the forum 100 times to try and fix all the strange errors I found . Now I installed it on a small 20 gig S-ATA hdd that I had laying around and it works great.
I'm also not familiar with linux, so it was fun for me to learn some commands for managing packages, etc.

But anyways, I'll get to the point now: I think I know why omavoss had this issue, because I had it too today. I had to remove and then reinstall the openvpn-as today because it somehow made the NAS's local ip unreacheable to ping/anything else - it worked only when accessed via external IP with port forwarding, not sure why, but I'll dig into it.

When trying to reinstall it I had the same errors mentioned by johnyb in [SOLVED] OpenVPN Install Failure and by scopeeye in OpenVPN-as does not create an init.d-script
I did all the steps you guys talked about, without any luck.

Then I saw that the problem was caused by the fact that the "openvpn" user and all the groups created by the openvpn-as plugin, remained in the setup of omv and while reinstalling, it could not create the user again. After removing the user and groups, reinstallation and activation worked as expected. I found it out by looking at the /usr/local/openvpn_as/init.log file - it was referenced in the installation log:
Automatic configuration failed, see /usr/local/openvpn_as/init.log
You can configure manually using the /usr/local/openvpn_as/bin/ovpn-init tool.

I hope this helps Also, thank you for your hard work and dedication on this