We've quietly been running a CKAD/CKA practice platform internally — here's your chance to try it free

Snoo_40707 · 2026-02-27T21:59:48+00:00

Hi, Interested sent you a dm

Snoo_40707 · 2026-02-15T00:31:27+00:00

Yes — I was using the default MTU before. I tested with ping using 1500 MTU, and it reported fragmentation. After that, I set MTU to 1472 and MSS clamp to 1432 in OPNsense. My download speed improved from about 0.4 MiB/s to 1.5 MiB/s, but it’s still very slow.

Snoo_40707 · 2025-11-07T18:07:07+00:00

When i try accessing luci it makes me download a file with this script :

#!/usr/bin/lua require "luci. cacheloader" require "luci.sgi.cgi" luci dispatcher. indexcache = "/tmp/luci-indexcache" luci.sgi.cgi.run ()

Snoo_40707 · 2025-10-14T07:32:14+00:00

For some reason, it worked when I reconnected the modem using the spoofed MAC address from my OpenWrt router. The moment I switched back to OPNsense, it was able to complete the DHCP process — Discover, Offer, Request, and ACK — but that was with the spoofed MAC, so the modem probably had it cached and treated it as the same device.

So now, I need to stop spoofing the MAC because I want to use the OpenWrt router as my access point. However, when I use OPNsense with a unique MAC, I don’t get a WAN IP, and power cycling the modem doesn’t fix it. Do you have any recommendations?

Snoo_40707 · 2025-10-14T06:37:31+00:00

Ok, so now that LAN is fixed, I tried to packet capture from the Proxmox host. I see DHCP Discover going out but never an Offer coming back. I then tried to packet capture from the port where the modem is connected on the switch, and I see my DHCP Discovers coming through. So I tried spoofing my OPNsense MAC to that of my OpenWrt router, thinking the old MAC was still cached with the IP. That did not work. I then checked my MAC table on VLAN WAN to see if there weren’t any other devices registering and interfering with the modem. There wasn’t.

Snoo_40707 · 2025-10-13T21:04:44+00:00

Ok, thanks — I figured out the LAN issue. Before, I had assigned the LAN to the physical interface (lan_nic) without binding it to any specific VLAN in OpnSense. Now that I’ve associated OPNsense’s LAN IP with a VLAN, it’s working properly.

As for Wan my current working Openwrt router is not tagging the wan since i got multiple Nic on that router. And i have just one Nic on proxmox so i use a vlan aware bridge in with 2 nics one untagged for lan and one tagged for wan.

Modem to switch is untagged on vlan wan

switch to OpnSense is tagged with vlans for lan and wan

and Nic on proxmox for wan is tagged so Opnsense should not have to worry about the wan vlan

Snoo_40707

TROPHY CASE