rh1
Honorary Master
I am glad I am not a tech person, what I dont know cannot hurt me!

South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Your ISP will do some DDos protection if you are lucky, but securing your network is your responsibility.This weekend I spent a good couple of hours staring at my live firewall logs. What I saw was constant port scans from IPs all across the world (Bulgaria, America, Netherlands etc.) Not even scanning random ports, just going down the list like 39000, 39001, 39002 etc. I disconnected for a while to force a new IP address but that did not change, just the source IPs changed.
My firewall drops the packet, it doesn't block the packet (there is a difference).
My question is, should we just live with it and trust our CPE? Or should we be asking our ISPs to implement some algorithm to identify port scans and block them so that they can't even reach us?

or put something robust between that on your LAN/sStep one, is chuck the ISP supplied router
The router can still mess with your internet, inspect your traffic and participate in botnets using your connection.or put something robust between that on your LAN/s
But step zero should be disable UPnP and see if you can permanently damage it so it cannot be enabled again.
A standard home router is extremely unlikely to do proper inspection, especially on encrypted traffic. Most just do layer 4 filtering and DNS filteringThe router can still mess with your internet, inspect your traffic and participate in botnets using your connection.
Best to remove insecure devices entirely.
Once its part of a botnet, its no longer standard. Botnets will often send their own application binaries to leverage unimplemented features in the hardware.A standard home router is extremely unlikely to do proper inspection, especially on encrypted traffic. Most just do layer 4 filtering and DNS filtering
Some ISPs insist on the having their kit in the loop, which can be aggravating.Once its part of a botnet,
Ok I have used Opnsense for 5 years and before that PFSense for many years (10+). I think I am covered. Just commenting on the amount of port scanning. Mine looks like about 30% incoming is dropped.Your ISP will do some DDos protection if you are lucky, but securing your network is your responsibility.
Step one, is chuck the ISP supplied router in the bin and get something that actually gets its CVE's patched and does some reputation and signature based blocking. Most ISP supplied routers are insecure because they never get software updates and support from the manufacturers.
Ubiquiti gateways do a decent job of making it easy for the average person, but if you know what you are doing, you can get by with something cheaper running OpenWRT or a Mikrotik Router.
But this level of port scanning is normal, in todays age
View attachment 1927093
In the last 30 days, 6% of incoming traffic packets were dropped due to signature and reputation rules.
We're discussing the external interface.
Port forwarding is a NAT.
Is this confusing?
Weird. Deal with 3 distinct NOC teams on a daily basis and they are absolutely not, in any way, means or form, confused about this usage.Well then say port forwarding.
The default NAT (masquerade)has to exist.
You can’t not have it.
This is actually... not great. Unless there is an actual FW managing it.our VPN (Windscribe which has lots of protect tricks up its sleeve)
This is actually... not great. Unless there is an actual FW managing it.
VPN == Extension of trust and direct access to a network over which you have zero visibility or control.
I did extensive research on them and have chatted to support many times through the years, am convinced they're totally trustworthy and competent. They do all their own funding, have over 100 million registered users.
As for a firewall - there's one built into the desktop app, presume their servers are just as competent.
Great if that's the case. Using MTN's 4G fixed network.You are lucky though, in that you are using an LTE router you say? The default APN should give you some protection as the mobile operators tend to block incoming traffic by default.
I would have thought the created wide-use tunnel is then (largely) sealed and safe, thanks for this. I only let a few essential apps use the split tunneling option.The firewall you see in windscribe (I use them too) is to stop your traffic from defaulting leaking back on your non-vpn connection should something happen with your connection to windscribe. It does nothing more.

Sure, but you arent going to get full TLS inspection regardless. And if they try, it would be very noticeable from a user experience and performance perspective.Once its part of a botnet, its no longer standard. Botnets will often send their own application binaries to leverage unimplemented features in the hardware.
BTW do you know that Windscribe Pro includes settings for use on a router, if wantedbut your network itself still interfaces the internet at your router, your front door. Nothing that windscribe can do to protect you from incoming traffic at that door.
Routers use manual VPN configs rather than the app. Start with the WireGuard configuration generator, then import the downloaded config into your router’s VPN client section.
NAT is what's protecting his LAN from the port scans. They're hitting the router and being dropped. Source NAT/PAT is what allows multiple devices on your LAN to use a single external IP, you can't avoid it.Welcome to the internet
They are ALL out to get you. Behave appropriately.
DO NOT NAT, unless you have some working knowledge of what it is or what you're doing.