Messages

https://docs.opnsense.org/manual/dhcp.html#reservations

A classic one. Easy to fix.

Thank you!!

I just found this topic: https://forum.opnsense.org/index.php?topic=35080.0

Where a power user said the ranges can't overlap - and apparently I had that IP indeed within range, which I just narrowed down

Thanks!  I will give it a try!

Hi there, I have my cellphone assigned to 192.168.1.6 and it normally works fine

To my shock today I plugged in a new device for the first time, an Android TV device which uses DHCP as anything else to get an IP, and it apparently was given 192.168.1.6 as an IP address even though it's MAC address is completely unique and not even remotely similar by a single digit.

What is going on here? thanks!

Dunno what Unbound's problem is, I have a fairly straightforward setup

In Services > Unbound > Query Forwarding, I have 192.168.1.24 port 5353 enabled which is my DNS resolver.

Randomly today I could not get onto aliexpress.com, my browser said it couldn't resolve the address.  I opened my terminal, and 'nslookup' also failed with SERVFAIL.  However I then typed dig address.com @192.168.1.24 -p5353 and it worked INSTANTLY. 

Tried dig @192.168.1.1 and it failed.

Where is the massive desynchronization going on here?  Why is OPNsense and Unbound reporting SERVFAIL when it very clearly is working just fine via dig?

Why not?

Terrible design choice, what do you expect people to do, constantly be deleting and recreating their gateways as needed?

I have to constantly re-do and update the gateways as I change tunnel endpoints, there's no reason I should not have permission when I am root

It's more likely the pppoe interface is displaying the correct ip address as negotiated from IPCP, and that your ISP has another layer of SNAT, nat'ing your PPPoE address to another address.

Thank you for the reply!

Oh dear, okay, well it seems that the only one listening to public incoming connections is the 78.x.x.x IP and NOT the 142.x.x.x IP reported in the monitor screen

I have a WireGuard server listening and it won't work when connecting to the 142.x.x.x internal IP, but works great when the 78.x.x.x IP is specified!

Thanks again for your time

Okay and just to follow up, after more testing, so on OPNsense itself if I spawn a shell and 'curl ipinfo.io' it reports the 142.x.x.x address which does report as my correct city and all other details, but then if I simply receive a DHCP address and do a 'curl ipinfo.io' on the client -- it reports the actual correct 78.x.x.x IP!  The one that I need to be passed to my Dynamic DNS monitor.

Thanks again, sorry for the triple post

I've even tried different check IP methods like 'icanhazip' and it STILL is reporting the 142.x.x.x IP instead of the 78.x.x.x one

So confused!

Hello, novice user here, using Bell Fiber internet in Canada.  I use OPNsense of course, completely up to date, and have think I've narrowed down my Dynamic DNS updating woes to the fact OPNsense is detecting the wrong IP address as my WAN IP!

What I mean is this

You cannot view this attachment.

If you see here, the IP is being reported as a 142.x.x.x address, which is being passed on to my Dynamic DNS client, and is unconnectable.
But when I open a terminal and do a 'curl ipinfo.io' for example, it displays my true IP which is a 78.x.x.x IP address

So I guess my question is, why?  And how do I fix it?

I need to pass on the 78.x.x.x IP to the Dynamic DNS updater, and simply choosing WAN isn't working

Thanks so much!

Hi there

OPNsense 25.1-amd64
FreeBSD 14.2-RELEASE
OpenSSL 3.0.15

Every day, several times a day, I have to re-enter my login credentials to OPNsense (192.168.1.1).  It absolutely refuses to keep me logged in and I'm not sure how to change this as it's persisted across both Brave and Edge now!

Furthermore it always flips back to 7 rows in the view and I need it to stay on ALL!  So I can see more than 7 small results at a time!

Thanks so much for any help

I've never disabled any cookies, though!  It's just my regular web browser and I don't have any kind of cookie rejecting stuff enabled or uBlock etc..

Thank you though, I am off to Google

Hi there

OPNsense 24.7.12_4-amd64
FreeBSD 14.1-RELEASE-p6
OpenSSL 3.0.15

Every time I go into Aliases or tunnels or anything at all really, OPNsense is defaulting to a piddly 7 results at a time. 

I have to stop what I'm doing and go into the top right corner and change the 7 to "ALL" which wouldn't be so bad if it remembered, but it doesn't remember :(

I followed the guide in the OPNsense documents for Selective Routing to External VPN.  The tunnel is up with no problems, and connectivity works, yet my dashboard is showing the Gateway is offline, and in the interfaces, appears red with 100% packet loss:

You cannot view this attachment.

And to make things even more ridiculous, the gateway address listed IS pingable!  From right within the tunnel itself!  It's just OPNsense having problems for some reason?

And I obtained the gateway the exact way the guide says -- I connected the tunnel, did a traceroute, and that IP is the first hop after 10.2.0.1

Thanks kindly for any help!

I am in absolute hell right now.

Tried following the WireGuard Selective Routing to External VPN Endpoint tutorials and now I notice in the dashboard the wheel is filled up with state violations.  When I click the pie chart, it shows non-stop scrolling of state violation rules

I am in literal hell right now, and all I wanted to do was connect to my VPN's with OPNsense.

I hate this so much.  The guide I followed doesn't seem to work either, my DNS is leaking

I'm here for the same reason..  This is an absolute nightmare.  The documentation is one of the worst things of all, the guide just totally is ignorant to the needs of the user at the bottom of it

The tunnels are established, and I can assign a client to the alias which will then browse through the tunnel with no problems.  A 'curl ip.me' check shows the VPN IP..  But I can't solve the leaking DNS problem