Recent posts

#1

26.7 Series / Re: No Web_GUI if LAN is DHCP ...

Last post by ednt - Today at 06:36:59 PM

Yes, of course, I set it to only listen on LAN.

#2

26.7 Series / os-frr: no route map for redis...

Last post by ednt - Today at 06:35:28 PM

AI mentioned that I should set a route map in the section RIP for redistribution bgp:

router rip
 default-metric 5
 network x.x.x.x/24
 passive-interface vlan0.x
 passive-interface vlan0.y
 passive-interface vlan0.z
 redistribute bgp
 version 2
exit

-> redistribute bgp route-map Only_Default

Else all routes of the internet will flood the internal routers.

But I can not set a route-map in the RIP menue.

Is the AI corect?
How canI achieve this entry?

#3

26.7 Series / Re: Upgrade 26.1 -> 26.7 faile...

Last post by rocketraman - Today at 06:18:47 PM

Same issue here, upgrade borked on "waiting for configd". Rebooting, uninstalling the Intel CPU Microcode plugin, and then running the upgrade again worked. Surprised this wasn't handled automatically.

#4

26.7 Series / Re: Performance Issues on 26.7...

Last post by dg6464 - Today at 05:03:10 PM

Just curious what sort of configuration you have for tunables if you can be more specific for the X520 or X710?

I haven't enabled the Microcode plugin stuff, as I've seen most people removing it or disabling recently.

Just following ChatGPT guidance and the fact that my previous configuration and setup on older versions was rock solid and performant.

So unless there has been a change in the way OPNsense uses the hardware or drivers in a major way... I'm not sure the tunables and such should make a difference if I haven't changed them in years.

But I am happy to follow any specified best practices and troubleshooting steps for Intel X520 or X710 configuration tunables and CPU microcode.

The one factor I do want to verify is if you are running PPPoE on your OPNsense setup... as that has been a reason for historical performance grief as FreeBSD has changed over time.

Any guidance or links you recommend are appreciated.

Happy to provide configuration details or snippets if it will help.

Thanks!

#5

26.7 Series / Re: Multiple VLANs - sometimes...

Last post by gpb - Today at 04:15:40 PM

While I've had 2 of these for many years, I added another a couple months ago.  My f/w is current - TL-SG108E 6.0/1.0.0 Build 20230218 Rel.50633.

#6

26.7 Series / Re: Multiple VLANs - sometimes...

Last post by nero355 - Today at 04:03:24 PM

I finally made the first part! Which means I got my brain working with PVID and UNTAGGED etc.
AP is fully working now. One switch works... yeah, this part is done.

Thank you @nero355 & viragomann for all the hints/help! That was really helpful =)

On Sunday will be the swap with the openwrt main router and then I've to check the other switches, proxmox and whatnot.

w00t w00t !!! NICE! :D

I'll be back ;)

OK Arnold :P

I didn't read all the above, but one note about that switch.

Do not use DHCP for the IP address assignment of the switch itself, just put in a static address.  Reason...sometimes the switch will get an IP address from one of the other VLANs.  I spent some time on this and it appears it sends a DHCP request on all VLANs and which ever answers first wins.

So it may seem to work, but sometimes when it renews its address it might change.  Just an FYI.  I have a few of these and they are set and forget, otherwise.

I have read about some weird issues with the TP-Link 105/108 E and PE models in the past, but a lot of those issues were fixed via either new Revisions or simply Firmware Updates so it would be nice to know which combination you have at the moment for future reference :)

#7

26.7 Series / Re: "old" rules show up in "Ru...

Last post by nero355 - Today at 03:59:09 PM

I am slightly confused right now.

I think a lot of people would be less confused if they would just keep an eye on the Release Notes carefully each time there is an update/upgrade and in this case perhaps also at least only read the Migration Assistant part that's related to the Firewall Rules migration :)

Not saying you didn't or that there are no confusing parts about this, but IMHO there would be at least a certain amount of less confusion if more people did that...

#8

General Discussion / Re: Roku DNS storm is impactin...

Last post by Monviech (Cedrik) - Today at 03:55:43 PM

You could try the new rate limits of pf out to limit how many pakets the Roku could send the opnsense dns port.

https://github.com/opnsense/core/commit/80f4affed7074a1095a3ffabe98419af2d4498af

#9

General Discussion / Re: Roku DNS storm is impactin...

Last post by nero355 - Today at 03:48:33 PM

I may need to break down and install a standalone DNS there to get this load off of OPNsense.

You could ofcourse give it a small dedicated DNS Server running on a Raspberry Pi 2B/3B or perhaps even a Pi Zero and keep everything else as is :)

What a horrible device by the way...

Has anyone ever complained about this via Roku Support or something like that ?!
That amount of DNS Requests from such a small shitty device is just INSANE!!! :(

#10

26.7 Series / Re: Multiple VLANs - sometimes...

Last post by gpb - Today at 03:30:33 PM

I didn't read all the above, but one note about that switch.  Do not use DHCP for the IP address assignment of the switch itself, just put in a static address.  Reason...sometimes the switch will get an IP address from one of the other VLANs.  I spent some time on this and it appears it sends a DHCP request on all VLANs and which ever answers first wins.  So it may seem to work, but sometimes when it renews its address it might change.  Just an FYI.  I have a few of these and they are set and forget, otherwise.