Messages

1

General Discussion / Re: PfSense tunnel to OpnSense ping work on one side

« on: February 22, 2019, 06:02:17 pm »

SOLVED
everyting was ok,  hosts file problem confused me for my test


JF

2

General Discussion / Re: PfSense tunnel to OpnSense ping work on one side

« on: February 22, 2019, 05:49:48 pm »

Nope
I have intermittent results

Is there some rules to add on the OpnSense side to  to allow traffic coming  from a Tunnel with PfSense ?

IP/Comptuer  Behind OpnSense Can ping comptuer behind PFsense
But the opposite.

And on PfSense I didn't have anything to do special  to do..

3

General Discussion / Re: PfSense tunnel to OpnSense ping work on one side

« on: February 22, 2019, 04:12:43 pm »

Probleme solved
Added a rule on IPSEC to allow traffic
Though it would be implicit
My bad

4

General Discussion / PfSense tunnel to OpnSense ping work on one side

« on: February 22, 2019, 03:46:00 pm »

I create at tunne between a Pfsense and an OpnSense firewall


Network A <----> PfSense <----> OpnSense <----> Network B

Without adding any rules once the Tunnel was IP,
- Network B stations (behind OpenSense) can ping Network A stations

- But Network A stations cannot ping network B stations

Does OpnSense need extra rules we would not need to do on PfSense ?

JF

5

General Discussion / Re: Simple NAT question NEW User to OpnSense

« on: February 22, 2019, 02:21:51 pm »

tKS !!!! iT IS WORKING
BInat was one of my error (NAT didn 't work)
JF

6

General Discussion / Re: Simple NAT question NEW User to OpnSense

« on: February 22, 2019, 12:00:42 am »

I will try again. but there is so much more option that what you describe
https://pasteboard.co/I2eWrbT.png

I know I have to do what you describe ( tks I do appreciate ) but it didn't work last time..


I will check again my Freebsd network config to be sure the different IPs are in /etc/rc.conf  and make some ping test

Good night ! Wherever your tare

7

General Discussion / Re: Simple NAT question NEW User to OpnSense

« on: February 21, 2019, 11:08:25 pm »

HUM

All those servers do have different Public IP and customers will connect to this different IP and FQDN

Server 1   public ip xyz   name.domain.com   PTR to this IP
Server 2   public ip xyz   name2.domain.com   PTR to this IP


tks !

8

General Discussion / Re: Simple NAT question NEW User to OpnSense

« on: February 21, 2019, 10:09:39 pm »

The interface is more complex that what you say

https://pasteboard.co/I2eWrbT.png

Tks !
JF

9

General Discussion / Re: Simple NAT question NEW User to OpnSense

« on: February 21, 2019, 12:46:12 pm »

Tks Bart.  Will try !

10

General Discussion / Simple NAT question NEW User to OpnSense

« on: February 21, 2019, 02:02:47 am »

Hello everyone,

I am new to OpnSense ( was using PfSense)

I am trying to do something that is usualy simple to do.

3 servers ----> OpnSense  (3 public IP)  ---->   Internet

I am trying to have those 3 servers on the internet with their own IP.
But After playing during a while with one server, it's always going out using the MAIN OpnSense IP.

I used the NAT section of the interface, tried NAT LAN, Nat WAN and it both case it didn't worked

When trying to use Nat 1 on on1, I specify the public IP I want to use, tell the NAT rule which server internally it need to be nated to

Question :
1- when creating the Nat rule, to O chose Lan or wan ? in both case I can specify what is the internal and external ip.
2- Virtual IP, do I have to use that ?

My test was simple, I curl ipinfo.io  and it gaved back the " main firewall" ip and not the one I created in the NAT rule

JF
Sorry for that newbie question LOL I played with so many brand of firewall and my ego too a hit :-)