Messages

1

18.7 Legacy Series / Re: Reporting: Traffic, IPSec Top-List empty

« on: November 08, 2018, 08:29:59 am »

Thanks for clarification

2

18.7 Legacy Series / Re: [Solved] nping functionality

« on: November 07, 2018, 05:07:09 pm »

Will do 

3

18.7 Legacy Series / Re: nping functionality

« on: November 07, 2018, 04:57:20 pm »

Arg, thanks, absolutely correct. Used always nping for that.

Would still be nice to be freely set a source ip at "Interfaces: Diagnostics: Ping".

4

18.7 Legacy Series / [Solved] nping functionality

« on: November 07, 2018, 04:13:31 pm »

Hi,

is there any tool for opnsense equal to e.g. nping to forge the source ip for testing via icmp?

Thanks,
Thomas

5

18.7 Legacy Series / Reporting: Traffic, IPSec Top-List empty

« on: November 07, 2018, 02:54:26 pm »

Hi,

when we go to /status_graph.php, Report Traffic and select IPSec, the top list is empty, although traffic is active.
Anyone experiencing the same issue?

Settings the Interface to e.g. LAN works fine, and the top list is shown.

Thx

6

18.7 Legacy Series / Re: Direct edit of ipsec.conf possible?

« on: November 07, 2018, 10:57:31 am »

Thx, then we have to go the default way.

7

18.7 Legacy Series / Re: Direct edit of ipsec.conf possible?

« on: November 06, 2018, 01:32:54 pm »

yes, we also used it for that. Maybe @Franco can enlighten us?

8

18.7 Legacy Series / Re: Direct edit of ipsec.conf possible?

« on: November 06, 2018, 11:18:29 am »

Could we maybe work with "Manual SPD entries"?

Strongswan automatically creates SPD policies for the networks defined in this phase2. If you need to allow other networks to use this ipsec tunnel, you can add them here as a comma seperated list.

9

18.7 Legacy Series / Re: Direct edit of ipsec.conf possible?

« on: November 06, 2018, 08:16:53 am »

Thanks, not really what we expected.

10

18.7 Legacy Series / Re: Direct edit of ipsec.conf possible?

« on: November 05, 2018, 08:25:09 pm »

The VPN "partner" insists on every single small subnet routing

11

18.7 Legacy Series / Re: Direct edit of ipsec.conf possible?

« on: November 05, 2018, 06:20:54 pm »

We have 10 subnets on left and 12 subnets on right. How to add that via the GUI, when for every SPD the local network and the remote network must be entered?

12

18.7 Legacy Series / Re: Direct edit of ipsec.conf possible?

« on: November 05, 2018, 04:06:26 pm »

left and right subnets, quite a lot - would be at the ipsec.conf just two lines.

13

18.7 Legacy Series / Direct edit of ipsec.conf possible?

« on: November 05, 2018, 12:50:34 pm »

Hi,

we have for one VPN connection many subnets to route and via GUI its hard to add them.

Is it possible to edit directly the ipsec.conf or where is OPNsense storing its own configuration for strongswan?

Thanks

14

18.7 Legacy Series / GUI, ssh access broken - else working

« on: November 05, 2018, 11:51:50 am »

Hi,

we are running our OPNsense on Hyper-V for month, and every x weeks, the GUI is no longer working and access via ssh is broken (seems the ssdh daemon is down).

Firewall routing is still fine, also openswan is working as expected.

So far we also cant login via console, it hangs after entering "root" for the login.

The console output only shows:

hvvss0: Unknown opt from host: 4

Did anyone experience a similar behavior?

OPNsense version = 18.7.5

Thanks,
Thomas

15

18.1 Legacy Series / [Solved] OpenVPN: Lets Encrypt = VERIFY ERROR

« on: June 09, 2018, 02:30:31 pm »

Hi,

we setup OPNsense (latest version of today) with OpenVPN, which works fine so far.

OpenVPN -> Servers -> Server Certificate, we use the internal OPNsense for "Server Certificate".

Error on the windows client:

Code: [Select]

Jun 09 14:46:41: OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed

Client: openvpn-install-2.4.6-I602.exe, latest version from openvpn.net. Same issue with Viscosity as openvpn-client.

Solution: On client export use "Inline Configuration", "other" and NOT Archive.

Hopefully also for someone else.

Best