Community discussions

MikroTik App
 
ccrum
newbie
Topic Author
Posts: 31
Joined: Sun Jul 11, 2004 5:49 am

230 not resp on internet side but still passing traffic

Sun Jul 11, 2004 5:52 am

Here is a new one. I have a routerboard 230 running 2.8.11. Last night it
just quit responding to me on the interent side. I can`t ping it, telnet to
it, http to it, nothing. However, the wierdest thing is that my clients are
still able to get to the internet. I have rebooted the router twice, but it
still won`t show up to the internet. The clients don`t seem to be affected
as they can ping out to the internet, get to web sites, email, it seems like
everything. From the client side of the router, I can get to the winbox.
However, I can`t ping out to the internet from the ping tool itself even
though the router is passing traffic. If I look at the torch, it appears
that all the clients are sending and recieving data. Nobody has called to
complain about service outages which usually happens when I`m down for more
than 5 minutes. So, what the heck is going on here? Anyone ever seen this?
 
User avatar
lastguru
Member
Member
Posts: 432
Joined: Fri May 28, 2004 9:04 pm
Location: Certified Trainer/Consultant in Riga, Latvia
Contact:

Sun Jul 11, 2004 2:10 pm

maybe firewall's input or output policies have triggered to deny? Please check out the policies and try to disable everything you have in these firewall chains (input and output only; router's responsiveness is not affected by forward, and as clients can still use the Internet, it means that the forward it correct)
 
ccrum
newbie
Topic Author
Posts: 31
Joined: Sun Jul 11, 2004 5:49 am

Sun Jul 11, 2004 4:34 pm

I looked at all the firewall rules and there is nothing in output at all and only one thing in input. I'll try removing it. The chains are set to accept. Any more ideas? I'm beginning to think this is a routing problem with my upstream bandwidth provider, but they claim there is nothing wrong on their end.
 
Trisc
Member Candidate
Member Candidate
Posts: 242
Joined: Sat May 29, 2004 11:24 pm
Location: Glos, UK

Tue Jul 13, 2004 9:41 pm

It sounds similar to a problem we have seen with IP routes where the public interface on the default route changes to a PPPoE user's interface for no apparent reason.

We have to remove both interfaces and re-enter the default route to get it working again.

Who is online

Users browsing this forum: Ahrefs [Bot], ivicask, rjuho, VinceKalloe and 88 guests