<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:"times new roman",serif">It is a long shot but maybe...</div><div class="gmail_default"><font face="times new roman, serif"><a href="https://www.bbc.com/news/technology-44438812">https://www.bbc.com/news/technology-44438812</a></font><br></div><div class="gmail_default"><font face="times new roman, serif"><br></font></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 15, 2019 at 11:27 AM Robert G. Brown <<a href="mailto:rgb@phy.duke.edu">rgb@phy.duke.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 14 Jun 2019, Jonathan Engwall wrote:<br>
<br>
> Maybe I am not being clear. 192.168.0.5 was an intruder.<br>
<br>
Inside your private network? What kind of security are you using on<br>
your wireless access point inside your router (or your wireless enabled<br>
router)? The old encryption schemes can be cracked in literally a<br>
minute or two by somebody driving by in a car.<br>
<br>
Otherwise, a typical router won't pass packets from the outside to the<br>
inside unless you explicitly enable them, port by port.<br>
<br>
Finally, have you removed the default admin password to ensure that the<br>
modem/router cannot be logged into from the outside?<br>
<br>
rgb<br>
<br>
> <br>
> On Fri, Jun 14, 2019, 10:08 AM Jonathan Engwall<br>
> <<a href="mailto:engwalljonathanthereal@gmail.com" target="_blank">engwalljonathanthereal@gmail.com</a>> wrote:<br>
> I saw it yesterday. A nearly invisible VM connected at my login.<br>
> Whete do I go from there?I really don't know.<br>
> <br>
> On Fri, Jun 14, 2019, 9:54 AM Robert G. Brown <<a href="mailto:rgb@phy.duke.edu" target="_blank">rgb@phy.duke.edu</a>><br>
> wrote:<br>
> On Fri, 14 Jun 2019, Jonathan Engwall wrote:<br>
><br>
> > Robert Brown,You never saw this?<br>
><br>
> I did, and my extensive reply (which you apparently didn't<br>
> see, but<br>
> which is likely in the beowulf list archives?) basically<br>
> boils down to:<br>
><br>
> We need a LOT more information about your problem to be<br>
> able to help.<br>
> The nmap scan below doesn't really tell me anything at all<br>
> except that<br>
> yeah, some hosts are down.<br>
><br>
> Look in the archives and you can probably find it.<br>
><br>
> ? ? ?rgb<br>
><br>
> ><br>
> > On Sun, Jun 9, 2019, 1:41 PM Jonathan Engwall<br>
> > <<a href="mailto:engwalljonathanthereal@gmail.com" target="_blank">engwalljonathanthereal@gmail.com</a>> wrote:<br>
> >?? ? ?Hello Beowulf,<br>
> > Recently we had serious trouble with the internet. A<br>
> technician had to<br>
> > climb the pole. Another technician, an IT specialist in<br>
> Mexico City,<br>
> > could not resolve the issue, sent the man here.<br>
> > Now trouble is back. What does this mean? Where are the<br>
> missing IPs?<br>
> > From the pole to the modem, to my repeater, to my<br>
> machine, and then my<br>
> > VM gives this using nmap:<br>
> ><br>
> > Starting Nmap 6.40 ( <a href="http://nmap.org" rel="noreferrer" target="_blank">http://nmap.org</a> ) at 2019-06-09<br>
> 13:30 PDT<br>
> > Initiating Ping Scan at 13:30<br>
> > Scanning 256 hosts [2 ports/host]<br>
> > Completed Ping Scan at 13:31, 6.64s elapsed (256 total<br>
> hosts)<br>
> > Initiating Parallel DNS resolution of 256 hosts. at<br>
> 13:31<br>
> > Completed Parallel DNS resolution of 256 hosts. at<br>
> 13:31, 0.04s<br>
> > elapsed<br>
> > Nmap scan report for 192.168.0.0 [host down]<br>
> > Nmap scan report for 192.168.0.1<br>
> > Host is up (0.0080s latency).<br>
> > Nmap scan report for 192.168.0.2<br>
> > Host is up (0.00068s latency).<br>
> > Nmap scan report for 192.168.0.3 [host down]<br>
> > Nmap scan report for 192.168.0.4 [host down]<br>
> > Nmap scan report for 192.168.0.5<br>
> > Host is up (0.063s latency).<br>
> > Nmap scan report for 192.168.0.6<br>
> > Host is up (0.00068s latency).<br>
> > Nmap scan report for 192.168.0.7 [host down]<br>
> > Nmap scan report for 192.168.0.8 [host down]<br>
> > Nmap scan report for 192.168.0.9 [host down]<br>
> > Nmap scan report for 192.168.0.10 [host down]<br>
> > Nmap scan report for 192.168.0.11 [host down]<br>
> ><br>
> ><br>
> ><br>
><br>
> Robert G. Brown? ? ? ? ? ? ? ? ? ? ? ? <a href="http://www.phy.duke.edu/~rgb/" rel="noreferrer" target="_blank">http://www.phy.duke.edu/~rgb/</a><br>
> Duke University Dept. of Physics, Box 90305<br>
> Durham, N.C. 27708-0305<br>
> Phone: 1-919-660-2567? Fax: 919-660-2525? ?<br>
> ?<a href="mailto:email%3Argb@phy.duke.edu" target="_blank">email:rgb@phy.duke.edu</a><br>
> <br>
> <br>
> <br>
><br>
<br>
Robert G. Brown <a href="http://www.phy.duke.edu/~rgb/" rel="noreferrer" target="_blank">http://www.phy.duke.edu/~rgb/</a><br>
Duke University Dept. of Physics, Box 90305<br>
Durham, N.C. 27708-0305<br>
Phone: 1-919-660-2567 Fax: 919-660-2525 <a href="mailto:email%3Argb@phy.duke.edu" target="_blank">email:rgb@phy.duke.edu</a><br>
<br>
<br>
_______________________________________________<br>
Beowulf mailing list, <a href="mailto:Beowulf@beowulf.org" target="_blank">Beowulf@beowulf.org</a> sponsored by Penguin Computing<br>
To change your subscription (digest mode or unsubscribe) visit <a href="https://beowulf.org/cgi-bin/mailman/listinfo/beowulf" rel="noreferrer" target="_blank">https://beowulf.org/cgi-bin/mailman/listinfo/beowulf</a><br>
</blockquote></div>