Messages

Anyone???

I feel rather stupid, but i cant get a simple NAT forward to work. Not even in my virtual sandbox environment.

My sandbox looks like this:

WAN: 1.2.3.0/24
  Opnsense 1.2.3.20
  windows PC_A 1.2.3.10

LAN: 192.168.1.0/24
  Opnsense 192.168.1.1
  windows PC_B 192.168.1.100
  Test_Server_A 192.168.1.201 (just a plain http for test/verification purpose)

PC_B can with no problem access the test server on http://192.168.1.201/test.php, it can also the real internet via the virtual host system, so the routing and network is working just fine.

PC_A can access the real internet trough the virtual host system but i can no access on http://1.2.3.20/test.php

If i replace the Opnsense with a e.g. IpFire - then my NATing works as expected, so this profs that my virtual networks ect. is set up correct.

The Opnsense is freshly installed, and updated today (11 may). Attached is a bitmap of my Rules and NAT.

So what i'm i missing?

Thanks
Om

Greetings all,

I'm a newbie of the Opnsense but is already quite impressed with the product. So much i'm considering to make it my primary firewall.
I'm running it, in test, as a virtual appliance, and it performing great. But here is the catch, if my server goes down i loose connectivity, and particularly if i'm a way it would be a disaster as i could not "dial in" to my network.

Currently I'm using a Zyxel USG firewall, so I'm wondering if there is any way i could use that as a failover device.
There is article https://wiki.opnsense.org/manual/hacarp.html?highlight=failover (see configuring) that explains how to do it with carp. but from that i can see that is not implemented in any Zyxel USG.
So are there any bright minds out there with an idea?

I'm considering if it could be done by having two default gateways, and adjusting the metric. But in my experience two default gateways always ends up in a mess.

Thanks
OM