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

Messages - Anth

#1
I am really just posting this hoping you fix this. I downloaded 22.7 AMD64 VGA version and installed it to my brand new Intel NUC

Problem was aftar installation, the GUI would not load. It simply brought up a white screen. No option to enter username or password. Just a blank white screen when I put the IP address in.

I tried changing in the shell WAN and LAN interfaces. Changing to DHCP login address, then static, assigning my PC a static address, then DHCP, changing from HTTPS to HTTP in the shell options. I tried disabling all security, Antivirus, Ad blockers on my PC. Tried Multiple browsers all the same problem. I then tried a totally different PC with no security on it. Same thing.  I then installed a fresh version of windows onto a brand new VMware with no security on it. Same thing

I reinstalled Opnsense from scratch onto the NUC, same thing. Then updated it from the shell. I did everything same issue. I tried the live version, same thing. I spent well over 12hrs and could not get it to just open the GUI.

As simply a troubleshooting test I wiped the NUC and installed PFsense, the install process looked identical to Opnsense's and straight away GUI loaded after installation of it to my hard drive.

I am extremely reluctant to wipe this NUC to try Opnsense again as it seems something is broken in the install process. I do not know what it is. But I am fairly confident something within Opnsense v22.7 is causing the GUI not to load given PFsense worked straight away so while it might be some compatibility issue. PFsense didn't flag it. I was hoping someone could possibly look into this and fix it.
#2
General Discussion / FreeBSD PPPOE Single Thread Issue
December 29, 2021, 05:18:59 PM
Hi, I was just wishing to inquire anyone who may know. But the widely known issue within FreeBSD of PPPOE only being routed using a single thread/core of your CPU thus meaning unless you have a 2GHZ or above CPU any multicore CPU won't be able to manage Gigabit broadband speeds put over PPPOE.

I noticed the upcoming release of Opnsense has an upgrade to FreeBSD13. Will this version of FreeBSD have the issue resolved or is it still going to be a problem?
#3
Tutorials and FAQs / Updated Opnsense, now no Internet
September 25, 2020, 06:23:57 PM
Can someone possibly help with this. I have been using Opnsense for about a year perfectly fine.

Yesterday I used the internal updater, everything was seemingly fine afterwards, this morning however I suddenly cannot access the internet at all.

If I go to Interfaces>Diagnostics>Ping.

I can ping 8.8.8.8 from the WAN Interface. This comes back with 0% packet loss.
If I ping 8.8.8.8 from the LAN Interface however I get 100% packet loss.
If I ping Google.com from the WAN I get "# /sbin/ping -S '172.16.16.122' -c '3' 'google.com'
ping: cannot resolve google.com: Host name lookup failure

So it seems something is wrong with my LAN interface and DNS. But I am getting internet onto my WAN Any suggestions?

on my Firewall, for NAT I had always just left it as "Automatic outbound NAT rule generation (no manual rules can be used)". I hadn't messed with this at all.

Any suggestions to get the internet back on please?
#4
I have just yesterday switched to a custom Opnsense router and am setting things up and getting to grips with it. I am liking it a lot so far. However, there is one very annoying issue I am encountering that is probably a simple fix that I am not seeing.

The issue is, if I set a static IP on the device itself that is connected to the router. It is not showing as connected or existing anywhere that I can see in the Opnsense settings. Its just totally invisible to me.

On other routers in the DHCP leases, even if its static on the device the device will show in the list with that IP. On opnsense it is not showing at all. Its totally invisible.

If I turn off the static IP inside the device settings for whatever device I have. Then it immediately then shows up inside the DHCPv4 leases list as active and I can then set it with a static IP on the Opnsense router, which is kind of half a fix, as I would just like to see somewhere the devices I have connected with a static assigned IP on the device itself. It seems an odd thing that Opnsense would overlook so I am figuring there is a section I am missing or an option I am missing to allow me to see all these.

Thanks