Re: [WISPA] www.google.com

2009-12-07 Thread os10rules
Is this something specific to the RB450/450G? I have the RB750 and I'm running 4.3 and having no issues. I'm using the RB750 on a 15Mbps/2Mbps cable connection with numerous pcq queues doing prioritization (no limiting) on outbound (queuing with no prioritization on the inbound) and I'm

Re: [WISPA] www.google.com

2009-12-07 Thread can...@believewireless.net
It's not specific to any board, as it happens on X86 and RB1000s as well. However, it only happens to customers using Mikrotik as their DNS server. On Mon, Dec 7, 2009 at 7:46 AM, os10ru...@gmail.com wrote: Is this something specific to the RB450/450G? I have the RB750 and I'm running 4.3

[WISPA] www.google.com

2009-12-06 Thread RickG
OK, 3 times in the past week that I've noticed I could not get to www.google.com via the web, nor ping it, and DNS could not resolve it. I COULD ping and resolve google.com. I tried changing my DNS to OpenDNS and Public DNS (4.2.2.1) but had the same results. M firewall is an RB450G running 4.3.

Re: [WISPA] www.google.com

2009-12-06 Thread Josh Luthman
I am having the same issue. We have a thread on Butch's MT list but it is just discussion. On 12/6/09, RickG rgunder...@gmail.com wrote: OK, 3 times in the past week that I've noticed I could not get to www.google.com via the web, nor ping it, and DNS could not resolve it. I COULD ping and

Re: [WISPA] www.google.com

2009-12-06 Thread Josh Luthman
But a quick fix is to flush your MT DNS then your PC. Should have mention that before, sorry. On 12/6/09, RickG rgunder...@gmail.com wrote: OK, 3 times in the past week that I've noticed I could not get to www.google.com via the web, nor ping it, and DNS could not resolve it. I COULD ping

Re: [WISPA] www.google.com

2009-12-06 Thread RickG
Ya, I think I mentioned it there already. I figured it may not be a Mikrotik problem so wanted to post here too. -RickG On Sun, Dec 6, 2009 at 10:39 PM, Josh Luthman j...@imaginenetworksllc.comwrote: I am having the same issue. We have a thread on Butch's MT list but it is just discussion.

Re: [WISPA] www.google.com

2009-12-06 Thread Josh Luthman
I'm quite confident it's MT. Introduced in 4.0. On 12/6/09, RickG rgunder...@gmail.com wrote: Ya, I think I mentioned it there already. I figured it may not be a Mikrotik problem so wanted to post here too. -RickG On Sun, Dec 6, 2009 at 10:39 PM, Josh Luthman

Re: [WISPA] www.google.com

2009-12-06 Thread RickG
Thanks Josh! I figured that out too but it didnt come back quickly but rather took a few mnutes. So I thought maybe it was coincidence and there is some other issue. The interesting part is that I changed my DNS settings on my PC so wouldnt that bypass any Mikrotik issues? -RickG On Sun, Dec 6,

Re: [WISPA] www.google.com

2009-12-06 Thread can...@believewireless.net
Seeing the same thing. Flushing the cache seems to fix it for a while. Looks like it's been a bug for a little while: http://forum.mikrotik.com/viewtopic.php?f=2t=35891 I'm going to try the script mentioned to flush the cache every 15 minutes. On Sun, Dec 6, 2009 at 10:57 PM, RickG

Re: [WISPA] www.google.com

2009-12-06 Thread can...@believewireless.net
Actually, I just noticed in MT that you can set the cache-max-ttl. So, I set it to 15 minutes. On Sun, Dec 6, 2009 at 11:11 PM, can...@believewireless.net p...@believewireless.net wrote: Seeing the same thing.  Flushing the cache seems to fix it for a while.  Looks like it's been a bug for a

Re: [WISPA] www.google.com

2009-12-06 Thread can...@believewireless.net
Some people think it has to do with the max UDP packet size so I increased mine to 768. Now... only time will tell. On Sun, Dec 6, 2009 at 11:13 PM, can...@believewireless.net p...@believewireless.net wrote: Actually, I just noticed in MT that you can set the cache-max-ttl. So, I set it to 15

Re: [WISPA] www.google.com

2009-12-06 Thread RickG
Where is that at? On Sun, Dec 6, 2009 at 11:13 PM, can...@believewireless.net p...@believewireless.net wrote: Actually, I just noticed in MT that you can set the cache-max-ttl. So, I set it to 15 minutes. On Sun, Dec 6, 2009 at 11:11 PM, can...@believewireless.net p...@believewireless.net

Re: [WISPA] www.google.com

2009-12-06 Thread RickG
Same here. I'll report back if it happens again. Thx! On Sun, Dec 6, 2009 at 11:26 PM, can...@believewireless.net p...@believewireless.net wrote: Some people think it has to do with the max UDP packet size so I increased mine to 768. Now... only time will tell. On Sun, Dec 6, 2009 at 11:13

Re: [WISPA] www.google.com

2009-12-06 Thread Josh Luthman
I set my max cache from 1w to 15m. On 12/6/09, RickG rgunder...@gmail.com wrote: Same here. I'll report back if it happens again. Thx! On Sun, Dec 6, 2009 at 11:26 PM, can...@believewireless.net p...@believewireless.net wrote: Some people think it has to do with the max UDP packet size so