Comments
-
I deleted "everything", rebootet and made the setup again. Now it seems to work. Thank you for your help :smile:
-
.
-
I wrote a Ticket, but no answer i thought it could be a Simple Problem. What i forgot even if i tracert to my Gateway on eth5 xxx.xxx.xxx.49 windows/firebox tries eth0 defualt gateway. If i trace tu xxx.xxx.xxx.50 one of the Network IP's on eth5 windows uses the correct Route: Routenverfolgung zu xxx.xxx.xxx.50 über…
-
No the traceroute in windows uses the default eth0 WAN xxx.xxx.xxx.141 1 1 ms <1 ms <1 ms 192.168.10.1 2 2 ms 3 ms 3 ms ip-xxx-xxx-xxx-225.um08.pools.vodafone-ip.de [xxx.xxx.xxx.225] And i'm a little bit perplexed what the error could be or what i could set in the firebox
-
Now i understood sorry. I did this on the firewalls traceroute: xxx.xxx.xxx.141 -i eth1 traceroute to xxx.xxx.xxx.141 (xxx.xxx.xxx.141), 30 hops max, 40 byte packets 1 xxx.xxx.xxx.49 1 ms 1 ms 3 ms 2 xx.xx.xx.xxx 268 ms 321 ms 321 ms Seems that it uses the correct Route also if i test this with eth0 eth2
-
Hello, thank you for the responses. @bruce_briggs, I don't quite understand. When I test with the firewall diagnostics, Traceroute uses the correct network port (eth5) when tracing to one of the networks behind the VPN. However, when I test it in Windows to the same network, it always uses the Default Network of the…