>tracert 192.168.1.254
Tracing route to 192.168.1.254 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.xx.1
2 1 ms <1 ms <1 ms 192.168.1.254
Trace complete.
xx is not 1, but that is the ip address of my untangle server.
>tracert 192.168.1.254
Tracing route to 192.168.1.254 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.xx.1
2 1 ms <1 ms <1 ms 192.168.1.254
Trace complete.
xx is not 1, but that is the ip address of my untangle server.
Sorry, maybe I'm misunderstanding the issue. Is the issue that you can reach 192.168.1.254? Or you can't?
Attention: Support and help on the Untangle Forums is provided by
volunteers and community members like yourself.
If you need Untangle support please call or email support@untangle.com
I'm wondering why I can.
Thanks
James
You can since it is a routable IP address. The IP is the gateway of the Untangle WAN.
Attention: Support and help on the Untangle Forums is provided by
volunteers and community members like yourself.
If you need Untangle support please call or email support@untangle.com
Wouldn't I expect to see it in the current routes then?
Yes, in dev <NIC name> scope link
Attention: Support and help on the Untangle Forums is provided by
volunteers and community members like yourself.
If you need Untangle support please call or email support@untangle.com
I just got att fiber and if you still need help I can show you my setup. I changed the gateway to 0.254 so I could leave my .1 addresses still on untangle.