Hi
After connecting the SoftEther VPN Client the routing table is update.
We have some local broadcast communication on the client that stops working after the SoftEther client is connected to the server.
It’s there any way that we can connect without that the local broadcast communication is update?
mvh
Jarle.
Broadcast
-
- Posts: 6
- Joined: Thu Jan 21, 2016 8:59 pm
Re: Broadcast
Seems that the broadcast is redirected to the external network?
-
- Posts: 6
- Joined: Thu Jan 21, 2016 8:59 pm
Re: Broadcast
Not anybody that can help with this?
-
- Posts: 42
- Joined: Tue Jan 19, 2016 7:13 pm
Re: Broadcast
Jarleavloyp wrote:
> Seems that the broadcast is redirected to the external network?
Are you referring to the clients keep alive transmission? If not needed you can disable it. https://www.softether.org/4-docs/1-manu ... _Functions
> Seems that the broadcast is redirected to the external network?
Are you referring to the clients keep alive transmission? If not needed you can disable it. https://www.softether.org/4-docs/1-manu ... _Functions
-
- Posts: 6
- Joined: Thu Jan 21, 2016 8:59 pm
Re: Broadcast
eastavin wrote:
> Jarleavloyp wrote:
> > Seems that the broadcast is redirected to the external network?
> Are you referring to the clients keep alive transmission? If not needed you can
> disable it.
> https://www.softether.org/4-docs/1-manu ... _Functions
Hi,
I'm refering to the route 224.0.0.0 240.0.0.0 On-link 192.168.30.54
The 192.168.30.0 is the external network. Seems like the broadcast is also route, this does not happen with our IPSEC VPN connection.
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.23.1 192.168.23.197 20
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.23.0 255.255.255.0 On-link 192.168.23.197 276
192.168.23.197 255.255.255.255 On-link 192.168.23.197 276
192.168.23.255 255.255.255.255 On-link 192.168.23.197 276
192.168.30.0 255.255.255.0 On-link 192.168.30.54 257
192.168.30.54 255.255.255.255 On-link 192.168.30.54 257
192.168.30.255 255.255.255.255 On-link 192.168.30.54 257
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.30.54 257
224.0.0.0 240.0.0.0 On-link 192.168.23.197 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.30.54 257
255.255.255.255 255.255.255.255 On-link 192.168.23.197 276
===========================================================================
Persistent Routes:
None
> Jarleavloyp wrote:
> > Seems that the broadcast is redirected to the external network?
> Are you referring to the clients keep alive transmission? If not needed you can
> disable it.
> https://www.softether.org/4-docs/1-manu ... _Functions
Hi,
I'm refering to the route 224.0.0.0 240.0.0.0 On-link 192.168.30.54
The 192.168.30.0 is the external network. Seems like the broadcast is also route, this does not happen with our IPSEC VPN connection.
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.23.1 192.168.23.197 20
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.23.0 255.255.255.0 On-link 192.168.23.197 276
192.168.23.197 255.255.255.255 On-link 192.168.23.197 276
192.168.23.255 255.255.255.255 On-link 192.168.23.197 276
192.168.30.0 255.255.255.0 On-link 192.168.30.54 257
192.168.30.54 255.255.255.255 On-link 192.168.30.54 257
192.168.30.255 255.255.255.255 On-link 192.168.30.54 257
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.30.54 257
224.0.0.0 240.0.0.0 On-link 192.168.23.197 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.30.54 257
255.255.255.255 255.255.255.255 On-link 192.168.23.197 276
===========================================================================
Persistent Routes:
None
-
- Posts: 42
- Joined: Tue Jan 19, 2016 7:13 pm
Re: Broadcast
I recall seeing something about this in the documentation. Just can't find it. Here are some ideas you will have to review for relevancy.
See 11.1.6 and 8 and 30
https://www.softether.org/4-docs/1-manu ... leshooting
See 3.4.8
https://www.softether.org/4-docs/1-manu ... _Functions
Background 1.4.1
https://www.softether.org/4-docs/1-manu ... ion_Method
That all I got. Maybe another reader can advise?
See 11.1.6 and 8 and 30
https://www.softether.org/4-docs/1-manu ... leshooting
See 3.4.8
https://www.softether.org/4-docs/1-manu ... _Functions
Background 1.4.1
https://www.softether.org/4-docs/1-manu ... ion_Method
That all I got. Maybe another reader can advise?
-
- Site Admin
- Posts: 2274
- Joined: Sat Mar 09, 2013 5:37 am
Re: Broadcast
Did you try to raise interface metric value than physical NIC?
-
- Posts: 6
- Joined: Thu Jan 21, 2016 8:59 pm
Re: Broadcast
Hi, did not try that will check this out.
Thanks.
cedar wrote:
> Did you try to raise interface metric value than physical NIC?
Thanks.
cedar wrote:
> Did you try to raise interface metric value than physical NIC?