brent saner via plug on 14 May 2024 09:42:20 -0700


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Network question


On Tue, May 14, 2024, 10:34 Steven Grunza via plug <plug@lists.phillylinux.org> wrote:
Am I correct in assuming all of these seemingly random TCP connection attempts are attempts to hack into my network?  

They're all SYNs from the looks of it, so could be, but it's unlikely it's targeted. Stuff is scanning all the time. It's not really easy to say one way or another without knowing what dest ports, what they're doing on the wire, etc.


The destination address is my DMZ machine.  I tried using Port Forwarding but it didn't work so I am trying DMZ (basically forward everything to a particular machine).

I was able to ssh from a remote machine into my network for about two days before I started getting "no response" messages (I forget the exact message).

That'd be Comcast. It's unlikely inbound ssh will work for you again for as long as you use them, at least with that IP lease.


I was able to see that while I was trying to connect, there were not packets from the remote network machine I was using, just all this junk.

Yep.


I really don't want to pay for both home Internet access and AWS services just to host a MQTT-SN / MQTT broker but it's looking like I might need to give up on Comcast being able to provide outside network access to my server.

Honestly, I admire your optimism in thinking this would work long-term with Comcast. Verizon is not much better. The smaller/local ISPs, if available, are better about it but can sometimes be pricier. 

Avoid AWS for this. Get a flat-rate per-month VPS.
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug