DHCP client information

Is there a way to determine the information which was sent to a client
via DHCP. Such as the gateway and the network subnet? I have a
computer which is on the comcast network and I can't figure out what
the ipaddress of the gateway was sent. I look into /etc/resolv.conf
and I don't see any DNS servers either.
Apparently I'm getting the ipaddress, but I can't tell what the rest of
the information is that it is sending.

On 8 Jan 2006 09:47:37 -0800, (E-Mail Removed) wrote:
> Is there a way to determine the information which was sent to a client
> via DHCP.

Most of the time.

Other people's Free advice:
http://www.catb.org/~esr/faqs/smart-questions.html

Always provide your linux vendor, release, desktop manager,.... name/version
of application you are having a problem with.....
It may help you get better answers.

Depends on which dhcp client, (pump, dhcpc, dhclient,...) you are using.

if dhclient you might try looking at /var/lib/dhcp/dhclient-eth*.leases
if dhcpc you might try looking at /etc/dhcpc/dhcpcd-eth*.info

In article <(E-Mail Removed). com>,
<(E-Mail Removed)> wrote:
:Is there a way to determine the information which was sent to a client
:via DHCP. Such as the gateway and the network subnet? I have a
:computer which is on the comcast network and I can't figure out what
:the ipaddress of the gateway was sent. I look into /etc/resolv.conf
:and I don't see any DNS servers either.
:Apparently I'm getting the ipaddress, but I can't tell what the rest of
:the information is that it is sending.
:

Look in /var/lib/dhcp/dhclient-*.leases .

--
Bob Nichols AT comcast.net I am "RNichols42"

(E-Mail Removed) said:
>Is there a way to determine the information which was sent to a client
>via DHCP. Such as the gateway and the network subnet? I have a
>computer which is on the comcast network and I can't figure out what
>the ipaddress of the gateway was sent. I look into /etc/resolv.conf
>and I don't see any DNS servers either.
>Apparently I'm getting the ipaddress, but I can't tell what the rest of
>the information is that it is sending.

I saw something like this recently -- on a system that was configured
so that the wireless lan interface was the primary one, and the
ethernet interface the secondary. Whenever wlan was enabled (even without
a base station being reachable), the gateway/DNS information was not
propagated to appropriate places.
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)