Bug #11677
closed
MultiWAN issue after upgrade to 2.5.0 - gets external WANIP but link down
0%
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
Updated by Jim Pingle over 3 years ago
- Category changed from Routing to Interfaces
- Status changed from New to Rejected
- Priority changed from High to Normal
This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .
See Reporting Issues with pfSense Software for more information.