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 - FrankAusNRW

#1
After 48 hours I can confirm, that the procedure above is working.
Non of the weired IP-address reservations was comming back so far.

Even after upgrading to 26.1.5 it's all quiet.
#2
I just did it a bid more radical, after i've identified the two container on proxmox:
1. I've stopped KEA
2. I've renamed both KEA csv-files, no other files exist in that folder (just to keep them)
3. I gave the two proxmox container a new MAC-address (both hat multiple IPv4 addresses assigned to just 1 (!) MAC-address
4. I've maintained the new MAC-addresses in KEA as fix leases for the two proxmox container
5. I've fired KEA up again, immediately a new file "kea-leases4.csv" was created
6. I've fired up the two proxmox container
7. The fix leases are correctly assigned to the proxmox container

Finally, no weired assignments w/ 86400 seconds and no MAC address and no name appear in the csv-file
#3
I've read the recommendations earlier and disabled "Automatic Discovery". In a first instance this doesn't help.
Maintaining the csv file in /var/db/kea/ was helping, but an hour later all IP addresses have been "in use" again.

The proxmox comment is also the same here. I'm running 2 proxmox nodes, and 2 container are the root cause for utilizing the IP addresses, identified by the MAX addresses in the "Automatic Discovery" log when this was still activated. I coudn't figure out what is different at the two containers compared to the oder ones, apart from the fact, that the interfaces had only IPv6 addresses assigned. But I'm not using nor deploying IPv6 adresses at all by KEA. And no other DHCP server is running.  - weired!

I'm also not using VLAN - yet.
#4
Same issue here w/ OPNsense 26.1.4. ICS-DHCP is not installed anymore and DNSmask DHCP is disabled, so only KEA is running.
The DHCP range is going from .200-.249. All IP adresses in the DHCP range AND all unused IP addresses outside the DHCP range are blocked, even for inactive clients w/ fixed leases.
Effectively there is no chance for a client to obtain an IP address at the moment.
This is causing some trouble.

Is there a workaround or a fix in the near future?
If not, I need to get back to ICS or DNSmask DHCP for the time beeing.

The installation was a fresh ISO 26.1.2 installation.
#5
Bei mir läuft OPNsense (24.7) aktuell auf einem APU2 Board an einer 300er Glasfaserleitung hinter einer Fritzbox. Rein von der Leistung her reichen die aus.
Ansonsten schau mal nach einer ausrangierten Sophos SG 230 rev.2 im 19" Gehäuse wenn etwas mehr Leistung erforderlich ist. Hardware lässt sich aufrüsten, ist ein "normaler" x86 PC mit Intel Pentium G4400 CPU.
#6
I've tried this on a SG 230 Rev. 2 w/ 38.400 sucessfully.
Or: try another cable.
Or: Switch primary- / secondary console
#7
Just installed OPNsense 24.7 on a SG230 r2 appliance smoothly.
The CPU is a G4400 (2c/2t) that can be replaced by another LGA1151 socket CPU if required.
#8
I'm just testing a SG230 v2 appliance w/ 6+2 ports installed.
Installation went smooth, CPU can be changed, memory can be expanded.
If the LCD and the buttons are working need to be tested, but I woun't need that at all.
#9
My issue has been solved by restarting the services.
#10
Thanks Patrick, I've restarted the services and now it is working again.
The interfaces are still set to "recommended", so no selection of interfaces at all.
#11
Hi,
I'm having almost the same issue. SSH is not working too.

On my APU2 board I can still login to the WebGUI when connected via OpenVPN.
If you have installed a VPN service you may give it a try?
#12
Hi there,
I'm running OPNsense on an APU2 board already for a year and happy with it. Just normal homelab services and OpenVPN for remote access.
Recently - on holiday - I've updated OPNsense remote via openVPN to 24.7 and further to 24.7.1 without any issues. Remote access works perfect.

Getting back 2 days ago I've tried to open the WebGUI on the defined https port, but cannot login anymore.
The weired thing is, that I can still login when I'm using the OpenVPN tunnel, but NOT in my own LAN at home.

The message is "ERR_CONNECTION_TIMED_OUT". I've tried Google Chrome, Firefox and Edge, non is working.

All devices are online and Internet access is just fine.

SSH access with PuTTY etc. fails too.

Any idea what is happening here? I'm lost ...