OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of Vasco »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

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.

  • Messages
  • Topics
  • Attachments

Messages - Vasco

Pages: [1]
1
24.7 Production Series / Re: Kernel panics after upgrade to R1
« on: July 17, 2024, 12:35:06 pm »
Quote from: franco on July 17, 2024, 12:11:20 pm
Let's just try this one:

# opnsense-update -zkr 24.7.r1_2

I placed a bet...


Cheers,
Franco

Sorry for partially missing the tests. Submited a crash report after boot with this one but didn't see a "panic" in dmesg-

2
24.7 Production Series / Re: Kernel panics after upgrade to R1
« on: July 16, 2024, 11:29:37 pm »
Quote from: computeralex92 on July 16, 2024, 09:37:57 pm
Quote from: computeralex92 on July 16, 2024, 09:32:59 pm
Quote from: franco on July 16, 2024, 09:19:11 pm
We were wondering if this does this also crash with the beta kernel? Because it sort of indicates that it didn't before.

# opnsense-update -kr 24.7.b


Cheers,
Franco

Let's try it out ;-)
Already downloaded, reboot is happening in a sec.

I'm now running the following kernel:

Code: [Select]
FreeBSD OPNsense.localdomain 14.1-RELEASE FreeBSD 14.1-RELEASE stable/24.7-n267717-cf61c67cb34 SMP amd64

I will keep you updated, but directly after the reboot no panic happen.

did the same and also no panic after reboot

3
24.7 Production Series / Re: Kernel panics after upgrade to R1
« on: July 16, 2024, 08:43:04 pm »
I can also confirm this issue and also submitted a report

4
General Discussion / Re: Problem with DHCP Static Mappings
« on: February 18, 2022, 03:22:48 pm »
Just to add to the discussion, I'm having a similar but different problem. I migrated to opnsense recently so I'm new with it but I'm experiencing a weird issue. I'm trying the combined use of opnsense and pihole so decided to add another pihole in a sbc I had stored somewhere. Now comes the weird part, it was assigned a dynamic IP but I changed it to a static one outside my dynamic pool. Now I have 2 IPs for the same device (they don't appear both in leases) and I can ssh using any of the IPs. Also the pihole management page can be reached with both IPs. I tried to erase the dynamic IP in some places like "/var/dhcpd/var/db/dhcpd.leases" but it always comes back. I also tried to remove the static IP but the device still gets that IP even after reboot as I can reach it with through it. Probably because of this, if I set it as my only pihole it doesn't receive any hits and is bypassed.
I don't know what else to do (the sbc is running ubuntu 18.04).

Sent from my Redmi Note 8 using Tapatalk


Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2