D1NZ

Home fibre too

Maybe have a look your router, this more and more sounded like it's bottleneck out at router. Make sure your router can do 1Gbps from the spec search. Also an ONT = Modem for fibre, behide ONT usually it's Router.

pfSense it's running based on FreeBSD 10.1 for current version which also means whatever hardware driver FreeBSD 10.1 support it's being ported over to pfSense. check here for the Hardware list:- https://www.freebsd.org/releases/10.1R/hardware.html And do a hardware "chipset" search on that page, e.g. "Intel i82586" for one type of the NIC. Here is my box hardware list:- Intel Xeon E3-1225 V2 @ 3.20GhzIntel S1200KPR server board mini-ITXA-data ECC 4GB x 2 1600MHzIntel Ethernet Server Adapter I350-T2 This box has been running for few years now with zero issue with latest version of pfSense.

There are some people have got it working by going back from Magician 4.6 to 4.4 Problem with 4.6 is it doesn't recognise correct OS.

if your line it's stable enough and copper quality up to par and you on xDSL you can looking into interleaving, normally ISP will have interleaving enable by default. You can look into it and turn it off, you might lost a little speed but ping will be hell alot better.

Please also check if Windows Firewall have VNC in the allow list and ticked.

my experience with pfSense I learned, always check if your on-board NIC chip is supported by current BSD vserion used by pfSense e.g. current version using FreeBSD 10.1 so https://www.freebsd.org/releases/10.1R/hardware.html You will have a better idea for what hardware to use or not to use, and yes if you want to stick with pfSense just pick up some cheap intel NIC that are supported from eBay or Amazon That aside, for auto detect interface you need to plug eth cable into the port on PC from switch/router while in auto select. Also with some googleing your board only have 1 NIC on-board, it just wouldn't work unless you running both WAN and LAN on 1 x RJ45 port and separate them by VLAN.

wired solution would be the best way to go but not always possible. if it's not possible I would look into directional wireless antenna if you have a good light of sight of each building. some of those directional antenna are rated like 30km or so, but that's way too over kill. have a look products like Ubiquiti NanoStation 200mW one are rated at 1km+, and 500mW one are going to be at 15km+ and they are fairly cheap in team of price.

few months away from NBN, prolly not worth doing it unless you want to setup something like fallover on your copper line. anyhow I will stop giving you ideas, good luck.

How old is your router? if everything checks out above from what other have said, I would suggest you maybe try a new modem/router.

if you gonna be sticking with copper line, I would suggest get a master filter installed, the reason being:- 1. xDSL filters in house can be faulty, and it's gonna be a pain to find out which if you have lots around the house. 2. each filter actually adding noise to your copper line, so master filter will keep it down to just one filter. Not sure about in Australia but in New Zealand all install of copper line are required a master filter now. it look something like this:-

There is few more information needed, before useful advice being given. 1. are you going to have WiFi device on different VLAN? which separate from your wired devices. 2. what are those extra room used for? renting out to other ppl?

Sounds like you are getting DDOSed and if your line is dynamic reboot your modem & router will get your a new ip which fix the problem. But if the person who is DDOSing your got your IP address again, than you shit out of luck and will need reboot everything again.

Linux box - Smokeping Windows - PingPlotter (has free and paid version)

Network stability prolly could be done putting your network under load? a simple program could do this is iperf, and have few of them running from different PC or laptop so on.

Because of how range extender work, you will likely only get half of what you are running now. Running a wire it's my best bet but not always possible. But if wire like Cat5 or Cat6 it's not possible maybe try eth over powerline.

That's pretty much everything you could do, next I would look into your router firmware see if there is a port forwarding issues or bugs. First try updating the firmware. If that still not working I would try completely different router.

Maybe try turn off DMZ and troubleshoot one thing at a time.

also check if your ISP is blocking any of those ports to be used.

if you on xDSL line, I would give your ISP a call and check to see if they can turn your interleaving off. with interleaving turned off you might have a less stable line but you will have a lower ping. interleaving it's like error correction with xDSL line, google it if you want to know more.

Firstly check your xDSL line stats page, from that we will know what's your line quality like or even your rough distance from your ETP to your exchange.

from New Zealand with fibre @ home