[LUNA] Ping Reply question
Michael W. Hall
hallmw at att.net
Fri Sep 5 19:53:56 CDT 2014
Any idea what file you would edit to fix that?
On Thu, 2014-09-04 at 18:50 -0500, Branden Harper wrote:
> There you go. There is a dns server on your local system replying with
> that name.
> On Sep 4, 2014 6:29 PM, "Michael W. Hall" <hallmw at att.net> wrote:
>
> > I never thought to do that. Here are the results.
> > hallmw at Tardis:~$ ping jack
> > PING jack.gateway.2wire.net (192.168.1.78) 56(84) bytes of data.
> > 64 bytes from jack (192.168.1.78): icmp_seq=1 ttl=64 time=0.049 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=2 ttl=64 time=0.022 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=3 ttl=64 time=0.067 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=4 ttl=64 time=0.059 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=5 ttl=64 time=0.050 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=6 ttl=64 time=0.059 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=7 ttl=64 time=0.060 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=8 ttl=64 time=0.029 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=9 ttl=64 time=0.028 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=10 ttl=64 time=0.051 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=11 ttl=64 time=0.043 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=12 ttl=64 time=0.058 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=13 ttl=64 time=0.063 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=14 ttl=64 time=0.059 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=15 ttl=64 time=0.034 ms
> > 64 bytes from jack (192.168.1.78): icmp_seq=16 ttl=64 time=0.059 ms
> > ^C
> > --- jack.gateway.2wire.net ping statistics ---
> > 16 packets transmitted, 16 received, 0% packet loss, time 15001ms
> > rtt min/avg/max/mdev = 0.022/0.049/0.067/0.014 ms
> > hallmw at Tardis:~$ nslookup 192.168.1.78
> > Server: 127.0.1.1
> > Address: 127.0.1.1#53
> >
> > 78.1.168.192.in-addr.arpa name = jack.
> >
> >
> > On Thu, 2014-09-04 at 11:25 -0500, Branden Harper wrote:
> > > If you do a ping to 'jack' does it work correctly? Have you tried
> > > `nslookup jack' and `nslookup 192.168.1.78' ?
> > >
> > > Just a couple of things I thought of today.
> > >
> > >
> > > On Wed, Sep 3, 2014 at 8:59 PM, Michael W. Hall <hallmw at att.net> wrote:
> > >
> > > > After I upgraded to Ubuntu 14.04 LTS, I ssh into my desktop. I then
> > > > pinged my laptop to see if the reply would say tardis. Below are the
> > > > results. Not sure where the jack is coming from, but one reply did say
> > > > Tardis.
> > > >
> > > > mwhall at TAZ:~$ ping tardis
> > > > PING tardis.gateway.2wire.net (192.168.1.78) 56(84) bytes of data.
> > > > 64 bytes from jack (192.168.1.78): icmp_req=1 ttl=64 time=8.31 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=2 ttl=64 time=13.0 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=3 ttl=64 time=34.4 ms
> > > > 64 bytes from Tardis.local (192.168.1.78): icmp_req=4 ttl=64 time=11.1
> > > > ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=6 ttl=64 time=4.25 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=7 ttl=64 time=6.17 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=8 ttl=64 time=7.28 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=9 ttl=64 time=3.14 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=10 ttl=64 time=2.92 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=11 ttl=64 time=3.52 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=12 ttl=64 time=4.16 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=13 ttl=64 time=2.39 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=14 ttl=64 time=3.17 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=15 ttl=64 time=5.75 ms
> > > > 64 bytes from jack (192.168.1.78): icmp_req=16 ttl=64 time=3.03 ms
> > > >
> > > > On Thu, 2014-08-14 at 17:14 -0500, Michael W. Hall wrote:
> > > > > My bad Bob. Laziness on my part. It is short for Raspberry Pi. The
> > > > > little computer. They are awesome.
> > > > >
> > > > > On Thu, 2014-08-14 at 01:22 +0000, Bob Nance wrote:
> > > > > > I’m afraid I don’t know what RPi is, but I would get it’s a remote
> > > > ping server. If it reporting that name, it is resolving it from
> > somewhere!
> > > > > >
> > > > > > ---
> > > > > > Bob Nance
> > > > > > Novation Systems
> > > > > > bob.nance at novationsys.com
> > > > > > 256-534-4620
> > > > > >
> > > > > > On Aug 13, 2014, at 5:36 PM, Michael W. Hall <hallmw at att.net>
> > wrote:
> > > > > >
> > > > > > > So you are saying tha t the RPi is putting that in the reply
> > status?
> > > > > > > That is strange, why would it do it for just my laptop? The
> > other
> > > > > > > machines have the correct name.
> > > > > > >
> > > > > > >
> > > > > > > On Tue, 2014-08-12 at 02:58 +0000, Bob Nance wrote:
> > > > > > >> I hope I understand what you’re asking. Since the ping response
> > > > doesn’t carry any identifying information beyond layer 3, the name
> > > > resolution has to be occurring on the computer reporting the ping
> > status.
> > > > Is that helpful?
> > > > > > >>
> > > > > > >>
> > > > > > >> ---
> > > > > > >> Bob Nance
> > > > > > >> Novation Systems
> > > > > > >> bob.nance at novationsys.com
> > > > > > >> 256-534-4620
> > > > > > >>
> > > > > > >> On Aug 11, 2014, at 9:45 PM, Michael W. Hall <hallmw at att.net>
> > > > wrote:
> > > > > > >>
> > > > > > >>> Ok. I am setting up my RPi and have it working. I ping my
> > laptop
> > > > from
> > > > > > >>> the RPi or any machine and in the reply it does not have the
> > name
> > > > of my
> > > > > > >>> laptop. It has Jack where the name of my machine should be. I
> > > > have
> > > > > > >>> checked the hostname file and it has the name of my machine.
> > > > Anyone
> > > > > > >>> have an idea of where to fix that?
> > > > > > >>>
> > > > > > >>> Thanks,
> > > > > > >>> Michael
> > > > > > >>>
> > > > > > >>> _______________________________________________
> > > > > > >>> LUNA mailing list
> > > > > > >>> LUNA at lunagroup.us
> > > > > > >>> http://lunagroup.us/mailman/listinfo/luna
> > > > > > >>
> > > > > > >> _______________________________________________
> > > > > > >> LUNA mailing list
> > > > > > >> LUNA at lunagroup.us
> > > > > > >> http://lunagroup.us/mailman/listinfo/luna
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > LUNA mailing list
> > > > > > > LUNA at lunagroup.us
> > > > > > > http://lunagroup.us/mailman/listinfo/luna
> > > > > >
> > > > > > _______________________________________________
> > > > > > LUNA mailing list
> > > > > > LUNA at lunagroup.us
> > > > > > http://lunagroup.us/mailman/listinfo/luna
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > LUNA mailing list
> > > > > LUNA at lunagroup.us
> > > > > http://lunagroup.us/mailman/listinfo/luna
> > > >
> > > >
> > > > _______________________________________________
> > > > LUNA mailing list
> > > > LUNA at lunagroup.us
> > > > http://lunagroup.us/mailman/listinfo/luna
> > > >
> > > -------------- next part --------------
> > > An HTML attachment was scrubbed...
> > > URL: <
> > http://lunagroup.us/pipermail/luna/attachments/20140904/9eaec415/attachment.html
> > >
> > > _______________________________________________
> > > LUNA mailing list
> > > LUNA at lunagroup.us
> > > http://lunagroup.us/mailman/listinfo/luna
> >
> >
> > _______________________________________________
> > LUNA mailing list
> > LUNA at lunagroup.us
> > http://lunagroup.us/mailman/listinfo/luna
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lunagroup.us/pipermail/luna/attachments/20140904/bd5fd571/attachment.html>
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
More information about the LUNA
mailing list