Project

General

Profile

Actions
Copy link

Bug #11677

closed

MultiWAN issue after upgrade to 2.5.0 - gets external WANIP but link down

Added by Michael Knowles over 3 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
03/15/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.x
Affected Architecture:
All

Description

Hi there,
We upgraded our office pfSense instance from 2.4.5 to 2.5.0 last night, and lost WAN2 as a result. We get to see the correct (PPPoE-supplied) WAN IP address in the dashboard, but the gateway is marked as down with 100% packet loss. Routing is set correctly, and cannot PING from WAN2 interface to the outside world nor from outside in. Both WAN and WAN2 are from the same ISP (BT) yet WAN is set with a static IP at BT and the gateway is internet-legal yet WAN2 we are given an RFC1918 gateway address (not sure if that points to the problem but we've always been given an RFC1918 address from a dynamic IP address from BT).
I've attached a jpg showing the relevant area of the dashboard, and an excel spreadsheet of the gateway logs which i've had a go at redacting full IP addressing info - if you need full info or a backup of the system, let me know how to get it to you.
We've tried with the development strain (2.6.0) but the issue still exists.
Also tried changing or eliminating the gateway monitoring to no avail.

Files

Download all files
wan2down.JPG (100 KB) wan2down.JPG Michael Knowles, 03/15/2021 07:09 AM
gatewaylog.xlsx (13.3 KB) gatewaylog.xlsx Michael Knowles, 03/15/2021 07:09 AM
Actions
Copy link

Also available in: Atom PDF