If they are being given IPs from the LAN subnet then their DHCP broadcasts are hitting LAN. Something is bridging the LAN and VLAN9.

Ah, never saw that setting before .

Changing Top Navigation to Scrolls with page fixed it.

Thanks!

Screenshot_20231209-105143.png

It appears this update enabled a dual monitor feature. It does not occur in the previous version.

@jrey said in Danger, Latency on WAN mildly loaded:

Marking it as always up hides the when it really down.

Before doing that, I would make sure shaping is properly set up. Follow this guide to set up CoDel.

NB: Waveform can be inaccurate with high bandwidth connections. Balance it against another test like Speedtest. Speedtest doesn't give you a grade like Waveform, but it does give averages under load.

@yaboijersh said in DHCP Server not showing additonal boot options for PXE BOOT:

Thanks for the help!

Glad I could help!

Opened a feature request: https://redmine.pfsense.org/issues/15078

@jimp

That was the issue. I found a post that said to use ctl-a d (looking now that says to disconnect) not to kill the session like ctl-a \ does). Once I cleaned up all the screen connections, I was able to get in and have changed the way I connect and disconnect. Thank you very much!!!

:~# screen -ls
There are screens on:
2554.pts-0.computer (11/27/2023 07:35:26 AM) (Detached)
2552.pts-0.computer (11/27/2023 07:35:06 AM) (Detached)
2550.pts-0.computer (11/27/2023 07:34:38 AM) (Detached)
2547.pts-0.computer (11/27/2023 07:34:18 AM) (Detached)
2544.pts-0.computer (11/27/2023 07:33:41 AM) (Detached)
2514.pts-0.computer (11/27/2023 07:12:56 AM) (Detached)
2511.pts-0.computer (11/27/2023 07:12:27 AM) (Detached)
2508.pts-0.computer (11/27/2023 07:11:44 AM) (Detached)
1616.pts-1.computer (11/26/2023 08:11:02 PM) (Detached)
1612.pts-1.computer (11/26/2023 08:10:05 PM) (Detached)
10 Sockets in /run/screen/S-root.

@stephenw10 I have good news and I have bad news. The good news is that I got everything working. The bad news is I don't know what I did. LOL

Thanks for your help. I did check out the things you mentioned and I must have accidentally changed something. If I figure it out, I will post what I think I did.

@stephenw10

This worked like a charm! Thank you very much!

@emmaylots was having the same issue and can confirm that it works. Thank you!

I can confirm that the switches on the router mr8300 (or the router hardware itself) appear to be what is the cause behind the slowness when hardwired.

My first guess would be something stored in a saved login. Try using a private window in Firefox.

Huh, good to know. Thanks for the update!

Are the clients assigned interfaces? I would certainly expect to see those via the correct clients.

Do you see the gateways on the correct clients?

@johnpoz said in Static ARP Mapping:

So in general there is quite a bit of stuff going on with dhcp in general - also the move to kea version not supporting all features, etc. etc. I would hope they have all the issues worked out by next release.

I found out that it was really kea dhcp not letting go of leases that was the culprit. I have gotten rid of the static mapping.

@iSagen

Now it works! I had some NAT-rules ruining my setup. Deleted them and now it works.

:)

So it turned out that even under the leases section of the menu the old wifi router was listed as offline and inaccessible. I finally tried clearing my browser's history which did allow the browser to connect but there was a server error on the page. I then downloaded the new app that didn't exist when I bought the old router from Netgate back in 2015 and tried to use it to connect wirelessly to it after having reset it to factory settings. This was able to wake up the router I guess because I was able to access it through the browser finally, after having disconnected the pfsense router. I then set the old router to AP mode and it asked me to hook up the new pfsense router to the internet and then attach the new router to the old one and it worked. Thanks for everyone's help today. I really appreciate it. I guess I should have been using the dumb phone app for the old router a lot sooner but even a couple of months ago it was unnecessary. What a day lol

Well in that pcap it's just responding to Syn with Reset so it's refusing the connection anyway.

What interface is it using for replies though? How does in the state table?

Check the MAC address replies from the DC is using as destination. Is it actually sending them to the correct gateway to go back over the VPN?

What does the routing table on the DC look like?

That was just the reporter. Not sure why it was set to that. Added a target version.

On a hunch, I swapped the modem for one of the same model from my ISP. Problem is solved & I have GUI access once again. Chalking it up to coincidence with the modem failing at the same time NIC was replaced.

Thanks to everyone for your assistance.