What Are You Doing Right Now
-
Directly attached, no switch at all?
-
@Reid-Cooper said:
@coliver said:
Trying to figure out why my internal firewall is returning ping times of 2-300ms when it should be 0ms... I'm directly connected to it even. Jitter rate is in the 60-100% range too... something isn't right.
Oh now that's just not right. What kind of firewall is it?
Cisco/Meraki MX90.
-
@coliver said:
@Reid-Cooper said:
@coliver said:
Trying to figure out why my internal firewall is returning ping times of 2-300ms when it should be 0ms... I'm directly connected to it even. Jitter rate is in the 60-100% range too... something isn't right.
Oh now that's just not right. What kind of firewall is it?
Cisco/Meraki MX90.
Something is flooding the network it sounds like. Wireshark?
-
@Reid-Cooper said:
Directly attached, no switch at all?
Directly attached and not through a switch correct, from the punchdown directly over.
-
@coliver said:
@Reid-Cooper said:
Directly attached, no switch at all?
Directly attached and not through a switch correct, from the punchdown directly over.
Bad cabling then? Have you tried rebooting the Meraki? Maybe its cache is overloaded or something, and is causing issues. The FiOS router where I live I reboot nightly to clear the cache. Cleared up all kinds of issues.
-
@thanksajdotcom said:
@coliver said:
@Reid-Cooper said:
Directly attached, no switch at all?
Directly attached and not through a switch correct, from the punchdown directly over.
Bad cabling then? Have you tried rebooting the Meraki? Maybe its cache is overloaded or something, and is causing issues. The FiOS router where I live I reboot nightly to clear the cache. Cleared up all kinds of issues.
I don't think it is bad cabling, everything else on the network has appropriate response times. I've also done it via one of our VMs although that goes through a switch.
-
@coliver said:
@thanksajdotcom said:
@coliver said:
@Reid-Cooper said:
Directly attached, no switch at all?
Directly attached and not through a switch correct, from the punchdown directly over.
Bad cabling then? Have you tried rebooting the Meraki? Maybe its cache is overloaded or something, and is causing issues. The FiOS router where I live I reboot nightly to clear the cache. Cleared up all kinds of issues.
I don't think it is bad cabling, everything else on the network has appropriate response times.
Are you pinging it by IP or hostname?
-
@thanksajdotcom IP. Probably should start a new thread for troubleshooting.
-
Having a bit of apple pie with my custard
-
-
@thanksajdotcom said:
@coliver said:
@Reid-Cooper said:
Directly attached, no switch at all?
Directly attached and not through a switch correct, from the punchdown directly over.
Bad cabling then? Have you tried rebooting the Meraki? Maybe its cache is overloaded or something, and is causing issues. The FiOS router where I live I reboot nightly to clear the cache. Cleared up all kinds of issues.
That's pretty extreme. Why does a router have a cache? Other than a route cache, and how does one of those fill up post 1999?
-
@scottalanmiller said:
@thanksajdotcom said:
@coliver said:
@Reid-Cooper said:
Directly attached, no switch at all?
Directly attached and not through a switch correct, from the punchdown directly over.
Bad cabling then? Have you tried rebooting the Meraki? Maybe its cache is overloaded or something, and is causing issues. The FiOS router where I live I reboot nightly to clear the cache. Cleared up all kinds of issues.
That's pretty extreme. Why does a router have a cache? Other than a route cache, and how does one of those fill up post 1999?
Because FiOS routers are crap, despite they are supposed to be great. The router pre-nightly-reboot would work fine for 2-5 days before suddenly you couldn't access the web interface, network connections started dropping, and then it basically just crashed but didn't lose power. Then you'd have to hard power it off and back on and it'd work again for another 2-5 days. Since I setup a cron job to telnet in and reboot it nightly, we haven't had a single issue. Tell me what else it could possibly be, and I'm all ears.
-
-
Besides, the router was handling somewhere between 100 and 150GB of data transmission between up and down a day. FiOS connections may be able to handle that load, but their routers seem to become overloaded after a few days. I had the same issue with my FiOS router in Texas. Once I dropped it completely and went to my own router, the issue disappeared.
-
IT"S FRIDAYYY!!!! Getting ready to travel again.
-
@coliver said:
@thanksajdotcom said:
@coliver said:
Your computer is cabled and not over wifi, correct?
Correct.
So let me see if I got this right...
Cabled, pinging by IP, and this is basically how it flows?
Computer > patch panel > firewall
With that setup, you're getting 2-300ms response times that are somewhat random to the firewall, but everything else works fine?
-
@Minion-Queen said:
IT"S FRIDAYYY!!!! Getting ready to travel again.
Me too. Gibraltar in the morning, Cádiz tomorrow night.
-
@thanksajdotcom said:
@coliver said:
@thanksajdotcom said:
@coliver said:
Your computer is cabled and not over wifi, correct?
Correct.
So let me see if I got this right...
Cabled, pinging by IP, and this is basically how it flows?
Computer > patch panel > firewall
With that setup, you're getting 2-300ms response times that are somewhat random to the firewall, but everything else works fine?
Pretty much. Although VoIP is having some latency issues when calling out, internally it is working as expected, except for one user. Externally audio can be a bit choppy.
Every machine I've tested this with seems to have the same issue with latency when talking to the firewall, although not so much any other device on the network.
-
@thanksajdotcom said:
Because FiOS routers are crap, despite they are supposed to be great.
Mine in Texas worked fine. I replaced it for security reasons, but not because it wasn't fast.
-
@scottalanmiller said:
@thanksajdotcom said:
Because FiOS routers are crap, despite they are supposed to be great.
Mine in Texas worked fine. I replaced it for security reasons, but not because it wasn't fast.
Yes, but I doubt you had that volume of traffic going through your router from your home network on a daily basis. Like I said, usually around 150GB per day between up and down. I've seen Verizon routers run fine for months for people who just stream Netflix, browse the web and do the basics. But high levels of intensive use, and they just crack.
