Project

General

Profile

Actions
Copy link

Bug #3783

closed

wan interface loses IP after carrier reconnect

Added by Jonathon Reinhart over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
Gateways
Target version:
-
Start date:
07/29/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1.x
Affected Architecture:
amd64

Description

Summary: My WAN interface successfully gets an IP address via DHCP after reconnecting the Ethernet connection. However, after 1-2 minutes, it loses this IP address, and my gateway is marked as "down".

Background: For some reason, my WAN Ethernet connection seems to drop. This may be because it is an ASIX USB dongle on an ESXi 5.5 guest. (I recall reading about the link going down for no reason.)

Setup:
  • Version: 2.1.4-RELEASE amd64
  • System: ESXi 5.5 guest
  • LAN Interface: E1000 (virtual)
  • WAN Interface: ASIX AX88x72A (USB)
Steps to reproduce:
  1. Disconnect WAN Ethernet connection
  2. Re-connect WAN Ethernet connection
  3. WAN interface will get IP address via DHCP - Internet will be accessible
  4. After 1-2 minutes, WAN IP address is no longer there - Internet is inaccessible
  5. Click Release on status_interfaces.php
  6. Click Renew - Internet is accessible (until link goes down again?)

It appears that something causes the active dhclient process to close/exit, and for whatever reason it tries to restart but fails to. See the annotated log.

Files

pfsense_dhclient_log_redacted.txt (22.4 KB) pfsense_dhclient_log_redacted.txt dhcpd log showing dhclient restart behavior Jonathon Reinhart, 07/29/2014 06:55 PM
Actions
Copy link
 #1

Updated by Jonathon Reinhart over 9 years ago

Here is an annotated log showing the strange dhclient restart behavior.

Actions
Copy link
 #2

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Rejected

that's most likely a ue driver issue, maybe in combination with what you're doing with VMware. People see those have issues with link cycling or other odd behavior. Might work as is in 2.2, if it is purely a ue driver issue. Either way, the problem as described is not a general problem, it's not an issue in our code, either the NIC driver or VMware or how they're used in combination here.

If you'd like to pursue it further, try 2.2 to see how it behaves, and test outside of VMware. If you can narrow it down to a ue driver issue, report upstream to FreeBSD.

Actions
Copy link

Also available in: Atom PDF