Please try to ping in internet let’s say 8.8.8.8 from the router and post the result
Also try to do traceroute to the same 8.8.8.8 and post the result here
Unfortunately lots of users work on the network, so I can do testing only at the evening. (Or setup separate ports and use load balancing, or something like that to avoid downtime, but I don’t want to make it more complicated. I hope there is only a tiny mistake, and we can find it out easily.)
I can add further details, and I hope it helps:
We have another WAN connection working: that’s a symmetric 4/4Mbit leased line and probably ping would succed and would be routed via this line instead of the Dynamic IP WAN.
In the routes we use 2 rules for PPPoE: 1 dynamic (distance: ‘0’; also set to ‘0’ for DHCP Client) and 1 static for “HTTP” mark out with distance set to ‘1’.
Yesterday night when I did the test as mentioned above, the PING worked, but browsing failed, could it be some kind of routing problem? Am I using the recommended setup for Dynamic IP based WAN setup?
Update:
I’ve prepared the new WAN connection on another port and added the NAT and ROUTE rules as mentioned above.
Ping results:
Timeout/Host unreachable.
Tracert results:
timeout, and tries again and again with the dynamic IP of the new WAN IF. (Next hop should be the gateway of the Dynamic IP connection, shouldn’t it?)
I’ve just noticed that a dynamic, static route is created for the DHCP Client with distance value: 1.
Perhaps the routes should be modified to make it work?
I thought replacing PPPoE with Dynamic IP WAN is a simple process, maybe I was wrong… )
You said somewhere that you were able to ping but you could not browse, and it would fail immediately. that’s usually the case when you have dns resolving problem. open cmd.exe in windows and type nslookup . see if you can resolve any domain. for example google.com . if it failed but you can still ping for example 8.8.8.8 , its dns issue.
Ping works only via the primary WAN (4Mbit symmetric leased line), and the connection uses its DNS addresses, so no problem with DNS. I think its routing/NAT related, because HTTP traffice should be routed via the fast cheap WAN, but currently that fails.
And as I mentioned above the ping and tracert tests are failing via the new WAN’s interface in WinBox too…