So I changed my ISP fiber cable routing to my cabinet… as in what pipe it goes through and where it enters my network cabinet. Just a bit of cabling, same connections , same ports and same everything. Then after restarting the ISP modem a little later I have no Internet… Local lan works, but none of the computers connected to it has Internet. I review all connections, check IPFire, it has ISP IP, all the connections are ok. As an additional measure I connect the ISP cable directly to my Switch, bypassing IPFire, and that works, all computers get Internet again, however without firewall. As I am connected when I type this. Dangerous.
IPFire gets an IP from the ISP.
Nothing, zilch, is changed in the topology or network cabling.
But somehow IPFire does not forward the Internet connection to my computers? I do not even begin to know how I shall diagnose this. I have SSH access to Ipfire and can probably access logs and stuff (after changing back my network to default - its just a couple of cables) and all the weird cli commands and nano and all that, but I do not even begin to know where to look.
Tips? Running core 186 I think it was, not the very latest, one prior. No changes to IPFire since last update.
First thought is when you changed your cable routing, something unintentional changed that is causing this. Review your changes and reverse them to see if the problem is solved.
Another thing to try:
power off both modem and IPFire.
power on modem til it is at a ready state
power on IPFire, wait til fully booted and UI is accessible and try again.
Even powered off everything in the network cabinet for a few minutes.
Please observe I only changed how the cable is wired, it is easy to be confused by the word “routing”. What I di was move the cable location and how it is pulled through the cabinet, basically like if you move the power cable to your vacuum cleaner from behind the sofa while cleaning.
In regards to connectivity or patching or connections, nothing has changed…
The one thing I needed to do, and knew I had to do, was reset the connection to the ISP in the fiberbox by powering it off and on, since I interrupted it. There is no way this could affect anything else. I have conn to the ISP, just not working via IPFire.
yes, ran setup, it was ok… also verified afterwards when reconnecting to IPFire that all is correct.
ISP is DHCP.
Will check that later, taking a break, been messing with this for hours… the overall most critical thing was to get something towards internet running so I can work, so I will be a bit careful allocating time for testing.
For kicks, I just rebooted my IPFire, and when the UI came up, it was not grabbing the ISP IP. I gave it several minutes. Similar situation to you. LAN worked, but no WAN. So I rebooted the ISP modem and when it came back up, still no ISP IP in IPFire. So rebooted IPFire a second time, and this time it immediately grabbed the ISP IP and all was well. I assumed it was because the ISP Dynamic IP changed, but when I checked, it grabbed the same IP I had before.
So typing this on my laptop while hotspotting from my phone and messing with IPFire on the other comp
Right of the bat I see in IPMI that Red0 DHCP has failed to start.,
doing a clean reboot.
1st time…
default boot
Warning about grubbtrsfd something
Warning about “connection tracking daemon” not running
Warning … It failed to stop dhcp on Red0
Rebooting sequence > Starting boot
the usual old “harddisk” error (that fawlty plugin if you recall some months ago)
cleaning filesystem
green dhcp… ok
blue dhcp…ok
red… … … … … … dhcp ok, with list of dhcp assignments from ISP that looks ok.
So everything seems to have booted ok.
Still conn without Internet on the computer, resetting that local NIC… and after that ipconfig /renew (which disconnected IPMI, but only temporarily…) reconnecting to IPMI session.
Still no Internet on the desktop.
Rebooting, second time
Warning about grubbtrsfd something
Warning about “connection tracking daemon” not running
Warning … It failed to stop dhcp on Red0
Reboot sequence
the usual old “harddisk” error (that fawlty plugin if you recall some months ago)
Cleaning filesystem
green dhcp… ok
blue dhcp…ok
red… dhcp ok, with list of dhcp assigments that looks ok.
Still no Internet on desktop
So the only thing that seems troubling on my part is that it fails to do a clean shutdown of red dhcpd when rebooting?
The other Warnings have been there before I think…
And IPFire WUI tells me it has an ISP connection but it is not reaching its client comps…
One of the reasons I’m asking this is to see if DNS is involved. If you can ping an IP on RED, but internet is not working, then perhaps DNS is involved. If you can ping your gateway, then try nslookup with the gateway IP to see if it returns a name.
I was able to do both on that, but still not working. I fear the error is somehow deeper in the system, or, in spite of not showing any other symptoms, maybe something with the server it self, it is, after all one of those Atom server whose clock chip was flawed, or something like that. Then again I do not how “how” it would break…
In the meanwhile I have setup my spare router and will troubleshoot the Ipfire machine later. I just don’t have time now to solve it. I may have to begin from scratch, fortunately I have most of its settings documented, and setting up the old router was a breeze since I could lean on much of that documentation for relevant parts.
Actually not sure if I got around to do that if you check my post time you may consider I was not up for diagnosing but rather getting something up I know works no matter what…
But I have a backup so will get on it a bit later this week… the vital and most prioritized stuff was to get my VPN to work going or this would have started ticking serious money from my wallet instead of just some free time…
