Are there any network guys on here that could help me diagnose and unusual issue?
Timeline
Post
Remote status
Context
6
What's up?
It appears to have cleared up, but the problem was:
Multiple computers running on home internet, problem only affects one, so likely not issue with router.
Youtube streaming music on Brave, so full connectivity exists.
Problem: On Brave and on Edge, internet connectivity errors flag when conducting a Search, or when attempting to make a Poast Comment or extended-react. Email appears to be slow as well.
But that's it. Connectivity appears to be normal, but "internet connectivity problem" flags pop-up for some-but-not-all normal usage.
@Handy @shawnkhall @trucku
Multiple computers running on home internet, problem only affects one, so likely not issue with router.
Youtube streaming music on Brave, so full connectivity exists.
Problem: On Brave and on Edge, internet connectivity errors flag when conducting a Search, or when attempting to make a Poast Comment or extended-react. Email appears to be slow as well.
But that's it. Connectivity appears to be normal, but "internet connectivity problem" flags pop-up for some-but-not-all normal usage.
@Handy @shawnkhall @trucku
Hmmmm...
If it's really only affecting one computer, and others on the home network are also able to do the exact same things without issue, I would say three possible issues:
1. That computer has TCP stack gremlins -> Reboot
2. That computer has a slightly more shoddy wifi card than others and it's having trouble today -> Try connecting a cable if you can
3. NAT gremlins -> Reboot the router
Or, since you said it's a flag that's popping up (I guess windows), maybe different windows version is more touchy than normal about what it thinks is a "connectivity problem"... Do you experience actual verifiable issues, or is it just the popup?
If it's really only affecting one computer, and others on the home network are also able to do the exact same things without issue, I would say three possible issues:
1. That computer has TCP stack gremlins -> Reboot
2. That computer has a slightly more shoddy wifi card than others and it's having trouble today -> Try connecting a cable if you can
3. NAT gremlins -> Reboot the router
Or, since you said it's a flag that's popping up (I guess windows), maybe different windows version is more touchy than normal about what it thinks is a "connectivity problem"... Do you experience actual verifiable issues, or is it just the popup?
Still habbening...
Example: if I try to click the puke react (here on Poast), it's in an extended list, which requires opening a separate (window?). Poast will open an error page detailing network connectivity issues.
I rebooted the machine. I'll try rebooting the router next. Rebooting the router should have been one of the first things I did, but I was curious about what could have caused such specific, localized problems.
Example: if I try to click the puke react (here on Poast), it's in an extended list, which requires opening a separate (window?). Poast will open an error page detailing network connectivity issues.
I rebooted the machine. I'll try rebooting the router next. Rebooting the router should have been one of the first things I did, but I was curious about what could have caused such specific, localized problems.
That did it. Restarted router.
Routers do a couple of things beyond just batting packets in the right direction like a tennis player.
The first is NAT (Network Address Translation) - you only get 1 IPv4 address for your household because "we're out of those", and so everyone at home gets a 192.168.X.X address, and when you connect to a website, the NAT removes your address (because that would never work) and replaces it with it's own, but it also does some clever tactics to see who you are talking to, so that when a reply comes back, it can forward it back to the right computer on the local network. This requires tracking every active communication session. Normally it expires sessions which are inactive for a while, and then it stays in harmony, but if there are too many sessions at the same time, it can run out of memory to track new sessions. When this happens the symptoms are weird.
The second thing it does is QoS - because if you're making in a call and downloading a movie at the same time, you have a limited bandwidth and you really don't want the call to glitch just so the movie can download a little faster. So there's a whole ton of shit that happens in the router to prioritize each session vis a vis one another. And those sessions get batched based on the remote (website), local (computer), session ID, and what type of application it is (video call vs. email vs. download...). So that's another thing that can potentially get gummed up.
TLDR: Off and back on again remains undefeated...
The first is NAT (Network Address Translation) - you only get 1 IPv4 address for your household because "we're out of those", and so everyone at home gets a 192.168.X.X address, and when you connect to a website, the NAT removes your address (because that would never work) and replaces it with it's own, but it also does some clever tactics to see who you are talking to, so that when a reply comes back, it can forward it back to the right computer on the local network. This requires tracking every active communication session. Normally it expires sessions which are inactive for a while, and then it stays in harmony, but if there are too many sessions at the same time, it can run out of memory to track new sessions. When this happens the symptoms are weird.
The second thing it does is QoS - because if you're making in a call and downloading a movie at the same time, you have a limited bandwidth and you really don't want the call to glitch just so the movie can download a little faster. So there's a whole ton of shit that happens in the router to prioritize each session vis a vis one another. And those sessions get batched based on the remote (website), local (computer), session ID, and what type of application it is (video call vs. email vs. download...). So that's another thing that can potentially get gummed up.
TLDR: Off and back on again remains undefeated...
Replies
0
No replies yet.