[gopher] Gophernicus and seemingly random hits from localhost

James Mills prologic at shortcircuit.net.au
Sun Aug 27 22:14:20 UTC 2017


Is 192.168.0.100 also your Linux desktop? :)

If gophernisus is bound to the interface 192.168.0.100
then yes you're traffic will also be coming from this IP
but from some random src port.

:D

cheers
James


James Mills / prologic

E: prologic at shortcircuit.net.au
W: prologic.shortcircuit.net.au

On Sun, Aug 27, 2017 at 2:32 PM, Nathaniel Leveck <leveck at leveck.us> wrote:

> Since I know Kim is on here...
>
> My /var/log/daemon.log shows quite a few entries where single,
> nongophermap files are seemingly
> being requested by the server's internal network address (in my case
> 192.168.0.100). Is this
> normal? Am I in fact seeing outside requests? Am I subconsciously
> repeatedly sufing my own
> content and then blacking out?
>
> Example entry:
>
> Aug 27 15:09:58 rpod systemd[1]: Starting Gophernicus gopher server
> (192.168.0.100:49166)...
> Aug 27 15:09:58 rpod systemd[1]: Started Gophernicus gopher server (
> 192.168.0.100:49166).
> Aug 27 15:09:58 rpod in.gophernicus[5952]: request for "gopher://
> rpod.leveck.us:70/1/Textfiles/piracy/PRESTIGE/" from 192.168.0.100
>
> Curiously,
> Leveck
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20170827/c350fb80/attachment.html>


More information about the Gopher-Project mailing list