Hey guys. So I do basic networking for small businesses and ive been noticing something from the only isp in town that is barely hurting anything, but it is nonetheless. So anyway, I notice that if i have a computer, any computer, plugged in, sometimes it doesn't want to work at all. When it does this, if I run an ifconfig command, ill get an address 192.168.1.2 /24 which is weird becayse under normal circumstances, the internal address of the modem is 192.168.100.1 /24 aka different subnet. Normally i get a public ip address plugging the computer into the modem.
The plot thickens. When it does connect, if i ping 4.2.2.1 I consistently get packet loss. Nothing too crazy, but it shouldnt be happening. But yo if i plug a router in there, it works 100% of the time. And no packet loss. Today when I ran an if dhcpcd (a linux based dhcp client), i got what i hope to be the smoking gun (pictured).
So my question is, is s why the fuck does,a,router make it work better? He'll, even my own 35 dollar walmart router works better than no router at all. What gives? I have a theory, which may be totally wrong, i don't know. So, the cable modem can offer clients internal addresses (ive gotten 192.168.1.2 addresses from it) but it can also offer a public address, which it always does if you plug a computer in (normally). The address of the computer and the modem are usually different as evidenced by running an ifconfig command (ipconfig for winnders) and referencing that to a google search "what is my ip". If you get a router, however, and look at the internet settings on it, under dhcp or static, in the static spot it has the same address as the same google search. To elaborate, you can select dhcp or static on thw router gui page. Therein, you can also enter static ip address info. It comes prepopulated with the current info obtained via dhcp.
Is the modem issuing the router a local address instead of having two public addresses, one for the modem and one for the router, as it would be on a computer? There then would be a router to route across subnets (192.168.100.1/24 and 192.168.1.1/24). The computer wouldnt be able to do that since its not a router. That would explain why computers sometimes wouldnt want to connect, but not why it would connect and have 4% packet loss. Fuck me, man.
Heres why this isnt in home networking. This isn't about home networking. This is,not,about small business networking. This is about enterprise level shit, brah. This is service for an entire city were dealing with. I've called before but you know cable companies they all suck. So after i get a couple more examples, ill call them again.
In the picture, the dhcpv6 reply is from the cmts at our cable companys headend. Its pretty much the last router before hitting the cables running to your house.
No comments:
Post a Comment