Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - Free_Norway

#1
Hi

The advanced configuration on the OpenVPN Client creation page has for a long time been marked as being replaced/removed.
Is there a chance the features like "ping settings"(ping method/interval/timeout), UDP Fast I/O, Exit Notify, Send/Receive Buffer, persist-key/persist-tun, Gateway creation options could be integrated in the creation page?
I can see in the config(/var/etc/openvpn/client_.conf) that some of this features are set automatically, is there a description about that?

Kind regards
Sebastian
#2
Hi all

First of all i would like to thank the team for the excellent work they are doing with Opnsense :)

i have a problem with the creation of gateways for all the VPN interfaces i use.
By default there is always a ipv4 and ipv6 gateway created.
On an earlier version of Opnsense(i think before version 19) it was possible to rename and them delete the ipv6 versions i dont use. Now this is not possible anymore.
The only possible solution is to deactivate them.

By readiing a guide how to set up a multi vpn wan system i saw that the latest version for pfsense has now an option in the OpenVPN Client creation wizard to change the default option from "both" to ipv4 only or ipv6 only.

Is there any chance that such an option would be integrated into the OpenVPN client creation wizard in Opnsense or is there the possibility to do this manually?

Kind regards
Sebastian


#3
Hi all

First I want to thank the OPNsense Team for the excellent work they are doing, this is an amazing product.

I have a problem with suricata.
After some small changes in the configuration(don't really remember what I changed), suricata doesn't want to start.
I have tried disabling it and reboot, changing the settings back and forth, reinstall suricata....
but nothing helps.
When I try to start it from the GUI, the following lines appear in the log:
Sep 9 11:08:08 configd.py: [f7917fa0-b5e3-4953-8317-1094d29ece73] returned exit status 1
Sep 9 11:08:08 root: /usr/local/etc/rc.d/suricata: WARNING: failed to start suricata
Sep 9 11:08:08 configd.py: [f7917fa0-b5e3-4953-8317-1094d29ece73] start suricata daemon

Since I'm no expert, I really don't know what it means.

Help please! :)
#4
16.7 Legacy Series / no concole menu after bootup
December 20, 2016, 11:13:58 PM
Hi

After updating to 16.7.11_1 i lock me out of the my opnsense box.
When i tried to login through the console menu i noticed its not visible anymore.
I restarted the box and after the bootup the only thing that is visible is welcome menu and the interface list.
The only keyboard input that works is ctrl+alt+del which triggers a shutdown.

Is this supposed to be like this/are there new settings too enable the menu?

Regards
Sebastian
#5
16.7 Legacy Series / 16.7.8 update broke Openvpn setup
November 16, 2016, 11:47:24 PM
Hi

Has anybody experienced problems with openvpn client setups after the 16.7.8 update?
My client vpn's are not working anymore.
The log showes they(3 seperate vpn)connect but after some seconds the log shows different failures.
When disabling 2 of the clients i get the active client to reconnect, but it failes again after some seconds.
The log almost always shows these 3 lines or line 1 and 3
MANAGEMENT:Client disconnected
MANAGEMENT:CMD 'status 2'
MANAGEMENT:CMD 'state 1'
after that it reconnects again

Does anybody has an idea whats wrong?
#6
16.7 Legacy Series / UEFI Boot broke after 16.7.2 update
September 01, 2016, 10:22:28 AM
Hi

Has anybody encountered the same problem.
I just update my working opnsense box from 16.7.1 LibreSSL to 16.7.2 OpenSSL and it broke the UEFI boot.
Now when in the boot there is the message:
Failed to load '/boot/loader.efi'
Panic: No bootable partition found!

Any ideas?
#7
Hi all

After the upgrade from 16.1 to 16.7  didnt work very well(openvpn clients didnt work, gateways shown up twice) i decided to reinstall 16.7 last weekend.
After fiddeling around for a while with the USB-pen installer issue i got it installed and after a komplete new configuration everything was working perfect.

Now on monday things got strange.
After running for some time, the opnsense box rebooted on it's own when i was at work.
After coming home i checked opnsense and during my checks i rebooted again 4 times in 20/25min.
Then i stresstested it with setting up a couple of downloads with about 65-75 Mbps troughput over VPN.the firewall ran without a hickup.
Today it started again with the random reboots.

Can anybody tell me where to find the complete log?
The logfile under System-»Log file only shows logs after the last reboot

Regards
Sebastian
#8
Hi all

I use opnsense in a multi-VPN-WAN loadbalancing/failover setup.
The setup is from my vpn provider forum for setting up a multi wan vpn firewall, all traffic routed through one of the vpn wan's.
Today i tried traceroute and the result is showing my ISP ip address.
I tested my setup with 3-4 DNS leak test sites and all are reporting no DNS leaks.
Since i'am not a firewall expert, my question is:
Is this an expected result?

Thanks in advance :-)
#9
Hi everybody

I have been using Opnsense for over a year now and it's really a great product.

I use it to root all my traffic over a multi(3) vpn wan loadbalancing/failover config.
To set it up i followed a how-to in the vpn provider forum.

Since i'am not an firewall expert i have more and more questions about the rulesets i use and if there is a better way to set it up.
One example is the opnense.org how-to that explains how to set up Spamhaus.When setting up the firewall rules i wonder if i should choose my loadbalancing/failover group or both under the "gateway"?

I wonder if there is anybody that can help with this or is it possible to pay for such support?

Regards
Seb

#10
Hi

i'am, seeing this warning Message when i look at the boot cycle via the serial console.
I have seen this mesage before, but there has never been an issue, so i have overlooked it.
Trying to mount root from ufs:/dev/ada0s1a [rw]...
WARNING: /mnt was not properly dismounted
Mounting filesystems...
tunefs: soft updates remains unchanged as enabled
tunefs: file system reloaded
WARNING: /mnt was not properly dismounted


Is this something to worry about?

Regards
Seb
#11
Hei

I' am running a Opnsense Box With3 VPN WAN Connections in a loadbalancing/failover config.
After updating to 16.1.4 the services status view shows all the OpenVPN Client services as not started, dwspite all of them runing.
The same issue is in VPN->Connection Status

Does somebody have the same problem or has any tip for an solution?

Seb