Strange WAN DHCP Issue

jayman81

Hello,

I'm on starlink Internet and having drops is usually fairly normal. But the drops usually correspond to a loss of signal.

My em1 interface is acting strange since the upgrade where my pfsense is invoking rc.newwanip every 5 or so minutes. The same IP is normally assigned but at times a new IP will pop up and my Internet will drop.

Logs...

Feb 26 13:55:33 pfs check_reload_status[424]: rc.newwanip starting em1
Feb 26 13:55:34 pfs php-fpm[351]: /rc.newwanip: rc.newwanip: Info: starting on em1.
Feb 26 13:55:34 pfs php-fpm[351]: /rc.newwanip: rc.newwanip: on (IP address: 100.77.144.251) (interface: WAN[wan]) (real interface: em1).
Feb 26 13:55:34 pfs check_reload_status[424]: Reloading filter
Feb 26 13:58:03 pfs check_reload_status[424]: rc.newwanip starting em1
Feb 26 13:58:04 pfs php-fpm[351]: /rc.newwanip: rc.newwanip: Info: starting on em1.
Feb 26 13:58:04 pfs php-fpm[351]: /rc.newwanip: rc.newwanip: on (IP address: 100.77.144.251) (interface: WAN[wan]) (real interface: em1).
Feb 26 13:58:04 pfs check_reload_status[424]: Reloading filter
Feb 26 14:00:33 pfs check_reload_status[424]: rc.newwanip starting em1
Feb 26 14:00:34 pfs php-fpm[352]: /rc.newwanip: rc.newwanip: Info: starting on em1.
Feb 26 14:00:34 pfs php-fpm[352]: /rc.newwanip: rc.newwanip: on (IP address: 100.77.144.251) (interface: WAN[wan]) (real interface: em1).
Feb 26 14:00:34 pfs check_reload_status[424]: Reloading filter
Feb 26 14:03:04 pfs check_reload_status[424]: rc.newwanip starting em1
Feb 26 14:03:05 pfs php-fpm[99342]: /rc.newwanip: rc.newwanip: Info: starting on em1.
Feb 26 14:03:05 pfs php-fpm[99342]: /rc.newwanip: rc.newwanip: on (IP address: 100.77.144.251) (interface: WAN[wan]) (real interface: em1).
Feb 26 14:03:05 pfs check_reload_status[424]: Reloading filter
Feb 26 14:04:03 pfs check_reload_status[424]: Syncing firewall

I have gateway monitoring disabled. I've disabled some packages (pfblocker, ntopng). Wondering if someone can shed some light as to why this is happening?

Thanks!

ind1g0

I have Starlink as well and DHCP issues. If you plug Starlink into pfSense it will never get an address and sometimes I see the physical NIC bouncing. If you reboot pfSense it will get an address and keep it, until you unplug and plug it back in and then you will have to reboot pfSense once again to get an address. Can't figure out whats going on here. I built a new router on PFS 2.5 just for Starlink.

ghzgod

@jayman81 @ind1g0

The solution I've found to fix this is to do the following:

Interfaces > Your Starlink Int. > Tick Advanced Configuration under DHCP Client Configuration > Reject leases from 192.168.100.1 (which is the Dish aka Dishy) and then PFSENSE should stop having issues on reboot or new ip changes.

Please let me know if this works for you. Cheers.