Hi all,

I 've got a Vigor 120 v2, which is connected to my ISP.From the LAN side, it's attached to a Mikrotik router. I've open some ports in th Vigor in order to access the mikrotik and another server,inside my LAN. I've changed the port for the web management of vigor, from 80 to 8080. So, i've made the port redirection in terms of

"mydomain:41254 --> internalIPofMikrotik:80"
"mydomain:41243 --> internalIPofMikrotik:41243" (mikrotik has a rule to forward this packet to the specific server)

i can access vigor from outside just fine,by using mydomain:8080

When I use mydomain:41254 or mydomain:41243 I get no response!
Strange thing is that these packets DOES arrives in Mikrotik router, I can see the requests while packet sniffering the mikrotik. Also, the replies, ARE leaving the mikrotik router to Vigor, I can see these packets too!!! But i get no response in my browser!

Replacing Vigor with another router everything works fine, so there is no error inside my LAN. For an unknown reason, REPLIES, are coming out of vigor to wan...


Any ideas???

you need to set a gateway / default route on the 120 for that to respond, I'm guessing you're using pppoE? if so this won't be too dangerous since it'll still work nicely as a local PPPoE server I used to have to do this with a speedtouch modem I was using.

in the vigor 120's telnet interface, enter for example if your router was 192.168.1.1:
ip route add 0.0.0.0 0.0.0.0 192.168.1.1 lan static

ip route add <destination IP> <subnet mask> <gateway> lan static

That should allow your port forwards to work

I am using PPPoA,according to ISP's directions.Don't know if this has something to do... I did what u said with the default gateway,but still I get no response...

try using the modem's ping diagnostics from telnet, I think it's "ip ping 8.8.8.8" to check whether it can ping or not

First of all thnks for the help.

Second, the modem can ping just fine but still the port forwarding is not working...

that's good If it's able to access the internet now then the problem is likely with the router now, I think, it might be worth re-testing what happens to the packets now?