Topics

I've previously had an issue early last year on performing an update and getting the error

Could not authenticate the selected mirror.

I had some advice and changed settings and was then able to update from 19 to 20.1.7 but now if I try to update I get the same issue as before so unable to update to 20.7, but have not changed my settings

Are there still issues with updating when using ipv6? Is there a way to force the update via ipv4 without having to mess about with configuration changes?

Thanks

I have traffic shaping setup (followed the opnsense documentation) for my connection to ensure no device hogs all the bandwidth, this is set to ip protocol but then source/destinations are ipv4 settings.

do i just do similar for ipv6 to ensure that is traffic shaped and will it then share the whole bandwidth between both ipv4 and ipv6 devices

thanks

I've noticed when i get a ppoe disconnection with opnsense I don't always get my ipv6 addressing back until after I've rebooted opnsense.

Again this morning i lost ipv6 and access to my work vpn (but was able to connect via mobile data) - i rebooted opnsense a few times and also updated to the 20.1.7 from 20.1.? it was only about an hour have my connection had been up and running again that dhcpv6server started working again and handing out ipv6 and roughly the same time i saw ipv6 working on the lan.

Is there a way to record that you are not receiving an ipv6 on wan and when it came back on other than using external sites to check.

Also why do I always have to fully reboot the system to get ipv6 working again after there has been an outage with my connection through maintenance by isp or just disconnection of the ppoe.

I've noticed mainly after internet has reset the insight aggregator stops working

on checking the general logs it says the following

Code Select Expand

flowd_aggregate.py: flowd aggregate died with message Traceback (most recent call last): File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 158, in run aggregate_flowd(self.config, do_vacuum) File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 79, in aggregate_flowd stream_agg_object.add(copy.copy(flow_record)) File "/usr/local/opnsense/scripts/netflow/lib/aggregates/interface.py", line 72, in add super(FlowInterfaceTotals, self).add(flow) File "/usr/local/opnsense/scripts/netflow/lib/aggregates/__init__.py", line 187, in add self._update_cur.execute(self._insert_stmt, flow) DatabaseError: database disk image is malformed

what is the easiest way of resolving this

not sure which part of forum this is best in so stuck in GD

When you perform an install and tell the installer you grab the configuration from a backup can it automatically ignore the import settings that rely on plugins to work, so they are not brought in

Or can it be set that once installed, it downloads all updates and if you are restoring from a configuration that it automatically installs any plugins required

Hi,

How can you get the PPPoE uptime on the main lobby dashboard instead of it being hidden away under interfaces>overview

thanks

Hi,

I have opnsense configured on a 10.x.x.x range for all my wired devices

I have Google Wifi installed in router mode to make use of the mesh network (as some of the units are in areas that can't be hardwired back) - the google wifi gets it's ip on the wan for 10.x.x.x range and then allocates the range 192.x.x.x to its clients.

Is there a way of enabling the google wifi to provide addresses within the same range as the wired devices

And is there a way of getting IPv6 addressing through to the Google Wifi so it can allocate IPv6

I have a static ipv6 setup and isp provided range /64 (wan) and /48 (local) - my wired devices are receiving their ipv6 details, but would like to get this on the wifi devices as well

Hi,

I recently moved to ZEN from Sky and have had to rebuild my Opnsense setup from scratch as for some reason things would not work with a straight switch from Sky MER to ZEN PPPoE. I even performed a reset of the configuration and imported my settings but this still caused problems and then found out every time I tried checking for updates it would fail with authentication issues and plugins became listed as orphaned

So I performed a full rebuild and manually slowly entered all my settings again and found that i when i added the ipv6 wan monitoring gateway I was unable to use the firmware updates but when I disabled the gateway I was able to use the firmware updates.

I tried this on the february build of 19.1 and also after updating to the latest update for 19.1 and the problem still occurs.

So is this a bug or something else the cause of this, ideally I need to get the ipv6 wan monitor working so I can add ipv6 dns entries in the general settings area of opnsense

i get an ipv6 address from my isp and all wired devices on my network work with ipv6

but I have google wifi setup, but to get it work as a mesh I need it to use normal router mode as setting it in AP mode means I can't use the mesh network and some of the units can't be used as can't backhaul via ethernet.

I've enabled ipv6 on the google wifi and it says enabled, but it's not passing any ipv6 to client wifi devices of which I want to do, probably as it's only receiving a single ipv6 address and i have no dhcpv6 server running.

So can anyone offer any advice on how to get opnsense provide to provide an ipv6 to the google wifi, so devices can use ipv6 out to the internet

Hi,

I'm hopefully setting up a google wifi system for home (i was using a netgear orbi, but returned as constant failures with the satellites), but unlike the orbi, google recommends leaving the device in default router mode and not bridge mode otherwise mesh will not work.

I can't wire every unit up so need to get the mesh side working, but this will cause the wifi to be double natted. This isn't too bad for devices accessing the internet that won't be gaming, but how will i get these devices to then see my networked devices.

Google recommends,  setting router into bridge mode, then connecting the google wifi, then any switch after it, but if set to bridge mode how easy is it to configure this and wouldn't it then eliminate the need for opnsense?

Hi,

When I used smoothwall, I had a plugin that was able to monitor the modem (HG612 plus others) and display a graph on the system and was an excellent mod, this was written in Pearl and wondered if OpnSense would be able to use this or would it have to be re-written.

If it can be re-written to work with OpnSense, would anyone be willing to take on the challenge.

regards
Walkerx

I've recently upgraded my motherboard and at same time upgraded opnsense to 18.7.10 and have noticed that i'm unable to get ipv6 from my wan.

I've checked my settings in the wiki for sky fibre setup and the configuration is correct, so unsure of why not receiving any ipv6 settings and when test via ipv6 test site, it reports that ipv6 is not supported.

is there anything else that needs doing to get this working again

Hi,

I've just updated my old motherboard to a j3455N which supports aesni, but noticed that when booting from the installer it always hung on HPET and that unless you attach a vga cable it won't boot at all.

I found a few work-arounds on the net mainly for pfsense for the hpet issue and used this to get the system up and running, but does anyone know if this issue will be resolved in a later version of freebsd/opnsense

i've created a boot/loader.conf.local file and added hint.hpet.0.clock=0 which allows the system to be rebooted without someone having to use the console.

I've had IDS enabled and had installed snort, but every so often my whole network has gone down and when trying to connect to the OS box I've been unable to either via ip or name.

Due to these ongoing issues I attached a keyboard and monitor to the system, so could access the console - on doing so, only thing I could see was blocking from the ids, and if I logged onto the box and pinged a web address this was successful, but until I told the system to reboot fully I could still not access the box or internet from any networked device. I didn't know what commands were available to restart any of the services and in the menu option, you only have the option to restart all which wasn't successful.

I've now removed snort from ids and left it was the standard ones, but noted that the abuse.ch rules say 'not installed' and if tell the software to download and update the rules, these never change.

I've also ticked the enabled and ips mode boxes on the settings page as well setting the interfaces to wan

would these settings be correct or will i need to make further changes

I had both of these working on my setup, but have noticed recently that neither of them were running and wouldn't start after a reboot or when trying to manually start them.

I've removed both plugins and retried installing them, yet they still will not start

Would there be a configuration setup that could be preventing these from restarting/working

thanks

If my internet connection drops and then reconnects I seem to lose access to my opnsense gui, so can't restart dns or anything.

this is either via wifi or wired pc using a static ip

the only way to resolve the issue is to reboot the opnsense box, surely shouldn't need to do this when I loose connection.

I'm using unbound dns and upnp as have multiple xbox's setup and internet provider is sky

Would anyone be able to offer any advice, thanks

Hi all,

I've setup my outbound nat for use with multiple xbox's, but having a few issues with the nat status.

I did perform a search for the configuration on the forum, but its been removed https://forum.opnsense.org/index.php?topic=3521.0

So I've used a pfsense configuration to see if that works, and think i have set this correctly, but unsure

I know there are issues with the nat status on xbox one due to a bug, but i rarely saw problems with pfsense, so would be grateful if anyone has multiple xbox's setup and working could they share their configuration so I can see if mine matches

thanks

I've setup a couple of port forwarding rules which are both listed under firewall->nat->port forward
but what i have found is that one of them is listed under firewall->rules->lan while the other is not listed at all.

the rule that doesn't have the entry is for plex and I see the following error in alerts

[There were error(s) loading the rules: /temp/rules.debug:47:rule expands to no valid combination - the line in question
read [47]:nat on re1 inet6 proto tcp from re1:network to $PlexServer port {32400}->re1 port 1024:65535 #Plex Remote Access]

should both port forwards be shown in the rules section?

Hi,

I've moved from pfsense where previously had plex working without any issues, but I'm having trouble getting the port forwarding working on opensense.

I've performed a search and checked my settings matched with what others have configured, but still i'm unable to get it working if I choose a static port, even the default port, but if I have upnp enabled and let the system set this up, it works but later it will stop working.

I've grabbed a quick screenshot of what is happening when using upnp configuration and as can be seen the firewall is randomly denying access to plex

would be grateful for any help on getting this working using nat and port forwarding

I've installed and configured os-upnp to allow multiple xbox's to operate on same network, but when I've gone into the firewall settings to enable pure-nat I'm unable to locate this.

I have enabled the option 'reflection for port forwards' but this is only a tick-box, does this mean it is working in pure-nat mode or nat+proxy


thanks