Project

General

Profile

Actions

Bug #2393

closed

PF not "forgetting" older IP addresses after a change on the WAN interface

Added by Oliver Loch about 13 years ago. Updated about 13 years ago.

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

0%

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

Description

Hi,

when starting pfsense and the cable modem from my provider together at the same time, the cable modem comes up, assigns itself the ip address 192.168.100.1 and hands out the ip address 192.168.100.10 to pfsense until it's done it's handshake and pfsense can request a public ip address via dhcp.

After pfsense got the public ip address, there are still open connections that are nated via the private address. I tried to reset all states, flushed the rules, reloaded the rules and so on, but the box still uses "192.168.100.10" for some connections. It's not listed anywhere any longer but it's used by the box.

Only thing working is to reboot the machine and let it get a public ip from the beginning. I wonder if I miss something.

KR,

Oliver

Actions #1

Updated by Chris Buechler about 13 years ago

  • Status changed from New to Closed

duplicate

Actions

Also available in: Atom PDF