Project

General

Profile

Actions
Copy link

Bug #4303

closed

When using a public carp-ip on a wan interface that has a private ip apinger 'srcip' is set to the local ip.

Added by Pi Ba almost 11 years ago. Updated almost 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Gateway Monitoring
Target version:
-
Start date:
01/26/2015
Due date:
% Done:

0%

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

Description

When using a public carp-ip on a wan interface that has a private ip apinger 'srcip' is set to the local ip.
Even when outbound nat is set to perform natting on this private to the carp-ip that does not seem to affect the source ip send out.(As seen by tcpdump on that interface..)

I think the (carp-)ip that is configured in the same subnet as the gateway should be used as the source.

Actions
Copy link
 #1

Updated by Chris Buechler almost 11 years ago

  • Status changed from New to Rejected
  • Target version deleted (2.2.1)
  • Affected Version deleted (2.2)

that's how things work by design, the interface IP of the interface in question is the appropriate source. You can NAT it if you want it to work otherwise.

Actions
Copy link
 #2

Updated by Pi Ba almost 11 years ago

Ok for some reason there was a nat state that was already passing traffic. Deleting that state made the apinger pings work.

Actions
Copy link

Also available in: Atom PDF