Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Oct 2002 15:42:15 -0500
From:      "DaleCo Help Desk" <daleco@daleco.biz>
To:        "Peter Leftwich" <Hostmaster@Video2Video.Com>
Cc:        "FreeBSD LIST" <FreeBSD-Questions@FreeBSD.Org>
Subject:   Re: What is vnlru really?
Message-ID:  <020501c27d30$2c2ffd80$fa00a8c0@DaleCoportable>
References:  <20021026141539.T25789-100000@earl-grey.cloud9.net>

next in thread | previous in thread | raw e-mail | index | archive | help
From: "Peter Leftwich" <Hostmaster@Video2Video.Com>
To: "DaleCo Help Desk" <daleco@daleco.biz>
Cc: "FreeBSD LIST" <FreeBSD-Questions@FreeBSD.Org>
Sent: Saturday, October 26, 2002 1:17 PM
Subject: Re: What is vnlru really?


> On Wed, 23 Oct 2002, DaleCo Help Desk wrote:
> > PL> PS - Is `arp -a` the most reliable way to get one's current
IP address?
> > What's wrong with "ifconfig" ???
> > Kevin Kinsey
>
> I was not familiar with ifconfig and am surprised at such a similar
name to
> winipcfg for Win98.  It seems arp -a tells me one IP while ipconfig
tells
> me another.  Is that because I'm using DHCP, or is arp -a maybe
reporting a
> DNS value, not my currently-assigned IP?
>
> PS - Yack! ".biz?!"
>
Depends on your network configuration, I guess.
It only occurred to me after I had posted that
you might be interested in what IP you were
presenting to the world, and not just what addy
was assigned to the local interface.

However, ifconfig, which Windows has
"M"-ulated (immolated?) with "winipcfg"
and the even more sinister "ipconfig," will
tell you lots about all the system interfaces
when used with the -a switch, ie:

 #ifconfig -a
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.2.103 netmask 0xffffff00 broadcast 192.168.0.255
        inet6 fe80::2a0:ccff:fe25:9347%dc0 prefixlen 64 scopeid 0x1
        ether 00:a0:cc:25:93:47
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
        inet 127.0.0.1 netmask 0xff000000
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500

As you see from this example, this host is on a LAN
at 192.168.2.103... I assume, if you're using dialup,
that the IP addy would appear in the ppp0: section....

"arp -a" is going to give you information about more
machines than just your own, quite possibly.  I'd use
this instead:

#arp -n your.hostname.tld
your.hostname.tld (11.22.33.44) -- no entry

HTH,

Kevin Kinsey


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?020501c27d30$2c2ffd80$fa00a8c0>