cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3087
Views
0
Helpful
33
Replies

Cisco Router NAT transparency

AvidPontoon1
Level 1
Level 1

I have a firewall box that sits between the 'WAN' port on a cisco 2811 and the main ISP line in to my building. The topology looks like:

 

 ISP CONNECTION IN

UTM 

CISCO ROUTER

 

My problem is logging on the UTM. It runs a dns filtering service that filters the network traffic for the site. Between the UTM and Router there is a class C subnet: 20.20.20.0/24. The utm has 20.20.20.1 and the router has 20.20.20.2. The cisco router has nat configured on it to allow 0.0.0.0. My problem is that when a client visits a blocked page the UTM logs this with the ip of the client. The problem I am having is that the client ip address is always 20.20.20.2 (The ip of the WAN on the router) and not the ip of the actual client.

 

How can i get the firewall to see the actual client ip? Ive ruled it down to NAT on the router but have no idea on how to configure it. Please could someone explain what I need to do?

 

33 Replies 33


@Georg Pauwen wrote:

Hello,

 

now check the NAT rules generated on the pfsense. Since you have added a static route for 10.0.0.0/8, that network should be included in an automatically generated rule:

 

https://www.netgate.com/docs/pfsense/nat/automatic-nat-rules-generation.html


See attached image...

Hello,

 

check if Manual NAT has been enabled.

 

https://www.netgate.com/docs/pfsense/nat/advanced-outbound-nat.html

 

The logic is as follows:

 

Your entire network can access the pfsense, and the pfsense can access the entire network. The thing left to do is let the pfsense know that it has to translate (NAT) both 10.0.0.0/8 and 20.20.20.0/24.

Still nothing, failing to ping 20.20.20.1 now from all clients

Post your current running configuration...

Review Cisco Networking products for a $25 gift card