Call for testing: netmap on 20.7

[franco]

Kernels in the major version category always work interchangeably. But to be sure the latest code is tested I'm going to create a 20.7.6-next variant. Maybe after 21.1 is out we should work on a -devel type kernel track to avoid confusion and always upgrade to the new kernel if it is available.


Cheers,
Franco

[franco]

20.7.6-next is now available both in kernel (-k) and base set (-b).


Cheers,
Franco

[allebone]

Is there an update on pppoe support at all?

[franco]

Not that I know of, no.


Cheers,
Franco

[jbohbot]

I'm having some issues with LAGG on my LAN connection. It will just crash my LAN once I finish the install/wizard. I have searched this thread and a user has mentioned that instead of using the LAGG as the interface they used the 2 ports. In my case this would be ix0/1 connecting to my cisco switch.

I have 2 questions about doing this:
1, Doing what the user has done, would it be more taxing on the box and would it even work for protecting the network?
2, Do we have some kind of ETA as to when the next netmap will support LAGG interfaces?

For the moment I re-installed my opnsense and restored from a backup from before I installed Sensei since I was not even able to access my box from the LAN. I will be waiting before installing this again.

Thank you,
Jonathan

[klamath]

@franco

I am no longer able to downgrade to a fixed kernel on 2.7.8, I just upgraded from 2.7.5 to 2.7.8 and now getting this error message when trying to get the fixed kernel in place.

root@cerberus:~ # opnsense-update -kr 20.7.6-next
Fetching kernel-20.7.6-next-amd64.txz: .. failed, no signature found
root@cerberus:~ # opnsense-update -kr 20.7.4-next
Fetching kernel-20.7.4-next-amd64.txz: .. failed, no signature found

Thanks,
Tim

There is a new test kernel available, mostly for ix/ixl performance issues in iflib/netmap:

# opnsense-update -kr 20.7.4-next
# opnsense-shell reboot

You can see the relevant batch of new commits on the master branch[2].


Cheers,
Franco

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248652
[2] https://github.com/opnsense/src/commits/master

[franco]

The next kernels were temporary kernels that largely resemble 21.1 kernels. There is no reason to keep them around.


Cheers,
Franco

[klamath]

Can I upgrade the kernel on 20.7 to 21.1 to get the netmap and intel driver fixes without upgrading the OS to 21.1?

[klamath]

I will need to force an upgrade to 21.1 it seems to get the fixed kernel.

root@cerberus:~ # opnsense-update -zkr 21.1
Fetching kernel-21.1-amd64.txz: ... failed, no signature found
root@cerberus:~ # opnsense-update -kr 21.1
Fetching kernel-21.1-amd64.txz: ............ failed, signature invalid

[franco]

Any other version than 20.7.8_4 does not have the signature fingerprint for 21.1.. I'm not sure why you are not on this version. ;)

There is the "-i" parameter to do insecure upgrades, but it's nicer to not use it and use the latest 20.7 release with:

# opnsense-update -kr 21.1
# opnsense-shell reboot


Cheers,
Franco

[klamath]

I am running the business version of opnsense, I recently did the upgrade from 20.7.5 to 20.7.8 and allowed the kernel to get upgraded, after the upgrade my setup was running at a capped speed with IDS/IPS enabled.  Having the -next kernel branch available would have saved me another upgrade to 21.1 tonight.   

Any other version than 20.7.8_4 does not have the signature fingerprint for 21.1.. I'm not sure why you are not on this version. ;)

There is the "-i" parameter to do insecure upgrades, but it's nicer to not use it and use the latest 20.7 release with:

# opnsense-update -kr 21.1
# opnsense-shell reboot


Cheers,
Franco