Multi WAN, TO VM NAS with seperate Firewall

jochenmehlich

@viragomann said in Multi WAN, TO VM NAS with seperate Firewall:

The destination should be any if there are no special reasons for to set specific one.

@viragomann said in Multi WAN, TO VM NAS with seperate Firewall:

The rest of the 1:1 NAT rule is fine. One external IP to one internal.

Okay :D

@viragomann said in Multi WAN, TO VM NAS with seperate Firewall:

Ok, if the server are both on LAN within the same subnet there is no problem.

They should be.

jochenmehlich

its not working. the vms can go out.
only project is reachable.

here is the virtual-ip configuration

and the interface

Did i something wrong? Or should I ask my hoster, if any feature is missing?

viragomann

Are you sure, the safeserver is responding to the access from the internet?

To investigate use the packet capture tool from the Diagnostic menu on pfSense.
Take a capture on LAN interface while trying to access the Safeserver from outside.
If you see nothing take a capture on OPT1 to check if the packets arrives pfSense.

jochenmehlich

In OPT1 its showing the ping request

00:07:12.007358 IP 5.100.XXX.XXX > 144.76.93.234: ICMP echo request, id 6, seq 4, length

but there is nothing in lan

jochenmehlich

so i thing, something with the redirection is broke. (maybe the nat 1:1)?

viragomann

You have not allowed ping on OPT1. Your rules only allow http and https. So you cannot see a ping on LAN, cause pfSense blocks it.
So either test with http or allow ping.

jochenmehlich

now it should be allowed

but there is no difference. No incoming ping in LAN and no incoming https.

viragomann

Strange. Yes, it should work.

What if you add a usual port forwarding rule to OPT1 instead of the 1:1 for that server?

jochenmehlich

nothing will pass.

no https response from the projectserver or the safeserver.

jochenmehlich

is there any other method to make a firewall.
it must not be efficient, it must only work.

every vm must have its own rules and use its own public ip4 addresses.

viragomann

@jochenmehlich said in Multi WAN, TO VM NAS with seperate Firewall:

nothing will pass.

no https response from the projectserver or the safeserver.

No idea. That is straight forward.
I'd drop that installation and start from scratch.

jochenmehlich

i think thats the best method.
i will try it later - i have to sleep.

could you explain me, what i have to do?

viragomann

Just make a new installation of pfSense and configure it as you did before.
Sometimes anything go wrong and you cannot find any reason.

jochenmehlich

same issue like the installation from yesterday. Projectserver is reachable, Safeserver not ...

viragomann

Did you exchange external and internal IPs now deliberately?

Suspect saying to have no access to Saveserver as Saveserver was before 172.16.0.3 and now it's 172.16.0.2 (forwarded from 144.76.93.234).

jochenmehlich

@viragomann said in Multi WAN, TO VM NAS with seperate Firewall:

Did you exchange external and internal IPs now deliberately?
Suspect saying to have no access to Saveserver as Saveserver was before 172.16.0.3 and now it's 172.16.0.2 (forwarded from 144.76.93.234)

yes it was deliberately, but it isnt working and i dont now why. im wondering, because the projectserver is always reachable.