Bell Home Hub 3000- IP Address range

[MRSNM]

Hello I have a Bell Home Hub 3000 modem, the DHCP IP Range available displays 192.168.2. N till 192.168.2.N+254 whereas my device is connected 192.168.5. y etc, can someone explain why there is a variance. I am very much concerned about this.

[WelshTerrier]

Well…. Not sure what is what now….. It looks to me like there is no problem. Too many cooks in the kitchen, so to speak.

I hope this has been resolved. If not, sorry, but I need to move on. Have you discussed this with Bell Tech support? Take care!

[ZaneP]

There is one less cook in the kitchen!

There is a fundamental problem, which hasn't been resolved. There is a brute-force solution: factory-reset the modem.

[WelshTerrier]

That will fix it..... probably the easiest & fastest. Take care!

[Richard3]

the IP range 192.168.5.N is the guest network on the homehub 3000 this is so guest do not access your home network

[JDS_Next]

Hi @Richard3


PROBLEM REPORT - Bell Home Hub 3000

I think you are close to the answer.
I am reasonably knowledgeable... I come from Bell-Northern Research, and separately, have developed a number of global telecommunications software products that Bell funded and subsequently distributed. I mention this only, because there are 'Contributors' here, that have limited knowledge, and have historically not served Bell Canada well, in their Support efforts. I did have to speak with the Office of the President, on one occassion.
--

Sorry, for the intro...
--

I too, have the IP Address of '192.168.5.m' problem. 

I am interested getting resolution from proper Bell Support (Montreal) as I have spent several hours determing that the IP Address of 192.168.5.m is not a virus or an attack vector. I will send this message to the Office of President, within a week, if there is no proper response to this Problem Report. Why? Because it is a legitimate concern, and this Support Page appears to be managed by volunteers, sadly.

What I see...

On my Bell Home 3000 WiFi Router the DHCP range for what appears to be configured for 192.168.2.N... for all WiFi and Ethernet connection methods (Primary and Guest). This is configured globally in the Advanced Section of the Router Administrative Tool. This is a BUG.

I believe, I understand what is going on.

Case 1: If the NAME for both Primary and Guest Networks in the WiFi Router is the SAME, then the assigned DHCP Address is ARIBTRARILY assigned the Connecting Machine. This means that the IP Address could be either 192.168.2.n or 192.168.5.m. This could be a bug. I did not test extensively.

Case 2: If the Connecting Machine uses the GUEST connection method, then the Connecting Machine is assigned to what looks like a VLAN created in the Bell Home Hub 3000 (WiFi Router)... 192.168.5.m. The Bell documentation makes no reference to a VLAN capability. I consider this to be a BUG.

Case 3: If the Connecting Machine is a Virtual Machine, then the IP Address in the WiFi Router appears POD type and appears in the Primary list (not the Guest List). The assigned IP Address is of the 192.168.5.m type.

There are other cases to consider, but it would take to MUCH time to solve Bell's problems.
--

I notice that Radio-1 and Radio-2 for 5.0 GHz connections seem to be random.
--

-- Bell Support Employees (Hopefully Montreal... as these guys are excellent) -- ----------------------------------------

I think it would be useful to provide documentation in paper and HTML formats that, speaks to, the fact, that this WiFi Router has the capability to assign/ isolate traffic using a VLAN, and that the VLAN uses the 192.168.5.n DHCP segment.
--

If other people, who encounter this problem, find errors in my description, please correct.
🙂

END

[JDS_Next]

Printing...

If you have been assigned an IP Address in the 192.168.5.M range then, you will NOT have access to machines on the 192.168.2.N range.