Yup, connect the TP-Link to the modem and then connect to the TP-Link.
Use 192.168.100.1 thru the router. You can also use that with a direct connection to the modem when its in Bridge mode.
I don't encourage a direct connection to the modem when its in Bridge mode due to the constant port scanning by various miscreants scattered across the internet, probing for open ports or mis-configured firewalls.
With V2.0.10.36T6, in the modem as indicated on the status page, you can use 192.168.01. or 192.168.100.1 when the modem is in Gateway mode. When its in Bridge mode you can only use 192.168.100.1, which will normally work thru any connected router. There are exceptions but they are few and far between, so to speak.
With V7.1.1.30 loaded you can only use 192.168.0.1 when the modem is in Gateway mode and only use 192.168.100.1 when the modem is in Bridge mode.
@MD83 there are a few ways to do this.
First:
1. connect directly to the modem, even though I'm not a huge fan of this.
2. As soon as the pc/laptop gains an IP address, log into the modem using 192.168.100.1 I'm assuming that the modem is stuck in Bridge mode.
3. kick the modem back into Gateway mode when you've managed to log in.
Second:
Call tech support and ask the CSR to switch your modem back into Gateway mode
Third.
Reset the modem. Ugh. Depress the recessed reset button at the back of the modem for at least 15 seconds. It should reset the modem, at which point the modem will reboot into Gateway mode. Unfortunately you would have to set the modem up from scratch.
With the modem in Bridge mode, if you rebooted the TP-Link router it should pick up its assigned external address from the modem and you should be able to use 192.168.100.1 to access the modem's login page. If you can't, then the TP-Link is blocking the path out to the modem. Usually thats taken care of by defining a route out to the modem, but, I don't know if the TP-Link will let you do that.
@savuser12 can you delete the HFC MAC Address data as it shouldn't be posted to an open forum. Can you also post the upstream channel data that sits below the OFDM channel data. There should be three or four upstream channels running.
@MD83 I'm assuming that Rogers is using that 45.xxx.xxx.xxx block internally, which is a little odd, but, it is what it is.
Just to see whats up, and not worry about any confusion with the modem or TP-Link configuration, try pinging Rogers primary IPV4 DNS: 64.71.255.204
I'd let that run in the background while you're running the normal household internet activities. That might cause higher latency, but, I suspect the family would revolt if you said, "no internet for an hour!" Ok, so, run:
ping -n 3600 64.71.255.204
Lets see how that turns out.
@savuser12 your DOCSIS 3.0 channels (1 to 32) are higher than they should be, arguably within spec, yes, but, then should be down around 0 dBmV. Your QAM levels are ok, the signal to noise ratios are ok as well.
The upstream DOCSIS 3.0 levels aren't too bad where they currently sit.
The DOCSIS 3.1 OFDM channel can't be assessed as the signal level, signal to noise ratio and QAM Level isn't presented to the user. Tech support has access to that data, and I would expect the field techs to have access to that data as well.
My personal opinion about the packet loss in the ping test is that its higher than it should be, but, I base that on my test results from West Ottawa, which are typically well under 1%. The distribution of the high ping times (latency) would be interesting to see and it might be the more important point here. That's something I have to work on to make it easy to accomplish.
On the surface, yes the downstream signal levels are higher than normal, but, given the problems with the Rogers network these days, you might not have any problems caused by local issues. That's really problematic these days, are the problems local, or are they network issues? Really the only thing the tech can do is check the cables and connectors for continuity. That's a minor check and might not do much if anything to address any latency and packet loss that you're seeing 😞
@MD83 I haven't forgotten about you. I just don't know if I can offer any productive advice at this point. Your case looks very much like that of @JSS_BRAMPTON
https://communityforums.rogers.com/t5/Internet/Question-about-Signal-Levels/m-p/458649#M59936
Maybe the solution is to request a tech visit to check for noise issues? Don't know. The modems themselves are equipped to check and monitor for noise and as far as I know there is a noise record kept to each modem, if not minute by minute, maybe every five minutes. Don't know why Rogers can't use that record to initiate further action to resolve upstream noise issues.
-
94129 views
-
20 Likes
-
-
