From owner-freebsd-atm Wed Jan 24 8:44:13 2001 Delivered-To: freebsd-atm@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 1C78937B698 for ; Wed, 24 Jan 2001 08:43:56 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f0OGhoq30947 for ; Wed, 24 Jan 2001 11:43:50 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010124112130.036fecb0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Wed, 24 Jan 2001 11:37:43 -0500 To: freebsd-atm@freebsd.org From: Mike Tancsa Subject: en driver and talking to itself Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am not sure if this is because its a point to point interface, but from my own machine, I can never ping myself, only the other side. e.g. ifconfig en0 en0: flags=841 mtu 9180 inet 192.168.1.2 netmask 0xfffffffc ruby2% route add -iface 192.168.1.1 -link en0:3.0.03.8e ruby2% ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host ^C --- 192.168.1.2 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss But if I do this, ruby2# route add 192.168.1.2 127.0.0.1 add host 192.168.1.2: gateway 127.0.0.1 ruby2# !ping ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes 64 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=0.047 ms 64 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=0.022 ms It works. Is it supposed to work this way ? ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Wed Jan 24 11:47:28 2001 Delivered-To: freebsd-atm@freebsd.org Received: from cc762335-a.ebnsk1.nj.home.com (cc762335-a.ebnsk1.nj.home.com [24.3.219.36]) by hub.freebsd.org (Postfix) with SMTP id 733A337B402 for ; Wed, 24 Jan 2001 11:47:11 -0800 (PST) Received: (qmail 74369 invoked from network); 24 Jan 2001 19:45:59 -0000 Received: from athena.faerun.com (HELO athena) (192.168.0.2) by cc762335-a.ebnsk1.nj.home.com with SMTP; 24 Jan 2001 19:45:59 -0000 Message-Id: <4.2.2.20010124144335.00d26220@netmail.home.com> X-Sender: damascus@netmail.home.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 24 Jan 2001 14:46:51 -0500 To: Mike Tancsa From: Carroll Kong Subject: Re: en driver and talking to itself Cc: freebsd-atm@FreeBSD.ORG In-Reply-To: <5.0.1.4.0.20010124112130.036fecb0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:37 AM 1/24/01 -0500, you wrote: >I am not sure if this is because its a point to point interface, but from >my own machine, I can never ping myself, only the other side. > >It works. Is it supposed to work this way ? > > ---Mike Yes. I am not 100% sure.... but it might be because normally an ARP address is associated with the IP address. So there is some kind of mapping for you to ping yourself normally. However, over ATM, PVCs are mapped to IPs. PVCs are "locally" known... so the PVC mapping to your own ip address is only the case for the "other" end not for yourself. You could create a little mapping to "loop" back to yourself I would imagine. (I did this once, but I forgot the details) Other than that, yes, it is normal to not be able to ping yourself if you are using Classical IP over ATM. -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Wed Jan 24 12:21:30 2001 Delivered-To: freebsd-atm@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 9342037B699 for ; Wed, 24 Jan 2001 12:21:07 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f0OKFVV83910; Wed, 24 Jan 2001 15:15:31 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010124145616.01f89620@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Wed, 24 Jan 2001 15:09:23 -0500 To: Carroll Kong From: Mike Tancsa Subject: Re: en driver and talking to itself Cc: freebsd-atm@FreeBSD.ORG In-Reply-To: <4.2.2.20010124144335.00d26220@netmail.home.com> References: <5.0.1.4.0.20010124112130.036fecb0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 02:46 PM 1/24/01 -0500, Carroll Kong wrote: >At 11:37 AM 1/24/01 -0500, you wrote: >>I am not sure if this is because its a point to point interface, but from >>my own machine, I can never ping myself, only the other side. >> >>It works. Is it supposed to work this way ? >> >> ---Mike > >Yes. I am not 100% sure.... but it might be because normally an ARP >address is associated with the IP address. So there is some kind of >mapping for you Thanks. Actually, that makes sense. I wonder if there is a more optimal way to route to the interface rather than going through the loopback. It seems rather inefficient to talk to my Efficient :-) ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message