The mysterious lax31s19-in-x0a.1e100.net and www2.net.net
GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The mysterious lax31s19-in-x0a.1e100.net and www2.net.net
I ran tcpdump overnight. Nothing ran that connected to the Internet other than a single time check. In the morning I found 499 accesses by lax31s19-in-x0a.1e100.net (which resolves to 2607:f8b0:4007:818::200a by ping). 'whois' on this found nothing. A DDG search attributes it to Google. When I try to http-connect it gets redirected to www2.net.net, which won't let me browse because it detects an ad blocker, which I don't have, in both seamonkey and Firefox. Knows anyone about this?
Thanks. Firefox wasn't running. I wasn't browsing anything, was in bed. I don't browse YouTube. A whois on 1e100.net refers to markmonitor.com, which shows no obvious connection to Google. It uses Google's name servers, but I think lots of people do.
I'm using it now, but it requires specific addresses, not ranges.
Quote:
Originally Posted by frankbell
I also would recommend closing incoming ports in your router unless you have a positive need for them.
If that's possible I'll have to figure out how to do it. Many of these queries are zero-length queries to the https port. Since I'm not running a webserver they just get rejected. Most of the others are ICMP - I have to leave that on right? sendmail is listening, but I don't think I serve any other port. None of the queries are on 25.
There should be some way to log into your router and configure it. Check your router documentation.
As an aside, I just got a system "upgrade" from my ISP. As part of their "upgrade" they replaced my router with one of theirs (it has to do with the fact that they are also my cable provider, and their router is more compatible with their cable service, as now TV shows that I've "saved" for future viewing are now in their "cloud" and no longer on my cable box). I must say, their new router is much faster than my old one and the saved shows are working fine, but I still haven't figured out how to log into the router. But I will.
As regards iptables, take a serious look a ufw/gufw. They give you the capability of blocking incoming ports with a couple of commands.
Do you use it? I had to supply a slew of other stuff, 2 of which wouldn't build. Even if it does block a whole domain with millions of entries in iptables, I don't know I'd like that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.