We have a LAN connected through a VSAT satellite that was brought down by a storm a few days ago. We’re thinking it was a short and the lightning arrester didn’t work – a piece on the VSAT stopped running (the BUC), and the modem stopped working as well. We replaced the BUC and the modem, loading a new options file onto the modem (which is also a router, iDirect) from the NOC, the only options being different seem to be modem/transceiver related (not IPs).
We got internet from the modem working, but when we reconnected the router, an NIC wasn’t online. We had to replace the machine but used the same hard drive, i.e. smoothwall configs were all the same but NICs and MAC are different. Using the setup menu on command line, we assigned the new Ethernet ports to red (modem) and green (switches -> LAN).
What’s strange is that now we can get internet access through smoothwall, but only if we statically assign our IPs. The settings for DHCP remain the same on smoothwall as before the storm, but none of our machines are getting addresses when set to ‘obtain an ip address automatically’.
I tried using tcpdump to listen on port 67 and 68 for eth0 on the router, and it is getting requests but I’m not sure what they mean:
[time] IP 0.0.0.0.68 > 255.255.255.255.67 BOOTP/DHCP, Request from 00:16:6f…
Those are the only type of traffic.
All smoothwall updates installed. Tried switching which nics were red and green, and which ethernet cables were connected, (per Smoothwall NOT giving out DHCP) and that resulted in no WAN connection.
Am I right in assuming everything is cool between the NICs interfaces and smoothwall because internet is working? Could there be a DHCP setting I’m missing?
Some smoothwall settings:
Interfaces: green eth0 red eth1 static, smoothwall,
dhcp networkboot disabled interface -> green (only one in dropdown or CLI) no custom gateway current dynamic leases: 0 alive, 4 unreachable