Quote from: odites999 on Today at 02:40:05 PMmy provider is Movistar in Spain.Is there a chance that you could get kicked into a CG-NAT segment of their network after rebooting your Router ??
Quote from: francescofff on Today at 09:39:58 AMI bought a TopTon mini-PC with an Intel N150 (Alderlake ULX) quad-cores processor and Intel i226-v Ethernet cards.Please note that those NICs sometimes need a firmware update in order to function properly : https://forum.opnsense.org/index.php?topic=48695.0
QuoteMy internet service provider is currently Proximus Fiber with 500 Mbps download and upload speeds.- DHCP WAN or PPPoE ??
QuoteIf I connect my PC directly to the Proximus box, I get the correct speed.Proximus Box = Modem/Router in NAT Mode or Bridged Mode ??
QuoteI tried disabling hardware checksum offload, hardware TCP segmentation offload, and hardware large receive offload, but nothing changed. I also disabled ASPM in the BIOS. I added a few tunables in OPNsense. But still nothing.I believe it's recommended to have all of those disabled anyway.
QuoteAs a last resort, I booted Linux Mint in Live Session mode from a USB drive, and there I got a speed of 500 Mbps.You could have tried FreeBSD 14.x instead to be as equal to OPNsense as possible ;)
QuoteI don't understand why I'm being throttled as soon as I install OPNsense.My TopTon with less CPU and i225 NICs does all of this without any issue and so should yours!
I thought it was a powerful tool, but I can't even achieve a decent speed.
Quote from: franco on Today at 08:55:35 AMNot at the moment. It's on my wishlist for the next nano images, but it hasn't been discussed internally yet.Oww... OK... I misunderstood then...
Quote from: drosophila on Today at 01:49:46 AMHehe, looks like you didn't buy the Venus to show it off, given that I can barely make it out behind all those fans and heatsinks! :DI just had a lot of storage for that time and it was mostly used for gaming :)
Was that a NAS with all those harddrives?
QuoteHmm, Marvell was one but the other was a Vitesse PHY that was fed from the nForce4 and thus would likely also have used the nVidia PXE boot... I think it used the "forcedeth" driver, anyway. Oh well. :)IIRC driver-wise there was not much difference between the two NICs in Windows at least...
QuoteBTT: I believe I've found the problem: the nVidia boot agent seems to terminate the boot file name with some illegal character, or rather, with something while there shouldn't be anything there. The server log viewer would show just two blank lines (which is a bug in the server GUI...), but its syslog shows this:Would it be an option to have a dedicated PXE Boot VLAN on your network ?RRQ from x.x.x.x filename /pxelinux.0<FF>The working Realtek boot agents send the same request but without the postfixed "<FF>" (which probably translates to a single byte of all ones). Obviously that should not be there but now the question is: why does it work with udhcpd and Dnsmasq, just not with KEA? Is it possible that KEA incorrectly sends this but Realtek just discards it while nVidia keeps it? Or could this be a config problem?
I seem to recall that 0xff is the UTF-8 "continuation" marker, but even if that is correct that still doesn't explain why it's there.
Quote from: Residence0886 on Today at 02:48:14 PMSo I created a new firewall rule on the transfer-LAN adapter that covers all traffic and set it on top of the list. Source is my test-client and destination is any.You have to add this rule to the LAN interface. But maybe, that's just a typo.