Cannot access server-side LAN

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
SomeRandomGuy
Posts: 2
Joined: Fri Dec 01, 2017 9:49 pm

Cannot access server-side LAN

Post by SomeRandomGuy » Fri Dec 01, 2017 10:07 pm

I've setup SoftEther VPN Server on a Raspberry Pi 1. I can remotly connect to it via the built-in indows VPN Client and access the internet through my server. But I fail to connect to any computer in my server's lan besides the router (192.168.1.1).

I set up a virtual hub called "hub" and an local bridge between "hub" and "eth0". The internal IP of my server is 192.168.1.200.

Last hundred lines of the log. The log file is 3MB in total. The pattern below repeats itself:

2017-12-01 21:35:24.770 [HUB "hub"] SecureNAT: The UDP session 3288 has been created. Connection source 192.168.1.200:58475, Connection destination 255.255.255.255:3702
2017-12-01 21:35:24.780 [HUB "hub"] SecureNAT: The UDP session 3289 has been created. Connection source 192.168.1.200:60439, Connection destination 255.255.255.255:3702
2017-12-01 21:35:24.780 [HUB "hub"] SecureNAT: The UDP session 3290 has been created. Connection source 192.168.1.200:44401, Connection destination 255.255.255.255:3702
2017-12-01 21:35:24.790 [HUB "hub"] SecureNAT: The UDP session 3291 has been created. Connection source 192.168.1.200:39316, Connection destination 255.255.255.255:1900
2017-12-01 21:35:24.800 [HUB "hub"] SecureNAT: The UDP session 3292 has been created. Connection source 192.168.1.200:47980, Connection destination 255.255.255.255:3702
2017-12-01 21:35:24.800 [HUB "hub"] SecureNAT: The UDP session 3293 has been created. Connection source 192.168.1.200:51583, Connection destination 255.255.255.255:1900
2017-12-01 21:35:24.810 [HUB "hub"] SecureNAT: The UDP session 3294 has been created. Connection source 192.168.1.1:138, Connection destination 255.255.255.255:138
2017-12-01 21:35:25.289 [HUB "hub"] SecureNAT: The UDP session 3295 has been created. Connection source 192.168.1.200:51521, Connection destination 255.255.255.255:138
2017-12-01 21:35:25.301 [HUB "hub"] SecureNAT: The UDP session 3296 has been created. Connection source 192.168.1.200:43837, Connection destination 255.255.255.255:1900
2017-12-01 21:35:25.311 [HUB "hub"] SecureNAT: The UDP session 3297 has been created. Connection source 192.168.1.200:54777, Connection destination 255.255.255.255:3702
2017-12-01 21:35:25.311 [HUB "hub"] SecureNAT: The UDP session 3298 has been created. Connection source 192.168.1.200:54586, Connection destination 255.255.255.255:3702
2017-12-01 21:35:25.321 [HUB "hub"] SecureNAT: The UDP session 3299 has been created. Connection source 192.168.1.200:55563, Connection destination 255.255.255.255:1900
2017-12-01 21:35:25.331 [HUB "hub"] SecureNAT: The UDP session 3300 has been created. Connection source 192.168.1.200:51890, Connection destination 255.255.255.255:3702
2017-12-01 21:35:25.341 [HUB "hub"] SecureNAT: The UDP session 3301 has been created. Connection source 192.168.1.200:56295, Connection destination 255.255.255.255:3702
2017-12-01 21:35:25.413 [HUB "hub"] SecureNAT: The UDP session 2093 has been deleted.
2017-12-01 21:35:25.423 [HUB "hub"] SecureNAT: The UDP session 2094 has been deleted.
2017-12-01 21:35:25.434 [HUB "hub"] SecureNAT: The UDP session 2097 has been deleted.
2017-12-01 21:35:25.474 [HUB "hub"] SecureNAT: The UDP session 2086 has been deleted.
2017-12-01 21:35:25.484 [HUB "hub"] SecureNAT: The UDP session 2090 has been deleted.
2017-12-01 21:35:25.525 [HUB "hub"] SecureNAT: The UDP session 2089 has been deleted.
2017-12-01 21:35:25.536 [HUB "hub"] SecureNAT: The UDP session 2087 has been deleted.
2017-12-01 21:35:25.597 [HUB "hub"] SecureNAT: The UDP session 2091 has been deleted.
2017-12-01 21:35:25.607 [HUB "hub"] SecureNAT: The UDP session 2095 has been deleted.
2017-12-01 21:35:25.628 [HUB "hub"] SecureNAT: The UDP session 2096 has been deleted.
2017-12-01 21:35:25.762 [HUB "hub"] SecureNAT: The UDP session 2088 has been deleted.
2017-12-01 21:35:25.906 [HUB "hub"] SecureNAT: The UDP session 2092 has been deleted.
2017-12-01 21:35:25.957 [HUB "hub"] SecureNAT: The UDP session 3302 has been created. Connection source 192.168.1.200:50348, Connection destination 255.255.255.255:1900
2017-12-01 21:35:25.967 [HUB "hub"] SecureNAT: The UDP session 3303 has been created. Connection source 192.168.1.200:42653, Connection destination 255.255.255.255:138
2017-12-01 21:35:25.967 [HUB "hub"] SecureNAT: The UDP session 3304 has been created. Connection source 192.168.1.200:45278, Connection destination 255.255.255.255:3702
2017-12-01 21:35:25.977 [HUB "hub"] SecureNAT: The UDP session 3305 has been created. Connection source 192.168.1.200:54862, Connection destination 255.255.255.255:3702
2017-12-01 21:35:25.987 [HUB "hub"] SecureNAT: The UDP session 3306 has been created. Connection source 192.168.1.200:54751, Connection destination 255.255.255.255:3702
2017-12-01 21:35:25.987 [HUB "hub"] SecureNAT: The UDP session 3307 has been created. Connection source 192.168.1.200:49926, Connection destination 255.255.255.255:1900
2017-12-01 21:35:25.998 [HUB "hub"] SecureNAT: The UDP session 3308 has been created. Connection source 192.168.1.200:42283, Connection destination 255.255.255.255:3702
2017-12-01 21:35:26.038 [HUB "hub"] SecureNAT: The UDP session 2112 has been deleted.
2017-12-01 21:35:26.048 [HUB "hub"] SecureNAT: The UDP session 2110 has been deleted.
2017-12-01 21:35:26.090 [HUB "hub"] SecureNAT: The UDP session 2104 has been deleted.
2017-12-01 21:35:26.111 [HUB "hub"] SecureNAT: The UDP session 2109 has been deleted.
2017-12-01 21:35:26.151 [HUB "hub"] SecureNAT: The UDP session 2102 has been deleted.
2017-12-01 21:35:26.184 [HUB "hub"] SecureNAT: The UDP session 2113 has been deleted.
2017-12-01 21:35:26.256 [HUB "hub"] SecureNAT: The UDP session 2114 has been deleted.
2017-12-01 21:35:26.297 [HUB "hub"] SecureNAT: The UDP session 2098 has been deleted.
2017-12-01 21:35:26.307 [HUB "hub"] SecureNAT: The UDP session 2106 has been deleted.
2017-12-01 21:35:26.409 [HUB "hub"] SecureNAT: The UDP session 2101 has been deleted.
2017-12-01 21:35:26.441 [HUB "hub"] SecureNAT: The UDP session 2111 has been deleted.
2017-12-01 21:35:26.492 [HUB "hub"] SecureNAT: The UDP session 2099 has been deleted.
2017-12-01 21:35:26.577 [HUB "hub"] SecureNAT: The UDP session 2107 has been deleted.
2017-12-01 21:35:26.587 [HUB "hub"] SecureNAT: The UDP session 2103 has been deleted.
2017-12-01 21:35:26.598 [HUB "hub"] SecureNAT: The UDP session 2108 has been deleted.
2017-12-01 21:35:26.659 [HUB "hub"] SecureNAT: The UDP session 2100 has been deleted.
2017-12-01 21:35:26.679 [HUB "hub"] SecureNAT: The UDP session 2105 has been deleted.
2017-12-01 21:35:26.689 [HUB "hub"] SecureNAT: The TCP session 3132 has been deleted.
2017-12-01 21:35:26.711 [HUB "hub"] SecureNAT: The UDP session 3309 has been created. Connection source 192.168.1.200:36754, Connection destination 255.255.255.255:3702
2017-12-01 21:35:26.711 [HUB "hub"] SecureNAT: The UDP session 3310 has been created. Connection source 192.168.1.200:57159, Connection destination 255.255.255.255:138
2017-12-01 21:35:26.721 [HUB "hub"] SecureNAT: The UDP session 3311 has been created. Connection source 192.168.1.200:46436, Connection destination 255.255.255.255:3702
2017-12-01 21:35:26.731 [HUB "hub"] SecureNAT: The UDP session 3312 has been created. Connection source 192.168.1.200:33387, Connection destination 255.255.255.255:1900
2017-12-01 21:35:26.731 [HUB "hub"] SecureNAT: The UDP session 3313 has been created. Connection source 192.168.1.200:51112, Connection destination 255.255.255.255:1900
2017-12-01 21:35:26.742 [HUB "hub"] SecureNAT: The UDP session 3314 has been created. Connection source 192.168.1.200:38563, Connection destination 255.255.255.255:3702
2017-12-01 21:35:26.752 [HUB "hub"] SecureNAT: The UDP session 3315 has been created. Connection source 192.168.1.200:33901, Connection destination 255.255.255.255:3702
2017-12-01 21:35:26.823 [HUB "hub"] SecureNAT: The UDP session 2116 has been deleted.
2017-12-01 21:35:26.843 [HUB "hub"] SecureNAT: The UDP session 2129 has been deleted.
2017-12-01 21:35:26.854 [HUB "hub"] SecureNAT: The UDP session 2118 has been deleted.
2017-12-01 21:35:26.874 [HUB "hub"] SecureNAT: The UDP session 2124 has been deleted.
2017-12-01 21:35:26.925 [HUB "hub"] SecureNAT: The UDP session 2128 has been deleted.
2017-12-01 21:35:26.935 [HUB "hub"] SecureNAT: The UDP session 2119 has been deleted.
2017-12-01 21:35:26.945 [HUB "hub"] SecureNAT: The UDP session 2127 has been deleted.
2017-12-01 21:35:26.945 [HUB "hub"] SecureNAT: The UDP session 2130 has been deleted.
2017-12-01 21:35:26.957 [HUB "hub"] SecureNAT: The UDP session 2121 has been deleted.
2017-12-01 21:35:26.978 [HUB "hub"] SecureNAT: The UDP session 2122 has been deleted.
2017-12-01 21:35:27.071 [HUB "hub"] SecureNAT: The UDP session 2117 has been deleted.
2017-12-01 21:35:27.182 [HUB "hub"] SecureNAT: The UDP session 2125 has been deleted.
2017-12-01 21:35:27.213 [HUB "hub"] SecureNAT: The UDP session 2126 has been deleted.
2017-12-01 21:35:27.244 [HUB "hub"] SecureNAT: The UDP session 2115 has been deleted.
2017-12-01 21:35:27.381 [HUB "hub"] SecureNAT: The UDP session 2120 has been deleted.
2017-12-01 21:35:27.391 [HUB "hub"] SecureNAT: The UDP session 2123 has been deleted.

piracik
Posts: 9
Joined: Sat Dec 02, 2017 9:51 am

Re: Cannot access server-side LAN

Post by piracik » Sat Dec 02, 2017 10:04 am

Maybe turn off the firewall

SomeRandomGuy
Posts: 2
Joined: Fri Dec 01, 2017 9:49 pm

Re: Cannot access server-side LAN

Post by SomeRandomGuy » Sun Dec 03, 2017 4:42 pm

Thank you for your reply. Firewall was already disabled

fenice
Posts: 183
Joined: Sun Jul 19, 2015 4:23 pm

Re: Cannot access server-side LAN

Post by fenice » Sun Dec 03, 2017 5:54 pm

SomeRandomGuy wrote:
> Thank you for your reply. Firewall was already disabled

Have you specified the Default Gateway, DCHP settings and an IP for the secureNAT and is your inbound connection getting an IP address? I'm not suggesting you set-up the following but it does show the SecureNAT settings: https://majornetwork.net/2015/05/softet ... ress-pool/

[edit]I've just noticed that you mention having a Bridge and you don't, by any chance, have SecureNAT enabled as well do you? If you do you should not do that, either use a bridge or SecureNAT not both.
Regards


Bill

thisjun
Posts: 2458
Joined: Mon Feb 24, 2014 11:03 am

Re: Cannot access server-side LAN

Post by thisjun » Mon Dec 11, 2017 8:14 am

Please do not use localbridge and SecureNAT at same time.
It may make loop.

Post Reply