Messages

That worked and a button would be wonderful.

Now the question is why did it get corrupted?

Possibly dropped power? I have the box set to resume after a loss of power so I could have missed it.

I do have a UPS but it's old. I'm thinking I may need to do a real world test on the UPS. ( unplug from electrical service and let it run to see if the OPNsense box shuts down gracefully still or crashes from a bad UPS battery)

For those wonder what GDickson mean by "LL" = link local IPV6 Address.
Looking into it more may have something to do with my ISP giving out the link local IP. However doesn't quite explain why Windows direct was getting a proper IPv6 when connected directly to the bridged modem.

Same for me, I can get a other than LL address on windows and opensuse tumbleweed connected directly to the cable modem (cable modem has no routing is just a bridged modem) also using a linksys router, belkin router, d-link router and a have no idea was laying around no name cheapy don't even know where I got it or why router.

Seems the same behavior for a DSL modem also regarding just a LL address.

That was why it made it so damn confusing when on OPNsense we see just a LL on the gateway and instead of consistently testing anyhow we figure it won't or don't work and configure once again.

OPNsense is the only appliance / firewall-router I see this behavior with the gateway having a LL address.

When I ignored what was in the gateway and started to test each configuration was when it all came together WITHOUT throwing money at it hmmmmm.

I'm using

Code Select Expand

OPNsense 19.1.b_306-amd64
FreeBSD 11.2-RELEASE-p4-HBSD
OpenSSL 1.0.2q 20 Nov 2018

vnstat has been working just fine until today. No changes made by me, nothing I know of changed.
I tried restating the service, no help. I tried rebooting, no help. I deleted the plugin and reinstalled, no help.

Code Select Expand


vnstatd[51566]: Error: Database load failed even when using backup (Permission denied). Aborting.

ah I got it.

you want a board or system that's running OPNsense to have POE built in on it and NOT a separate switch or dongle.

Never seen one but it's not impossible. More failure points on a main board maybe.
The Braswell looks interesting but hard to find documentation for it to see what the poe situation is on the board.

Have you looked into Ubiquiti? You might be able to get some of their software running on the OPNsense box to control their switch from OPNsense?

thats why i told you to ignore any LL while configuring. I also always show a LL for the IPv6 gateway and for the lan I get the proper addressing shown.
It takes a few moments and most often shuting everything down at least once then botting in order.

1) dsl/cable/whatever modem
2) OPNsense box
3) whatever else is left on the lan.

for example my gateway shows LL

Code Select Expand

Gateways
Name RTT RTTd Loss Status
SPECTRUM_DHCP
90.59.64.1 7.2 ms 0.7 ms 0.0 % Online
SPECTRUM_DHCP6
fe80::2a3:d1ff:feed:7c19%em1 33.1 ms 1.7 ms 0.0 % Online

My two biggest hurdles to get it working was i had multiple gateways so I deleted all but 2 which helped.
And like you I paid far to much attention to what what was assigned at the gateway and didn't just check when I seen a LL.  Something isn't right in OPNsense I imagine maybe?

It all works :)



Congratulations you can count yourself as one of the few there to have it working.

Hi,

The link on the wol widget that takes you to the wol service is broken.
It goes to Page not found go back to previous page

greg

Col can you go to the kame project site and see the turtle moving even if it looks like you have no wan?

My wan looks like it has a fe LL address and my lan has a 2600 type.

by looking at what i see in my gateway it looks like no IPv6 also but it is there.

Code Select Expand

Gateways
Name RTT RTTd Loss Status
SPECTRUM_DHCP
90.59.64.1 7.2 ms 0.7 ms 0.0 % Online
SPECTRUM_DHCP6
fe80::2a3:d1ff:feed:7c19%em1 33.1 ms 1.7 ms 0.0 % Online

    Interfaces

  LAN 1000baseT <full-duplex> 192.168.10.1
2603:9090:e719:1600:215:17ff:fee8:97e0
  SPECTRUM 1000baseT <full-duplex> 96.59.119.50
2603:9090:ff00:e7:3c39:1679:317a:9099

now theres 2 ways explained and it cost nothing but if you want Bart you can give me your money to spend :)

cryptic non explanations help nobody.

you need to explain a lot better than give ra a try

It seems most everything to do with IPv6 is exceptional as in exceptionally hard to get working.

so if i modify these lines

Code Select Expand

## Get all adX, daX, and adaX (IDE, SCSI, and AHCI) devices currently installed
exec("ls /dev | grep '^\(ad\|da\|ada\)[0-9]\{1,2\}$'", $devs); ## From SMART status page

to this

Code Select Expand

## Get all adX, adaX (IDE, SCSI, and AHCI) devices currently installed
exec("ls /dev | grep '^\(ad\|ada\)[0-9]\{1,2\}$'", $devs); ## From SMART status page

I should in theory lose the da0 and da1 in the widget?

Will they be over written on a reinstall or upgrade?

  from chris42

How would this work on ipv6? I tried to mimic the NAT rules for ipv6, however then the DNS queries fail completely

Excellent question what would be the destination for IPv6 or what is the equivalent to 127.0.0.1 for IPv6?

would it be ::1 for the loopback like 127.0.0.1 is for IPv4 loopback?

I got brave and did a back up and upgraded.

The kernel and base do indeed stay locked!

It's safe to do :)

OPNsense holds few surprises and does what it should.

My thanks to the maintainers,staff and everyone that helps! Excellent software.

greg

I'm chicken also lol It took too much work to get the firewall running this well!

I need to move the wan nic to another nic and I'm even waiting on that.

I'll do it in a VM first to see how bad i mess things up.

Is it possible (very low priority of course) to have the UPnP status as a widgit for the dashboard?

when you do an update for the bogonsv6 it causes the browser (firefox) to pop up with (a page is slowing things down) stop it or wait.

The IPv4 bogons go quick, no slow downs.

tried waiting but it's never ending so had to stop it.
bogons do update according to the log.

Code Select Expand

Nov 24 07:11:58 root: update bogons is ending the update cycle
Nov 24 07:11:58 root: Bogons V6 file downloaded: 73 addresses deleted.
Nov 24 07:11:58 root: Bogons V6 file downloaded: 103457 addresses added.
Nov 24 07:11:58 root: Bogons V4 file downloaded: 2990 addresses added.
Nov 24 07:11:55 root: bogons update is beginning the update cycle
Nov 24 07:11:55 root: bogons update starting