1: NAT done but SSH not accessible
-
This post is deleted! -
@nogbadthebad I thought NAT simply forwards the traffic from a static IP to an internal ip. Because I want multiple services with mutiple ports to be accessible. that's why I chose NAT. Should I specify the ports even in NAT? Opening all the ports i snot right. Let me put it simple. Imagine I have configured a usable static IP as a VIP. I want that VIP to provide me access to an internal server for multiple services. How do you do it. Tell me the process I will follow exactly. I tried mutiple videos and documents but no luck. Yes, the 2nd one is the rule for NAT.
-
@johnpoz Thank you John.. I do not get the VIP logs in the firewall logs. I don't know why. If I delete the VIP the FQDN doesn't ping. If the VIP is up it pings. I tried installing Sniff package but it doesn't show in the services. I will go through the document more abd will update you.
-
You don't need a sniff package - its right under diag, package capture..
MY gawd this is getting frustrating.. It takes all of 30 seconds to take a sniff and test this..
You don't need to setup any firewall rules or anything. Setup your VIP... Send traffic to it on 22, while your doing the packet capture... Do you see this traffic?
Once you see this... Then setup the 1:1 nat.. That is all of 30 seconds more..
If it does not work, then sniff on your lan side interface with packet capture. Send traffic to vip - do you see the packets going to the private IP?If you do, but no answer then problem is on your server your send it too. If you don't see it sending then you did your 1:1 nat wrong..
The firewall rule you need will be to the private IP address in your 1:1 NAT.. Do you really need pictures for this??
-
Here I don't really have an IP I can use.. but on my /30 on wan at work I created a /32 vip using the broadcast address..
I then pinged it from home connection... While sniffing... See the traffic hitting it from my home 64.53 address..
It doesn't answer ping.. It then add firewall rule to allow ping - and bam it pings..
-
Here so I created 1:1 nat, then firewall rule to allow ssh from my home IP to the dest private IP..
I then created ssh connection to this while sniffing on lan side interface... You can see pfsense send on the ssh traffic. But it doesn't get an answer because IP is actually inside IP of another pfsense in NY from where I am at in Chicago.. And its default route to get to public would go out its wan vs coming back this way.
This is why you have to sniff and validate if pfsense is sending the data or not - the problem could be on your host box.
-
You are probably right. I tried a sniff on WAN VIP through WAN interface. But there is no request for the VIP. I am sorry for the delay as I was not working on my weekend. I will try configuring the rules and try again
-
If you would of followed the troubleshoot guide from 4 days ago I linked too... Just saying..
-
I am literally trying. I am doing this NAT for the first time. Thank you very much for your help. I have not checked the result. But still let me complete this and will post the result.
-
First thing I would do is setup your vip.. And then validate your seeing traffic to the vip before doing anything with any rules or 1:1 nat.. Since its not possible for pfsense to do anything with said traffic until it actually gets to pfsense wan.
Maybe you have something between where your trying and pfsense wan that blocks 22 (ssh).
Once you have traffic getting to pfsense on the port you want, then you can forward it to what you need be it with normal port forward or 1:1
