Deleting the bond0 has left one interface intact with the correct IP address. So I was able to use the secondary interface to test speeds directly. It seems pretty clear that pfsense is not the problem at all. Getting the same speeds directly with a laptop directly connected to the NAS. [image: 1639855781501-test.png] Iperf3 test shows network is not the problem. From Laptop to NAS iperf 3.6 Linux nas 4.4.180+ #42218 SMP Mon Oct 18 19:16:01 CST 2021 aarch64 ----------------------------------------------------------- Server listening on 4444 ----------------------------------------------------------- Time: Sat, 18 Dec 2021 19:33:48 GMT Accepted connection from 10.15.1.8, port 13951 Cookie: DESKTOP-VPJHHOI.1639856027.395816.51 TCP MSS: 0 (default) [ 5] local 10.15.1.7 port 4444 connected to 10.15.1.8 port 13952 Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 10 second test, tos 0 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 106 MBytes 889 Mbits/sec [ 5] 1.00-2.00 sec 111 MBytes 929 Mbits/sec [ 5] 2.00-3.00 sec 110 MBytes 922 Mbits/sec [ 5] 3.00-4.00 sec 111 MBytes 930 Mbits/sec [ 5] 4.00-5.00 sec 111 MBytes 933 Mbits/sec [ 5] 5.00-6.00 sec 110 MBytes 924 Mbits/sec [ 5] 6.00-7.00 sec 109 MBytes 913 Mbits/sec [ 5] 7.00-8.00 sec 110 MBytes 924 Mbits/sec [ 5] 8.00-9.00 sec 109 MBytes 917 Mbits/sec [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec [ 5] 10.00-10.03 sec 3.90 MBytes 944 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - Test Complete. Summary Results: [ ID] Interval Transfer Bitrate [ 5] (sender statistics not available) [ 5] 0.00-10.03 sec 1.08 GBytes 922 Mbits/sec receiver CPU Utilization: local/receiver 14.8% (0.6%u/14.1%s), remote/sender 0.0% (0.0%u/0.0%s) rcv_tcp_congestion cubic iperf 3.6 From NAS to Laptop iperf 3.6 Linux nas 4.4.180+ #42218 SMP Mon Oct 18 19:16:01 CST 2021 aarch64 Control connection MSS 1460 Time: Sat, 18 Dec 2021 19:35:02 GMT Connecting to host 10.15.1.8, port 4444 Cookie: yg6a4kxaczkaolqgasfxmaynim35ot3rbjro TCP MSS: 1460 (default) [ 5] local 10.15.1.7 port 32954 connected to 10.15.1.8 port 4444 Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 10 second test, tos 0 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 111 MBytes 934 Mbits/sec 0 211 KBytes [ 5] 1.00-2.00 sec 108 MBytes 903 Mbits/sec 0 211 KBytes [ 5] 2.00-3.00 sec 106 MBytes 887 Mbits/sec 0 211 KBytes [ 5] 3.00-4.00 sec 107 MBytes 900 Mbits/sec 0 211 KBytes [ 5] 4.00-5.00 sec 106 MBytes 891 Mbits/sec 0 211 KBytes [ 5] 5.00-6.00 sec 104 MBytes 870 Mbits/sec 0 211 KBytes [ 5] 6.00-7.00 sec 109 MBytes 911 Mbits/sec 0 211 KBytes [ 5] 7.00-8.00 sec 107 MBytes 895 Mbits/sec 0 211 KBytes [ 5] 8.00-9.00 sec 107 MBytes 901 Mbits/sec 0 211 KBytes [ 5] 9.00-10.00 sec 107 MBytes 900 Mbits/sec 0 211 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - Test Complete. Summary Results: [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.05 GBytes 899 Mbits/sec 0 sender [ 5] 0.00-10.00 sec 1.05 GBytes 899 Mbits/sec receiver CPU Utilization: local/sender 5.7% (0.4%u/5.3%s), remote/receiver 13.4% (6.5%u/6.9%s) snd_tcp_congestion cubic iperf Done.

@patch Problem Solved. It was a problem with my MacBook. I created a new profile on my MacBook and that one works fine. So there is issue with the network setup on my other profile. Anyway, Thank you so much for everyones help and advice. It has only strengthened my feelings about PFSense being a good choice.

Hmm, well that's good news, it implies the TB 10G adapter is not the cause so probably can be made to work. Unless you have some traffic shaping set in pfSense it's hard to see what might cause that. Something in Windows guess though I'm not sure what. Steve

@jt40 said in Sky modem replacement - MK2 socket: this is one of the suggested as replacement which supports Sky MER: TP-Link AC2100 - Archer VR2100 That's also a router (with a built in modem) not a modem. An actual modem is something like the Draytek V130 or Huawei HG612. I am in the UK but, alas, not yet in a FTTH area. If you upgrade to FTTH you still need a modem of sorts. The connection is provided via GPON so you get an ONT box that converts that to Ethernet you can plug pfSense into. Steve

@stephenw10 Thanks Steve, I can put my mind to rest now!

@gertjan I suspected that, then it's probably easier to "browse" it with a backend browser - get the data needed and present it again - at the "other" server.

It's the ntopng that became a troublemaker. I'm worry free now after turning off ntopng! I will figure out how to wipe this ntopng and install a fresh one. I looked at the crontab and nothing looked suspicious. Thanks you all for all the directions.

@dnwigley did you setup the switch to route between different networks you put these devices on? Did you setup any sort of multicast filtering? If you put the devices on the same L2 network.. Most switches wouldn't be do any filtering either. I think your going down some rabbit hole trying to blame it on something filtering something. If you discovered the other nas - and get presented to auth.. This pretty much shows your talking to it.. And highly unlikely your fitering some aspect of the auth process at your switch. You mention access to the DSM interface - how exactly are your trying to access that.. You should be able to access the dsm on port 5001.. Are you using some name that resolves to public IP vs your local one?

@work_purposes_only said in openBGPD and FFR - Migrating 2.3.x to Latest 2.5.x: @nollipfsense I've just inherited this network. So, I'll be taking this next year to tidy it up before going back to uni for my degree Okay...fine inheritance...hope it came loaded (your forum name implied business).

When you connected the PC directly to Eth1 did it show the expected link speed/duplex? 40Mbps is sufficiently slow to point to a link issue. Steve

@stephenw10 I forgot the first step: Always check the cables.

@hulleyrob Or maybe https://en.wikipedia.org/wiki/RRD_Editor Btw : I never had the need myself, or, by memory, didn't saw some one mentioning on the forum, actually modifying them, to retrieve history data. Also; I back up most of the RRD history data : https://www dot test-domaine dot fr/munin/brit-hotel-fumel dot net/pfsense.brit-hotel-fumel dot net/index.html

Yes, you can 'alternate host names' in Sys > Adv > Admin Access that the referer check will then accept. Steve

@Patch @stephenw10 Thanks for your help! Replacing the switch fixed the issue! I factory reset the TP Link managed switch and it's working now too. It's sometimes the simple stuff you over look on the troubleshooting path that trip you up. I could not determine any reason why the TP Link managed switch was preventing the Proxmox GUI from coming up. I checked everything before I reset it. Thanks again!

Hmm, I don't think I've ever tried to do that! You're right it doesn't ask if you want to enable https after setting the interface IP. I wouldn't call that a bug though, an oversight maybe but that's the intended operation. You can always set it in the config file if you really need to enable it before you have access to the webgui. You can open a feature request: https://redmine.pfsense.org/ Steve

@jhonthan said in DDNS doesn't work on version 2.5.2: DDNS doesn't work on version 2.5.2 Anyone saw this problem? No, DDNS works fine. Keep in mind that the "DynDNS" facility build in pFSense uses : /* * PHP.updateDNS (pfSense version) * * +====================================================+ * Services Supported: * - DynDns (dyndns.org) [dynamic, static, custom] * - No-IP (no-ip.com) * - EasyDNS (easydns.com) * - EasyDNS IPv6 (easydns.com) * - DHS (www.dhs.org) * - HN (hn.org) -- incomplete checking! * - DynS (dyns.org) * - ZoneEdit (zoneedit.com) * - FreeDNS API v1 (freedns.afraid.org) * - FreeDNS IPv6 API v1 (freedns.afraid.org) * - FreeDNS API v2 (freedns.afraid.org) * - FreeDNS IPv6 API v2 (freedns.afraid.org) * - Loopia (loopia.se) * - StaticCling (staticcling.org) * - DNSexit (dnsexit.com) * - OpenDNS (opendns.com) * - Namecheap (namecheap.com) * - HE.net (dns.he.net) * - HE.net IPv6 (dns.he.net) * - HE.net Tunnelbroker IP update (ipv4.tunnelbroker.net) * - SelfHost (selfhost.de) * - Amazon Route 53 (aws.amazon.com) * - DNS-O-Matic (dnsomatic.com) * - Custom DDNS (any URL) * - Custom DDNS IPv6 (any URL) * - Cloudflare (www.cloudflare.com) * - Cloudflare IPv6 (www.cloudflare.com) * - Eurodns (eurodns.com) * - Gandi LiveDNS (www.gandi.net) * - GratisDNS (gratisdns.dk) * - City Network (citynetwork.se) * - GleSYS (glesys.com) * - DNSimple (dnsimple.com) * - Google Domains (domains.google.com) * - DNS Made Easy (www.dnsmadeeasy.com) * - SPDYN (spdyn.de) * - SPDYN IPv6 (spdyn.de) * - All-Inkl (all-inkl.com) * - DuiaDNS (www.duiadns.net) * - DuiaDNS IPv6 (www.duiadns.net) * - Hover (www.hover.com) * - DreamHost DNS (www.dreamhost.com) * - ClouDNS (www.cloudns.net) * - GoDaddy (www.godaddy.com) * - Azure DNS (azure.microsoft.com) * - Dynv6 (www.dynv6.com) */ Just recently, last week or so, OpenDNS broke their server side app. That's repaired now. Namecheap has issues right now - see recent threads about namecheap. no-ip has regularly ( ? ) problems ...

@gertjan yes, I checked yesterday and it's also fixed for me. Thanks!

@aglarond You will find many a post by me going over transit networks ;) have to explain it like every other day it seems ;) Users are always trying to use their normal lan as transit and then wonder why they run into asymmetrical issues. Here is a good drawing that explains what has to be down with a downstream router. [image: 1639335337947-pfsense-layer-3-switch.png]

@stephenw10 Thank you very much for the reply. I searched, but couldn't phrase my question properly to find that.