Hi David!
this is only a solution for as long as your dhcp-server does not change
your designated ip-address.
but most of the times this works for a long long time unless you are in
an environment where you pay per minute, or prividers want to make sure
you cannot easily have a server environment
Hi Klaus,
I did this:
> try to put these in a manual network configuration ...
> would look like this:
> in /etc/network/interfaces
>
> auto eth0
> iface eth0 inet static
> address 66.203.194.60
> netmask 255.255.255.0
> broadcast 66.203.194.255
> gateway 66.203.194.1
>
Hi David!
* David Ballantyne <[EMAIL PROTECTED]> [2004-04-24 09:00:
> Thanks for the suggestions. I've tried them out, but still have no joy.
>
> If I try setting a gateway by hand:
for some reason i suspect your kernel being the reason for all that.
have you also updated that one when u swit
r try pinging 66.102.9.104 than www.google.com in order to find
> out if everything works.
>
> good luck,
> klaus
>
> * David Ballantyne <[EMAIL PROTECTED]> [2004-04-23 22:24:
>
> > From: David Ballantyne <[EMAIL PROTECTED]>
> > Subject: Re: problems with
Hi David!
sorry for the mail i sent u in "private" ...
maybe (if u are in control of the dhcp-server) the default-gateway is
not set?
you can influence the routing table yourself. mine looks like that
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use
.102.9.104 than www.google.com in order to find
out if everything works.
good luck,
klaus
* David Ballantyne <[EMAIL PROTECTED]> [2004-04-23 22:24:
> From: David Ballantyne <[EMAIL PROTECTED]>
> Subject: Re: problems with dhclient after upgrade to sarge
> To: [EMAIL PROTECTED], [EMAIL
Hi Klaus,
Sorry for not responding sooner, but I'm not subscribed to the list, so it
took me a while to find your messeage.
In response to your questions:
> what does 'route -an' give you?
I first ran /sbin/dhclient, and I get all the normal looking stuff. Then
running 'route -n' gives:
ansu
Hi!
Most likely your /etc/resolv.conf is wasted. Happens alltoo often in my
university. There is a "good" solution, but I didn't bother to look for it
yet. What I do:
$dhclient
$vim /etc/resolv.conf
(there probably is an empty "search" or "domain" entry -- remove it)
Only then, fire up your brow
PROTECTED]>
> Subject: problems with dhclient after upgrade to sarge
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Resent-From: [EMAIL PROTECTED]
>
> Hi,
>
> Last night I upgraded my woody system to Sarge, and my dhclient broke.
> Before the upgrade I was using
Hi,
Last night I upgraded my woody system to Sarge, and my dhclient broke.
Before the upgrade I was using the package that came with woody
(dhcp3-client 3.0+3.0.1rc9-2.2) and it worked 'out of the box'. That is,
all I had to do was type /sbin/dhclient and I was fine. After the upgrade,
dhcp3-c
10 matches
Mail list logo
