Project

General

Profile

Actions
Copy link

Bug #2297

closed

Inbound NAT on secondary WAN Interface when Primary Interface has no carrier

Added by Mark Royan about 13 years ago. Updated over 12 years ago.

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

0%

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

Description

Inbound connectivity (ICMP, NAT, etc) from WAN becomes inaccessible on a secondary WAN connection when the primary WAN connection loses carrier. The issue does not appear to start to effect connectivity immediately on carrier loss, it follows a period of time (2-3 minutes) after carrier loss on the primary connection. Bringing link (layer 1 / 2) back up on primary interface restores service on secondary wan interface. Outbound connectivity from the secondary interface does appear to function during the carrier loss on the primary interface.

Actions
Copy link
 #1

Updated by Jim Pingle over 12 years ago

  • Status changed from New to Closed

Probably this is due to the lack of a default gateway. Enable gateway switching under System > Advanced on the Misc tab and try it again. If that doesn't work correctly, then look at one of the other similar tickets that cover the same topic such as #1705

Actions
Copy link

Also available in: Atom PDF