GigHub blocking one old computer after replacement

snowblower
Regular Contributor

I have Bell GigaHub modem/router and fibre internet connection. It was running fine since October 2022 when it was installed.  A few days ago it lost the fiber connection and Bell replaced it with a new Giga Hub to restore the connection. The new one works fine *except* one old Linux server now cannot access the internet. It cannot ping the GigaHub router itself, and it can't ping any external internet address via the router. It can access every other computer on my local network, and every other computer can access it.  It just won't get along with the GigaHub. The linux server runs Ubuntu 10.04. The server has worked flawlessly over the course of serveral router, modem, and ISP changes over the years. It ran fine from the get-go with the original GigaHib. It just won't work with the new GigaHub that Bell gave me.

There's nothing exotic about the GigaHub setup. It's acting as the DHCP server. The linux server in question has a static ip address that is outside the range offered by the GigaHup HDCP server. Other devices with static IP addresses (e.g. a voip device) work fine. It's just this server that is not working. 

From the debug I've done I can see that the server sends a network request (at least makes the system call) and the GigaHub simply never responds. I'm at a loss beyond that, and there is no logging of debug info available on the GigaHub. And the problem extends to more than just "ping". It happens for any any all network access attempts that involve the GigaHub. They all just hang, with no response from the GigaGub.

Has anyone seen anything like this?

0 1 1,625
1 helpful reply

Accepted Solutions

snowblower
Regular Contributor

Fixed my problem.  There was a network address conflict. Something on my network got the (static) address of my server when the new router was installed before I could log into it for the first time and changed the DHCP range. The first address in the router's default DHCP address range happened to be the static ip address of my formerly broken server.  I know better than this... tap my wrist. I think it happened when the technition started plugging stuff back in. I told him, don't worry I'll get it, but by then the address was grabbed and the peices of the mystery where in place.  The conflicting device happened to be my doorbell camera and it refused to give up the address until I totally reinitialized it. There wasn't even much clue that it was the culprit, because it was still sending pictures, but there was an odd warning on the alarm app, which set the light bulb off for me.

View reply in original post

1 REPLY 1

snowblower
Regular Contributor

Fixed my problem.  There was a network address conflict. Something on my network got the (static) address of my server when the new router was installed before I could log into it for the first time and changed the DHCP range. The first address in the router's default DHCP address range happened to be the static ip address of my formerly broken server.  I know better than this... tap my wrist. I think it happened when the technition started plugging stuff back in. I told him, don't worry I'll get it, but by then the address was grabbed and the peices of the mystery where in place.  The conflicting device happened to be my doorbell camera and it refused to give up the address until I totally reinitialized it. There wasn't even much clue that it was the culprit, because it was still sending pictures, but there was an odd warning on the alarm app, which set the light bulb off for me.