"double bridge" setup will only work for 5 minutes
Posted: Fri Sep 19, 2014 12:19 pm
Hi,
i have some trouble with my "double bridge" setup. It works well for 5 minutes, and then, no more packets between vpn client and server are exchanged.
The setup is not very compicated, but maybe a bit "individuell *g
The softether server is configured to bridge to a tap_device (tap_soft).
On the vpn-server, i create a second bridge between eth0 and tap_soft.
The advantage of this setup is, that I can reach the vpn server though the vpn.
But after some time, the connection will not work anymore. (but the vpn-connection itself is connected)
For example, the "ping" from home-device --> vpn client will change:
64 bytes from 10.10.10.139: icmp_seq=148 ttl=128 time=40.9 ms
64 bytes from 10.10.10.139: icmp_seq=149 ttl=128 time=41.2 ms
From 10.10.10.115 icmp_seq=175 Destination Host Unreachable
From 10.10.10.115 icmp_seq=176 Destination Host Unreachable
or from vpn-client --> vpn server
...
Antwort von 10.10.10.100: Bytes=32 Zeit=36ms TTL=64
Zeitüberschreitung der Anforderung. (<-- "timeout")
...
Has somebody any idea, what could be the reason for this problem?
i have some trouble with my "double bridge" setup. It works well for 5 minutes, and then, no more packets between vpn client and server are exchanged.
The setup is not very compicated, but maybe a bit "individuell *g
The softether server is configured to bridge to a tap_device (tap_soft).
On the vpn-server, i create a second bridge between eth0 and tap_soft.
The advantage of this setup is, that I can reach the vpn server though the vpn.
But after some time, the connection will not work anymore. (but the vpn-connection itself is connected)
For example, the "ping" from home-device --> vpn client will change:
64 bytes from 10.10.10.139: icmp_seq=148 ttl=128 time=40.9 ms
64 bytes from 10.10.10.139: icmp_seq=149 ttl=128 time=41.2 ms
From 10.10.10.115 icmp_seq=175 Destination Host Unreachable
From 10.10.10.115 icmp_seq=176 Destination Host Unreachable
or from vpn-client --> vpn server
...
Antwort von 10.10.10.100: Bytes=32 Zeit=36ms TTL=64
Zeitüberschreitung der Anforderung. (<-- "timeout")
...
Has somebody any idea, what could be the reason for this problem?