pfSense Support Subscription

Author Topic: Frontier ONT DHCP issues  (Read 2273 times)

0 Members and 1 Guest are viewing this topic.

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1758
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Frontier ONT DHCP issues
« on: July 15, 2016, 01:23:26 pm »

I have a counterpart that I have running snapshots on his XTM5.  (latest right now and box did not come back up.) We had 2.2.X running on this box no problem.

He is a Frontier Fios customer.  Whenever the box is re-booted it will not get an address from the ONT without going to the "Interfaces" screen and hitting "Renew".

I may be able to look at this personally tomorrow but curious if anyone has any ideas?   I have a VPN to it so can look at it.


 :)
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline NOYB

  • Hero Member
  • *****
  • Posts: 1703
  • Karma: +158/-273
    • View Profile
Re: Frontier ONT DHCP issues
« Reply #1 on: July 15, 2016, 06:30:22 pm »
 
The interface and WAN settings may be useful.
 
Is the Frontier provided router still connected and pulling an address?
 
Bare metal or VM?
 
Is WAN a VLAN?
 

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1758
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: Frontier ONT DHCP issues
« Reply #2 on: July 16, 2016, 08:52:38 am »

Sorry was running out the door when I posted..

Is the Frontier provided router still connected and pulling an address?   No
 
Bare metal or VM?   Bare Metal    (Watchguard XTM5)
 
Is WAN a VLAN?       No.


WAN is setup DHCP with no IP6.  I have the actual interface MAC in the "MAC Controls" just in case the box was doing something weird like rolling its mac address to something else but no change.     Other than that   default.


 
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1758
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: Frontier ONT DHCP issues
« Reply #3 on: July 16, 2016, 08:56:48 am »
This is not from start up.  Its just normal renewal and repeats like this every time there is a renewal request. Seems like the Frontier system has issues.


Jul 16 06:21:11     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:21:12     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:21:14     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:21:18     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:21:25     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:21:43     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:22:28     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:23:43     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:25:19     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:28:40     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:29:12     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:29:31     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:29:39     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:29:51     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:30:25     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:31:49     dhclient     37491     DHCPREQUEST on em0 to 50.35.14.1 port 67
Jul 16 06:33:35     dhclient     37491     DHCPREQUEST on em0 to 255.255.255.255 port 67
Jul 16 06:33:35     dhclient     37491     DHCPACK from 50.35.14.1
Jul 16 06:33:35     dhclient         RENEW
Jul 16 06:33:35     dhclient         Creating resolv.conf
Jul 16 06:33:35     dhclient     37491     bound to 50.35.xx1.xx -- renewal in 900 seconds.
« Last Edit: July 16, 2016, 09:01:33 am by chpalmer »
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1758
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: Frontier ONT DHCP issues
« Reply #4 on: July 16, 2016, 09:07:53 am »
From Dmesg=

arpresolve: can't allocate llinfo for 50.35.14.1 on em0 arpresolve: 
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 ovpnc1:
link state changed to DOWN ovpnc1:
link state changed to UP arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 ovpnc1:
link state changed to DOWN ovpnc1:
link state changed to UP arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 ovpnc1:
link state changed to DOWN ovpnc1:
link state changed to UP arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 arpresolve:
can't allocate llinfo for 50.35.14.1 on em0 ovpnc1:
link state changed to DOWN ovpnc1:
link state changed to UP
« Last Edit: July 16, 2016, 10:42:22 am by chpalmer »
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1758
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: Frontier ONT DHCP issues
« Reply #5 on: July 16, 2016, 03:26:11 pm »
Quote
Jul 16 13:11:22     php-fpm     63565     /rc.newwanip: rc.newwanip: Info: starting on em0.
Jul 16 13:11:22     php-fpm     63565     /rc.newwanip: rc.newwanip: on (IP address: ) (interface: WAN[wan]) (real interface: em0).
Jul 16 13:11:22     php-fpm     63565     /rc.newwanip: rc.newwanip: Failed to update wan IP, restarting...
Jul 16 13:11:22     check_reload_status         Configuring interface wan
Jul 16 13:11:23     kernel         arpresolve: can't allocate llinfo for 50.35.14.1 on em0
Jul 16 13:11:23     check_reload_status         updating dyndns wan
Jul 16 13:11:23     check_reload_status         Reloading filter
Jul 16 13:11:23     check_reload_status         rc.newwanip starting em0
Jul 16 13:11:24     xinetd     9584     Starting reconfiguration
Jul 16 13:11:24     xinetd     9584     Swapping defaults
Jul 16 13:11:24     xinetd     9584     readjusting service 6969-udp
Jul 16 13:11:24     xinetd     9584     Reconfigured: new=0 old=1 dropped=0 (services)
Jul 16 13:11:24     php-fpm     82968     /rc.newwanip: rc.newwanip: Info: starting on em0.
Jul 16 13:11:24     php-fpm     82968     /rc.newwanip: rc.newwanip: on (IP address: 50.35.xx.xx) (interface: WAN[wan]) (real interface: em0).
Jul 16 13:11:24     xinetd     9584     Starting reconfiguration
Jul 16 13:11:24     xinetd     9584     Swapping defaults
Jul 16 13:11:24     xinetd     9584     readjusting service 6969-udp
Jul 16 13:11:24     xinetd     9584     Reconfigured: new=0 old=1 dropped=0 (services)
Jul 16 13:11:24     php-fpm     82968     /rc.newwanip: ROUTING: setting default route to 50.35.14.1
Jul 16 13:11:24     php-fpm     82968     /rc.newwanip: Removing static route for monitor 50.46.184.1 and adding a new route through 50.35.14.1
Jul 16 13:11:28     php-fpm     82968     /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Jul 16 13:11:28     check_reload_status         Reloading filter
Jul 16 13:11:28     php-fpm     82968     /rc.newwanip: Creating rrd update script
Jul 16 13:11:28     kernel         ovpnc1: link state changed to UP
Jul 16 13:11:28     check_reload_status         rc.newwanip starting ovpnc1
Jul 16 13:11:29     xinetd     9584     Starting reconfiguration
Jul 16 13:11:29     xinetd     9584     Swapping defaults
Jul 16 13:11:29     xinetd     9584     readjusting service 6969-udp
Jul 16 13:11:29     xinetd     9584     Reconfigured: new=0 old=1 dropped=0 (services)

Code: [Select]
em0: link state changed to UP

arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
ovpnc1: link state changed to DOWN
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
ovpnc1: link state changed to UP
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
ovpnc1: link state changed to DOWN
ovpnc1: link state changed to UP
em0: Watchdog timeout Queue[0]-- resetting
Interface is RUNNING and ACTIVE
em0: TX Queue 0 ------
em0: hw tdh = 696, hw tdt = 656
em0: Tx Queue Status = -2147483648
em0: TX descriptors avail = 40
em0: Tx Descriptors avail failure = 548
em0: RX Queue 0 ------
em0: hw rdh = 219, hw rdt = 218
em0: RX discarded packets = 0
em0: RX Next to Check = 219
em0: RX Next to Refresh = 218
em0: link state changed to DOWN
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
ovpnc1: link state changed to DOWN
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
em0: link state changed to UP
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
arpresolve: can't allocate llinfo for 50.35.14.1 on em0
ovpnc1: link state changed to UP
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline Paint

  • Full Member
  • ***
  • Posts: 208
  • Karma: +32/-2
    • View Profile
Re: Frontier ONT DHCP issues
« Reply #6 on: July 16, 2016, 11:39:42 pm »
Can you please post your DHCP settings?

Even if you are not cloning your MAC address, can you setup your DHCP settings similar to this and let us know if it resolves the problem? Can you capture the DHCP packet request from Frontier's ONT?

https://forum.pfsense.org/index.php?topic=114389.msg635823#msg635823
pfSense i7-4510U + 2x Intel 82574 + 2x Intel i350 Mini-ITX Build
940/880 mbit Fiber Internet from FiOS
Dell PowerConnect 2716 Gigabit Switch
Netgear R8000 AP (DD-WRT)
Asus RT-66U AP (DD-WRT)


Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1758
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: Frontier ONT DHCP issues
« Reply #7 on: July 17, 2016, 02:16:22 am »
Thanks for that link Paint!   I did look around but didn't run into that earlier.

I was able to put hands on today and we changed the WAN interface on this particular box from the gigabit  (em) port to the 10/100 (fxp) port which seems to have fixed the issue. Now that Im back home Im kicking myself for not trying out one of the other gigabit ports to see if they all did it.  Ill get help from the owner and try that as well if I can pin him down and get him to move the wire.

I want to continue to diagnose and will do a packet capture later this weekend or Monday after I get some sleep.

« Last Edit: July 17, 2016, 02:28:12 am by chpalmer »
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1758
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: Frontier ONT DHCP issues
« Reply #8 on: July 17, 2016, 02:23:14 am »

In actuality this thread would probably be better in the DHCP corner of the forum.  I was able to confirm today from the owner that it did happen from 2.3 onward. 2.2.6 was only on this box for 45 minutes. So no real testing happened.
 
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline Paint

  • Full Member
  • ***
  • Posts: 208
  • Karma: +32/-2
    • View Profile
Re: Frontier ONT DHCP issues
« Reply #9 on: July 17, 2016, 11:18:23 am »
Thanks for that link Paint!   I did look around but didn't run into that earlier.

I was able to put hands on today and we changed the WAN interface on this particular box from the gigabit  (em) port to the 10/100 (fxp) port which seems to have fixed the issue. Now that Im back home Im kicking myself for not trying out one of the other gigabit ports to see if they all did it.  Ill get help from the owner and try that as well if I can pin him down and get him to move the wire.

I want to continue to diagnose and will do a packet capture later this weekend or Monday after I get some sleep.

My pleasure.  Everything working?
pfSense i7-4510U + 2x Intel 82574 + 2x Intel i350 Mini-ITX Build
940/880 mbit Fiber Internet from FiOS
Dell PowerConnect 2716 Gigabit Switch
Netgear R8000 AP (DD-WRT)
Asus RT-66U AP (DD-WRT)