Topics

1

General Discussion / NANO PFSense vs NANO OPNsense

« on: April 03, 2016, 02:38:58 pm »

After my survey i saw that NANO PFSense had /cfg partition.

Why we don't have such partition on NANO OPNsense ?

and What we should do to have such structure to reach Fault Tolerance?

Regards,
Hosein

2

16.1 Legacy Series / IDS on Bridge Mode do not detect private IP attack

« on: March 05, 2016, 11:06:17 am »

hi

I am using OPNsense in bridge mode.
I want to run IDS/IPS service to protect my trusted network, from private and public ip address attacks.
but as i tested, i need to edit Suricata config file (suricata.yaml) and edit HOME_NET to reach my goal.

after some research i found out that HOME_NET config is an important suricata variable.

So
Why are you not adding HOME_NET config to Web Interface of Intrusion Detection on OPNsense ?


Thanks
Hosein

3

15.7 Legacy Series / WAN Gateway Become offline after restarting 4G internet Modem

« on: January 13, 2016, 04:13:12 pm »

hi

I have OPNsense on device with two ethernet interface
WAN: 192.168.1.1
LAN: 192.168.2.1

and WAN Gateway (4G Modem) IP address is : 192.168.1.2

Each time, after i restart (turn the power off and on) the 4G Modem, the Gateway Status become : Offline

Code: [Select]

Offline
Last check:
Wed, 13 Jan 2016 15:01:32 +0100
Gateway log file:

Code: [Select]

Jan 13 15:01:32 apinger: ALARM: WANGW(192.168.1.2) *** down ***
Of course in this state, internet is not connected for LAN network.
after that i repeatedly check the Gateway status and Gateway Log.
Nothing happen till the below log is appeared:

Code: [Select]

Jan 13 15:11:07 apinger: alarm canceled: WANGW(192.168.1.2) *** down ***
as you can see, it takes OPNsense about 10 min to reconnect the internet for LAN network.

and after repeating this situation, every time i get a different period of time:

Code: [Select]

Jan 13 15:01:03 apinger: alarm canceled: WANGW(192.168.1.2) *** down ***
Jan 13 15:00:44 apinger: ALARM: WANGW(192.168.1.2) *** down ***

Code: [Select]

Jan 13 14:59:36 apinger: alarm canceled: WANGW(192.168.1.2) *** down ***
Jan 13 14:53:05 apinger: ALARM: WANGW(192.168.1.2) *** down ***

Code: [Select]

Jan 13 14:27:05 apinger: alarm canceled: WANGW(192.168.1.2) *** down ***
Jan 13 14:22:01 apinger: ALARM: WANGW(192.168.1.2) *** down ***

Any Idea why this change of status take that long ?