Project

General

Profile

Actions
Copy link

Bug #2647

closed

rc.newwanip discovers wrong WAN IP when using DHCP

Added by Christoph Filnkößl over 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
09/30/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:
All

Description

It seems that pfSense's rc.newwanip has got problems discovering the right WAN IP after running some time.

We are running our pfSense as described below:
  • 213.0.0.9 as WAN IP - DHCP from provider (always the same address)
  • 212.0.0.16/28 as "IP Alias" Virtual IPs on the WAN interface

When booted, pfSense discovers 213.0.0.9 as it's own IP address - everything running fine.
Some days later dhclient runs successfully, gets the 213.0.0.9 IP but rc.newwanip discovers 212.0.0.19 as its WAN IP.
After that, pfSense only responds under the 212.0.0.19 IP.

read from bottom to top:

Jun 27 03:59:03    apinger: Starting Alarm Pinger, apinger(27639)
Jun 27 03:59:03    check_reload_status: Reloading filter
Jun 27 03:59:02    apinger: Exiting on signal 15.
Jun 27 03:59:01    php: : ROUTING: setting default route to 213.0.0.1
Jun 27 03:59:01    php: : rc.newwanip: on (IP address: 212.0.0.19) (interface: wan) (real interface: vr2).
Jun 27 03:59:01    php: : rc.newwanip: Informational is starting vr2.
Jun 27 03:58:55    dhclient[2348]: bound to 213.0.0.9 -- renewal in 189670 seconds.
Jun 27 03:58:55    check_reload_status: rc.newwanip starting vr2
Jun 27 03:58:55    dhclient: Creating resolv.conf
Jun 27 03:58:55    dhclient: /sbin/route add default 213.0.0.1
Jun 27 03:58:55    dhclient: Adding new routes to interface: vr2
Jun 27 03:58:55    dhclient: New Routers (vr2): 213.0.0.1
Jun 27 03:58:55    dhclient: New Broadcast Address (vr2): 255.255.255.255
Jun 27 03:58:55    dhclient: New Subnet Mask (vr2): 255.255.255.0
Jun 27 03:58:55    dhclient: New IP Address (vr2): 213.0.0.9
Jun 27 03:58:55    dhclient: ifconfig vr2 inet 213.0.0.9 netmask 255.255.255.0 broadcast 255.255.255.255
Jun 27 03:58:55    dhclient: Starting add_new_address()
Jun 27 03:58:55    dhclient: BOUND
Jun 27 03:58:55    dhclient[2348]: DHCPACK from 10.34.114.129
Jun 27 03:58:55    dhclient[2348]: DHCPREQUEST on vr2 to 255.255.255.255 port 67
Jun 27 03:58:55    dhclient: ARPCHECK
Jun 27 03:58:53    dhclient: ARPSEND
Jun 27 03:58:53    dhclient[2348]: DHCPOFFER from 10.34.114.129
Jun 27 03:58:53    dhclient[2348]: DHCPDISCOVER on vr2 to 255.255.255.255 port 67 interval 1
Jun 27 03:58:52    dhclient[2348]: DHCPDISCOVER on vr2 to 255.255.255.255 port 67 interval 1
Jun 27 03:58:52    dhclient[2348]: DHCPNAK from 10.34.114.129
Jun 27 03:58:52    dhclient[2348]: DHCPREQUEST on vr2 to 255.255.255.255 port 67
Jun 27 02:55:10    dhclient[2348]: DHCPREQUEST on vr2 to 10.34.114.129 port 67

Applying WAN interface setting again (no changes) helps and pfSense discovers the right IP.

This happens every 5-15 days and pfSense occupies a random IP from the 212.0.0.16/28 subnet.

Feel free to ask for further details.

Actions
Copy link

Also available in: Atom PDF