SG-2220 + SB8200 Modem



  • Hello All,

    I'm having an issue with these two devices, the SG-2220 running the latest code, basically since upgrading to a newer gigabit modem the SB8200 I've noticed in a few cases when there is a power blip the modem takes longer than the old one boot and offer a true public IP to the WAN port of my pfsense box.

    Previously I would just get the 192.168.100.1 IP, but I've blocked that IP in the interface settings. This resolved the issue of them booting together, however in some cases when there is a power outage, the WAN interface will just get stuck in unknown/pending until i manually intervene (replugging the cable, down/up the interface).

    Below are the DHCP logs, it appears pfsense tries to go back and use the original IP after a system reset, additionally according to this log it appears to have worked? Yet it does not. Looking for some guidance to potential better monitor and automatically remediate this WAN state:

    Mar 3 06:11:35 dhclient PREINIT
    Mar 3 06:11:35 dhclient 10277 DHCPREQUEST on igb0 to 255.255.255.255 port 67
    Mar 3 06:11:35 dhclient 10277 DHCPNACK from 192.168.100.1 rejected.
    Mar 3 06:11:35 dhclient 10277 DHCPREQUEST on igb0 to 255.255.255.255 port 67
    Mar 3 06:11:35 dhclient 10277 DHCPNACK from 192.168.100.1 rejected.
    Mar 3 06:11:38 dhclient 10277 DHCPREQUEST on igb0 to 255.255.255.255 port 67
    Mar 3 06:11:38 dhclient 10277 DHCPNACK from 192.168.100.1 rejected.
    Mar 3 06:11:41 dhclient 10277 DHCPREQUEST on igb0 to 255.255.255.255 port 67
    Mar 3 06:11:41 dhclient 10277 DHCPNACK from 192.168.100.1 rejected.
    Mar 3 06:11:46 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 2
    Mar 3 06:11:46 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:11:48 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 2
    Mar 3 06:11:48 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:11:50 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 2
    Mar 3 06:11:50 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:11:52 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 3
    Mar 3 06:11:52 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:11:55 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 8
    Mar 3 06:11:55 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:12:04 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 11
    Mar 3 06:12:04 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:12:15 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 17
    Mar 3 06:12:15 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:12:32 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 13
    Mar 3 06:12:32 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:12:45 dhclient 10277 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 2
    Mar 3 06:12:45 dhclient 10277 DHCPOFFER from 192.168.100.1 rejected.
    Mar 3 06:12:47 dhclient 10277 No DHCPOFFERS received.
    Mar 3 06:12:47 dhclient 10277 Trying recorded lease XX.XX.XX.XX
    Mar 3 06:12:47 dhclient TIMEOUT
    Mar 3 06:12:47 dhclient Starting add_new_address()
    Mar 3 06:12:47 dhclient ifconfig igb0 inet XX.XX.XX.XX netmask 255.255.254.0 broadcast 255.255.255.255
    Mar 3 06:12:47 dhclient New IP Address (igb0): XX.XX.XX.XX
    Mar 3 06:12:47 dhclient New Subnet Mask (igb0): 255.255.254.0
    Mar 3 06:12:47 dhclient New Broadcast Address (igb0): 255.255.255.255
    Mar 3 06:12:47 dhclient New Routers (igb0): XX.XX.XX.YY
    Mar 3 06:12:48 dhclient New Routers (igb0): XX.XX.XX.YY
    Mar 3 06:12:49 dhclient Deleting old routes
    Mar 3 06:12:49 dhclient 10277 bound: renewal in 61515 seconds.



  • As an update I've tested removing the 192 address from the reject list and I've also switched to the "FreeBSD" preset for DHCP options, so far this appears to have resolved my original issue of not switching the wan IP from a 192 to public IP on a cold boot of both, i'll have to wait and see if a power blip occurs again to test the true results.

    thanks


Log in to reply