2 ms·
Honestly, that experience was years ago, and I don't really care enough to raise a fuss about it just today, since their first-party router is "not too terrible
by LoganDark 4y ago
Honestly, that experience was years ago, and I don't really care enough to raise a fuss about it just today, since their first-party router is "not too terrible".
About Xfinity in particular though, assuming someone else uses them, I did learn just recently that at least Xfinity allegedly offers a special decoder box (or something) that is, I believe, free of charge, and lets you hook up your router directly rather than putting it through theirs as a DMZ, and it's supposed to get them to not cut the line. Some self-install kit or something. You can only get it by asking over phone call.
- baobrien 4y agoI bought my own 3rd party cable modem for Xfinity and it works fine.
- LoganDark 4y agoWell, in my situation/ISP it did happen. Though it was a while ago so I don't remember too many specifics.
- joecool1029 4y agoTwo guesses: 1. You had a modem that wasn't on their approved device list. It needs to be on this list to receive firmware customized to their network parameters. https://www.xfinity.com/support/devices/ https://www.xfinity.com/support/devices/ 2. (the most likely scenario) You were switching the macaddr of your router's WAN port every time you connected. For IPV4 Comcast was always set up to only allow one macaddr to bind to a public address at a time, you needed to trigger a dhcpcd release on the old macaddr before reconnecting or clone the mac of the old device if switching.