Messages

Solved the issue. Bitdefender is not trusting the site and blocking full gui. Disabling protection gives normal screen.
Adding IP address to trusted sites solved the problem.

Don't think so. Reader View isn't even an option for the OPNsense site. No icon, nor Ctrl-Shift-R will get rid of this.
Furthermore, Chrome shows the same behaviour as Edge, in either normal, or icognito mode.

Hi all,

New install (VM on Proxmox). HTTPS login screen looks like this. Login is possible, but the page isn't rendering properly on either Edge (regular or private window), or Chrome (regular or private window). Cache cleared.
What am I seeing here?

wrong forum, sorry.

Mod.. feel free to delete. Don't seem to know how.

As you probably concluded from having wireless Internet access through computers on the network, this is pretty much a out-of-the-box setup. The issue most likely is with your phone(s).
Delete the connection and connect again..?

Hello all,

I recently set up the openVPN server option following the "Setup SSL VPN Road Warrior" tutorial and it works great using the recommended Viscosity client on a Windows machine.

Connecting from a Linux box however is baffling me. I tried a GUI or the cli option to create a connection. The GUI, as is known, gives very little to no info as to why connection isn't happening. The cli option "openvpn --config [path to .ovpn] file is more descriptive and I'm getting the following output:

$ openvpn --config /home/[user]/VPN.ovpn
Options error: --ca fails with 'OPNsense-udp-1194-ca.crt': No such file or directory (errno=2)
Sun Sep 23 22:01:09 2018 WARNING: cannot stat file 'OPNsense-udp-1194-tls.key': No such file or directory (errno=2)
Options error: --tls-auth fails with 'OPNsense-udp-1194-tls.key': No such file or directory (errno=2)
Options error: Please correct these errors.
Use --help for more information.

Looks to me like the client is asking for a ca cert and tls key? So - what am I missing? Do I need to edit he default client export file? Something else? I can't seem to find the documentation I need to make this work and any help is appreciated.

Thanks in advance for your time.

I looked at it some more later this evening and with a fresh eye. I honestly didn't do anything else than enter 8.8.8.8 in my main workstation into DNS field for testing, and that worked. Removed it and it still worked. Then added 2 more interfaces, 1 for WiFi and another for Guest Wifi, gave both DHCP to hand out, added any-any rules in the FW and all is well.

All in all I'm glad it's working as expected, but on the other hand I would love to know what was wrong initially. Oh well...

(How can I mark this as solved?)

Thanks. I will, but am off to work. Later this afternoon or early evening, GMT -06:00 I can do this.

Hello all,

My question is rooted in frustration with myself. Usually I find that if no one else has the same issue, it's ME that's doing something wrong... Still - I hope someone is willing to be kind enough to help me out.

I have had OPNsense on a dedicated box before and had it running just fine. VPN's, different subnets - the usual soho configuration. Now, I've decided to put a new install on a VM in Proxmox. The host box has 2 onboard Intel G-nics and I've put 3 more G-nics in. 2 of those also Intel and one Realtek.

OPNsense has - so far - two vmbr's: vmbr0 (management nic for Proxmox) as the LAN and vmbr1 for WAN.

With OPNsense turned off, my firewall/router is a Sonicwall TZ210 and everything works. If I configure OPNsense with the same IP addressing/gateway/DNS settings and disconnect the Sonicwall and test with OPNsense, I have a problem...

I can ping anything by fqdn or ip address from OPNsense VM, using the WAN as the source, but nothing else works.
Packet capturing shows me that packets from the LAN are leaving OPNsense, but simply trying to open a webpage eventually times out and tells me the website cannot be found.

AAAAARGH...!! I'm sure it's documented elsewhere but I've searched and I've searched, but I couldn't find (... Elvis, anyone?) the answer to the problem.