On Tuesday 20 November 2007, Andrei Popescu wrote:
> On Tue, Nov 20, 2007 at 09:03:17PM -0500, Hal Vaughan wrote:
> > Would that be a setting on their router or on their Windows server?
> > My guess is it depends on whether my system is behind uses NAT.
>
> Whatever they use as the DHCP server. Th
On Tue, Nov 20, 2007 at 09:03:17PM -0500, Hal Vaughan wrote:
> Would that be a setting on their router or on their Windows server? My
> guess is it depends on whether my system is behind uses NAT.
Whatever they use as the DHCP server. They could also be using some
managed switches and you are
On Tuesday 20 November 2007, you wrote:
> On 21/11/2007, Hal Vaughan <[EMAIL PROTECTED]> wrote:
> > I have a default Sarge installation that I had to move to a new
> > network. It had been getting the address through DHCP with no
> > problem. Now, on the new network, it tries to connect to a DHCP
On 21/11/2007, Hal Vaughan <[EMAIL PROTECTED]> wrote:
> I have a default Sarge installation that I had to move to a new network.
> It had been getting the address through DHCP with no problem. Now, on
> the new network, it tries to connect to a DHCP server, but there's no
> connection. I was not
On Tue, Nov 20, 2007 at 05:53:40PM -0500, Hal Vaughan wrote:
> I have a default Sarge installation that I had to move to a new network.
> It had been getting the address through DHCP with no problem. Now, on
> the new network, it tries to connect to a DHCP server, but there's no
> connection.
gusti <[EMAIL PROTECTED]>:
>
> I have all the packages up-to-date, I'm using official kernel 2.6.18
> for debian stable. I already tried 'dhclient' from the packages
> 'dhcp-client' and 'dhcp3-client' and 'pump' from the package 'pump' and
> still after few minutes my network die and I mus
Kevin Veroneau <[EMAIL PROTECTED]> writes:
> My current set-up is, my ISP's cable modem connects to my debian
> sarge router/gateway. My other systems connect from that. My other
> systems run debian testing, when I connect the RJ-45 jack from my
> cable modem directly to my debian testing box,
On Tue, 2006-03-07 at 21:12 +0530, Aravind. R wrote:
Hello
I am using Debian Sarge. Whenever I boot the machine, the DHCP client
assigns an IP address, and just waits. Booting continues only when I
press Ctrl + C . Howver, the network works fine. Could you suggest some
remedy.
I had this exact
There's a config file which on Debian Sarge is at /etc/dhclient.conf I
think with a timeout variable. Just adjust that.
Thanks, Tom
On Tue, 2006-03-07 at 21:12 +0530, Aravind. R wrote:
> Hello
> I am using Debian Sarge. Whenever I boot the machine, the DHCP client
> assigns an IP address, and ju
On Tue, 2006-03-07 at 21:12 +0530, Aravind. R wrote:
> Hello
> I am using Debian Sarge. Whenever I boot the machine, the DHCP client
> assigns an IP address, and just waits. Booting continues only when I
> press Ctrl + C . Howver, the network works fine. Could you suggest some
> remedy.
# aptitud
On Tuesday, 27 December 2005 at 15:34:19 +0100, Florian Kulzer wrote:
> Richard Lyons wrote:
>
> [...]
>
> >I found that too, and tried "modprobe ieee80211_crypt_wep" The module
> >loaded but the connection still obstinately failed. I found two other
> >modules in /lib/modules/2.6.14-2-686/kerne
Richard Lyons wrote:
[...]
I found that too, and tried "modprobe ieee80211_crypt_wep" The module
loaded but the connection still obstinately failed. I found two other
modules in /lib/modules/2.6.14-2-686/kernel/net/ieee80211/, namely
ieee80211_crypt_ccmp and ieee80211_crypt_tkip, so I modprobe
On Tuesday, 27 December 2005 at 2:13:22 +0100, Florian Kulzer wrote:
> Richard Lyons wrote:
>
> [...]
>
> >Nearly! You were right that the modules were not loaded. I tried
> >'modprobe ieee80211' and 'ifup eth0' and also rebooting after editing
> >/etc/modules. It now loads two modules ieee802
Richard Lyons wrote:
[...]
Nearly! You were right that the modules were not loaded. I tried
'modprobe ieee80211' and 'ifup eth0' and also rebooting after editing
/etc/modules. It now loads two modules ieee80211 and ieee80211_crypt.
I assume that is the expected outcome.
It still does not asso
On Sunday, 25 December 2005 at 13:15:45 +0100, Florian Kulzer wrote:
> Hi again,
>
> Richard Lyons wrote:
[...]
>
> >eth0 IEEE 802.11b ESSID:"Coix" Nickname "HERMES I"
> > Mode:Managed Frequency:2.422 GHz Access Point: Not-Associated
>
> I think that is the cause of yo
On Sat, 24 Dec 2005 19:29:30 +
Richard Lyons <[EMAIL PROTECTED]> wrote:
> I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
> wifi card talks to the Netgear DG834G router when security is disabled,
> but when I turn WEP on it doesn't connect.
>
> /etc/network/interface
Hi again,
Richard Lyons wrote:
On Sunday, 25 December 2005 at 1:12:53 +0100, Florian Kulzer wrote:
Maybe you can first try to find out if you have a problem with the
interface itself or with the dhcp-client. To configure the interface
directly you can use the iwconfig command (as root)
I d
On Saturday, 24 December 2005 at 23:37:45 -0500, jlquinn wrote:
> Richard Lyons wrote:
[...]
> >
> >Exiting.
> >
> >Failed to bring up eth0.
> >
> >Which tells me I left something out. But what?
>
> Chances are with a thinkpad that you have onboard ethernet. eth0 will
> correspond to th
On Sunday, 25 December 2005 at 1:12:53 +0100, Florian Kulzer wrote:
> Hi Richard,
>
> Richard Lyons wrote:
> >But ifup eth0 gives
> >
> >etho: New link status: Connected (0001)
> >Listening on LPF/eth0/00:02:2d:a6:07:bb
> >Sending on LPF/eth0/00:02:2d:a6:07:bb
> >DHCPDISCOVER on
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it doesn't connect.
/etc/network/interfaces has
iface eth0 inet dhcp
wireless-essid Coig
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it doesn't connect.
/etc/network/interfaces has
iface eth0 inet dhcp
wireless-essid Coigxxx
Hi Richard,
Richard Lyons wrote:
But ifup eth0 gives
etho: New link status: Connected (0001)
Listening on LPF/eth0/00:02:2d:a6:07:bb
Sending on LPF/eth0/00:02:2d:a6:07:bb
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
...more similar...
No DHCPOFFERS receiv
Richard Lyons wrote:
On Saturday, 24 December 2005 at 13:21:04 -0800, Andrew Sackville-West wrote:
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it d
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it doesn't connect.
/etc/network/interfaces has
iface eth0 inet dhcp
wireless-essid Coigx
On Thursday 29 January 2004 07:59 pm, Christopher Blough wrote:
> Here is an updated capture of route -n
> --
> Kernel IP routing table
> DestinationGateway Genmask Flags Metric Ref
> Use Iface
> 209.112.193.120 *255.255.255.248 U 0 0
Here is an updated capture of route -n
--
Kernel IP routing table
DestinationGateway Genmask Flags Metric Ref Use
Iface
209.112.193.120 *255.255.255.248 U 0 00
eth0
netstat -nr results
Kernel IP routing table
D
I will get a copy of route -n information when my machine is at hand. At the
moment, I'm at work, and it isn't available. IIRC, the only entry was
something like this:
AddressGateway
209.112.xxx.120*
There was only that one entry.
The IP address listed in my route add example
Quoting Christopher Blough <[EMAIL PROTECTED]>:
[snip]
> route add -net default gw 209.xxx.xxx.xxx also returned a 'network is unreachable'
> error. Essentially, I am seeing my LAN boxes fine, but am completely unable to go
> past my firewall. Before anyone asks, yes, it's properly punched. All e
On Thursday 29 January 2004 01:47 pm, Christopher Blough wrote:
> I have recently made my first foray into Debian.
Welcome.
> I am able to ping the other three Windows-based boxes on my LAN (same
> subnet as this box). However, any attempt to resolve an internet
> address or to go outside of
Attila Csosz <[EMAIL PROTECTED]> writes:
> How to setup a dhcp client? My computer connected to an another(server)
> the server act as a "dhcp server". If I put the following lines to the
> /etc/network/interfaces
>
> auto eth0
> iface eth0 inet dhcp
>
> Is it enough or should I start a client pro
David,
--On Thursday, March 27, 2003 04:35:43 PM +0100 David Fokkema
<[EMAIL PROTECTED]> wrote:
>> After this my network link goes down and comes up again with the new
>> address.
>>
>> Any ideas what would cause the dhcpd to give me a new address instead
>> of assigning the same again?
>
> Are y
Harry,
> >> After this my network link goes down and comes up again with the new
> >> address.
> >>
> >> Any ideas what would cause the dhcpd to give me a new address instead of
> >> assigning the same again?
> >
> > Are you sure there is not even a DHCPNAK received? And I'm puzzled, since
> > tcp
David,
--On Thursday, March 27, 2003 03:31:45 PM +0100 David Fokkema
<[EMAIL PROTECTED]> wrote:
I run dhcpdump and get this output at the time when my IP changes
(192.168.1.192 is the 'old' address, 192.168.1.2 is the dhcpd):
TIME: 14:06:30.215030
IP: 192.168.1.192.68 (0:10:a4:f5:63:d6) >
> I run dhcpdump and get this output at the time when my IP changes
> (192.168.1.192 is the 'old' address, 192.168.1.2 is the dhcpd):
>
> TIME: 14:06:30.215030
> IP: 192.168.1.192.68 (0:10:a4:f5:63:d6) > 192.168.1.2.67
> (0:30:48:10:49:75)
> OP: 1 (BOOTPREQUEST)
> HTYPE: 1 (Ethernet)
>
David,
I run dhcpdump and get this output at the time when my IP changes
(192.168.1.192 is the 'old' address, 192.168.1.2 is the dhcpd):
TIME: 14:06:30.215030
IP: 192.168.1.192.68 (0:10:a4:f5:63:d6) > 192.168.1.2.67
(0:30:48:10:49:75)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HO
> On the dhcpd side (which is a RedHat system) I get:
>
> dhcpd: Reclaiming abandoned IP address 192.168.1.198.
> dhcpd: Abandoning IP address 192.168.1.198: pinged be fore offer
> dhcpd: Reclaiming abandoned IP address 192.168.1.200.
>
> After that, the client gets a new address and everything is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 24 June 2002 18:02, Alex Roitman wrote:
> Hello,
>
> I had my home system on a cable modem with AT&T Broadband
> as a provider for about a year. Everything worked perfectly
> well, until about a week ago they must have switched the
> DHCP ser
On Mon, Jun 24, 2002 at 05:02:27PM -0500, Alex Roitman wrote:
> Hello,
>
> I had my home system on a cable modem with AT&T Broadband
> as a provider for about a year. Everything worked perfectly
> well, until about a week ago they must have switched the
> DHCP server. Now my dhclient gets no DH
I'm not sure if this would help any, but I usually use pump instead of
dhcp-client. My ISP has a whole bunch of different IP blocks, and it's
strange. If I use dhcp-client (dhclient), I get IP blocks like 207.x.x.x, and
if I use pump instead of dhcp-client, I get 64.x.x.x. When I get an IP in th
On Tue, 2002-06-11 at 12:09, Bedford, Donald T. wrote:
> I've been using dhcp-client 2.0pl4-2 w/ Potato and just upgraded to Woody
> (w/ dhcp-client 2.0pl5-11). When I rebooted (and every time since) the dhcp
> client does not pick up an IP address and I have to manually start it - then
> all is we
On Wed, 20 Feb 2002, Paul Hampson wrote:
> You must also have
> auto eth0
> if you want it to configure on boot.
I forgot about that...
--
Baloo
On Tue, 19 Feb 2002, Raffaele Sandrini wrote:
> What must i do to get a host configurated automatically?
> Isn't it enough to place "iface eth0 inet dhcp" into the intefaces file and
> havind dhcp-client installed?
> I does not work on my machine with this confuguration.
This should be the case.
On Tue, Feb 19, 2002 at 06:00:25PM +0100, Raffaele Sandrini wrote:
> What must i do to get a host configurated automatically?
> Isn't it enough to place "iface eth0 inet dhcp" into the intefaces file and
> havind dhcp-client installed?
You must also have
auto eth0
if you want it to configure on bo
On Fri, Feb 01, 2002 at 10:31:10PM -0800, John Mautz wrote:
[...]
> What would like is to take the DNS addresses retrieved by dhclient and
> stick them in the dhcpd.conf, then have dhcpd restarted to apply the
> changes. This way when either ISP changes any server info on me all the
> changes a
On Fri, Nov 30, 2001 at 10:38:03AM +0530, Raghavendra Bhat wrote:
> Usage of dhcp-client is recommended over dhcpcd.
Yes, that was the reason I installed it.
> You have to enable CONFIG_FILTER=y in your kernel configuration options
> for dhcp-client to work properly.
I did not kn
On Thu, Nov 29, 2001 at 07:41:50PM -0800, Mike Pfleger wrote:
> I've got that running by tweaking my kernel. It required a number of
> options to be enabled, that I didn't use by default. Which kernel?
> I can send you my .config off-list if you like.
>
Currently am running 2.4.13-ac
What is the difference between
pump
dhcpcd
dhcp-client
any others?
Raghavendra Bhat wrote:
Subject:
Re: dhcp-client
From:
Raghavendra Bhat <[EMAIL PROTECTED]>
Date:
Fri,
[Fri, Nov 30, 2001 at 12:36:53PM +0530] Sridhar M.A. :
> Can somebody give me some pointers to set it up ?
Usage of dhcp-client is recommended over dhcpcd.
You have to enable CONFIG_FILTER=y in your kernel configuration options
for dhcp-client to work properly. Maybe in stock kernel-image pac
* Sridhar M.A. ([EMAIL PROTECTED]) wrote:
> Hi,
>
> Till recently I was using potato. I had installed the package dhcpcd
> to enable my cable internet connection. After apt-get upgrade to
> testing, I was surprised to see that the dhcpcd package was not
> upgraded, but removed. Downloaded and ins
On Tue, 2001-11-20 at 09:59, D. wrote:
> Thanks for the help on this. This is what my
> /etc/network/interface looks like now
> auto lo eth0
> iface lo inet loopback
> iface eth0 inet dhcp
> When I did the auto eth0 on the same line I got the
> error unable to configure auto=auto. When I did it
On Mon, 2001-11-19 at 14:03, D. wrote:
> Hi all,
>I have installed dhcp-client.
>My /etc/network/interfaces is:
> auto lo
> iface lo inet loopback
> iface eth0 inet dhcp
>I have made the files in /etc/network/ifup and
> ifdown and they each have in them eth0. I have a
> /var/dhcp
Thanks for the help on this. This is what my
/etc/network/interface looks like now
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
When I did the auto eth0 on the same line I got the
error unable to configure auto=auto. When I did it in
a seperate line it would not configure.
Anyway it
"D." <[EMAIL PROTECTED]> wrote:
>
>
> Hi all,
> I have installed dhcp-client.
> My /etc/network/interfaces is:
> auto lo
> iface lo inet loopback
> iface eth0 inet dhcp
> I have made the files in /etc/network/ifup and
> ifdown and they each have in them eth0. I have a
> /var/dhcp/dhclien
Hi all,
I have installed dhcp-client.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet dhcp
I have made the files in /etc/network/ifup and
ifdown and they each have in them eth0. I have a
/var/dhcp/dhclient.leases. The /etc/resolv.conf is
there and onc
On Tue, Nov 13, 2001 at 10:37:45AM +0530, Raghavendra Bhat wrote:
> Hello: In my home machine (sid+dhcp-client 3.0final-1+kernel 2.4.x),
> /etc/resolv.conf does not get modified when I do a 'networking daemon
> restart'. At a location machine (potato+dhcp-client 2.0pl4-2+kernel
> 2.4.x)
I haven't found pump to be terribly reliable in talking to my local
@home DHCP server(s)... I ended up removing it and instead using dhcpcd.
That, at least, reliably pulls an IP, as long as I make sure there's no
cache file available to it before it attempts to negotiate.
It sounds like what they'
Joe Hu wrote:
My cable modem provider, RCN, told me today that my linux box, which runs
dhcp client, sent out false information to RCN's dhcp server in such a way
that the dhcp server still thought the IP taken by my linux box was free.
That caused other RCN customers unable to connect to the ne
On Tue, Jun 19, 2001 at 10:45:01AM +0200, nico de haer wrote:
> Mike,
>
> Have you checked that the firewall is your default gateway?
> BTW assigning 192.168.1.0 as an IP to a host is a BAD idea!! this is your
> network address Pick your IP numbers in the range 192.168.1.1 to
> 192.168.1.254 (
On Tuesday 19 June 2001 05:58, Mike Pfleger spoke wisely:
> Hello.
>
> I've upgraded two partitions from Debian potato (well, Storm, actually) to
> testing, and have installed dhcp-client for net access through my firewall.
> I can ping my firewall, and verify the eth0 to firewall traffic via the
>
Hi!
> On Fri, May 04, 2001 at 05:09:57AM -0700, Aaron Walker wrote:
> >
> >I recently installed Debian v2.2r3 and I installed the DHCP client as
> >well.. when debian boots, DHCP assigns eth0 an IP (which it is
> >supposed to do, in this case 192.168.1.4) then it also assigns the
> >
On Fri, May 04, 2001 at 05:09:57AM -0700, Aaron Walker wrote:
>
>I recently installed Debian v2.2r3 and I installed the DHCP client as
>well.. when debian boots, DHCP assigns eth0 an IP (which it is
>supposed to do, in this case 192.168.1.4) then it also assigns the
>loopback (/dev
On Fri, Feb 02, 2001 at 11:57:29AM +0100, Daniel de los Reyes wrote:
> At boot time, dhcp-client checks all avaliable network interfaces. I only
> want it to work on one (/dev/eth1).
> How can I change this behaviour?
Take a look at /etc/dhclient.conf
There should be one 'interface' section for
On Fri, 29 Dec 2000 18:50:16 -0500
Ed Kear <[EMAIL PROTECTED]> wrote:
> If you have a Debian 2.2 or later system, try editing
> /etc/network/interfaces
Cheers, Ed. That is indeed the correct file to edit. My fault for not
specifying that I was using Woody - I didn't realise there was a
differenc
At 02:40 PM 12/29/00 -0600, Jon Pennington wrote:
Phillip Deackes wrote:
>
> On Fri, 29 Dec 2000 08:32:55 -0800 (PST)
> "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
>
> > edit /etc/init.d/ script. Each one has an argument for which
> > eth to
> > listen on. For pump it is -i eth0.
>
> What
Phillip Deackes wrote:
>
> On Fri, 29 Dec 2000 08:32:55 -0800 (PST)
> "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
>
> > edit /etc/init.d/ script. Each one has an argument for which
> > eth to
> > listen on. For pump it is -i eth0.
>
> What is ? I have no /etc/init.d/eth0 or /etc/init.d/dh
On 29-Dec-2000 Phillip Deackes wrote:
> On Fri, 29 Dec 2000 08:32:55 -0800 (PST)
> "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
>
>> edit /etc/init.d/ script. Each one has an argument for which
>> eth to
>> listen on. For pump it is -i eth0.
>
> What is ? I have no /etc/init.d/eth0 or /etc
On Fri, 29 Dec 2000 08:32:55 -0800 (PST)
"Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
> edit /etc/init.d/ script. Each one has an argument for which
> eth to
> listen on. For pump it is -i eth0.
What is ? I have no /etc/init.d/eth0 or /etc/init.d/dhcp or
anything like that - all I have whic
On 29-Dec-2000 [EMAIL PROTECTED] wrote:
>
> How do ou make the dhcp client only listen on one eth*? Whenever dhcp
> client is tarted it listens on every network interface on the system, how
> do I change this?
>
edit /etc/init.d/ script. Each one has an argument for which eth to
listen on. F
%% Phil Brutsche <[EMAIL PROTECTED]> writes:
pb> This is what I usually do:
pb> 1) take away the symlink /etc/rcS.d/S20dhcp-client (or something like
pb>that)
pb> 2) use /etc/network/interfaces to configure all interfaces.
Ah! I see. So, in my /etc/network/interfaces I have:
ifa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A long time ago, in a galaxy far, far way, someone said...
> I just noticed something weird on my firewall Linux box (Debian
> GNU/Linux 2.2 standard, plus security.debian.org fixes).
>
> This box has 3 interfaces: lo of course, plus eth0 which is ho
Sorry to reply to my own mail, but hey, I finally got my cable
connection working and I'm willing to share what I've learnt. ;-)
The problems I experienced were with the method my cable provider uses
to get their clients authenticated / initialized / connected.
This is what happens:
o Fi
On Sat, 9 Sep 2000, S.Salman Ahmed wrote:
> I just tried installing Potato using the latest boot floppies (compact
> set) and had the same result - pump failed to get configuration info
> using DHCP. I ended up statically configuring the ethernet card in my
> system using the same values as would/
I used the boot floppies, and it worked with my cable modem. I guess I
didn't know it was using pump, it just worked by magic. I went ahead and
installed dhcpcd when I was done.
BTW, make sure you get root.bin, resc.bin, plus all three driver floppies
BEFORE you start the installation and blow awa
A long time ago, in a galaxy far, far way, someone said...
> So, does this mean that if I try and install potato on my home system
> using the boot floppies (to avoid having to burn 1 or more CDs) and I
> select the DHCP net configuration option for doing a network/internet
> install that the inst
On Wed, Sep 06, 2000 at 01:53:19PM -0500, John Reinke wrote:
> Read Sven's message below again - dhcpcd - this is not server software.
Yup, note the 'c' in dhcpcd. Stands for client. And the binary behaves
like a daemon in the way that it disconnects from the terminal and keeps
running the way usu
Yeah, there's that, but from all the inquiring I have done, that address is
pretty much
unchanging. The problem I've found with @home, at least in Eugene, OR, is that
they use
alot of mystique to describe what they do, like it's magic or something, when
all they
really do is pass packets and ru
Read Sven's message below again - dhcpcd - this is not server software.
This is what I use for my cable modem connection. It worked for me before
I even had a clue what I was doing! It automatically is assigned the DNS
servers, etc, so all you need to do is turn it on and it works (even
easier than
Oh, no, dhcpd is the server software. That won't work at all, unless you are on
contract with @home to provide this service:^) In fact, you might be handing
out
addresses to @home customers who wonder why it doesn't work.
What they don't tell you about @home is that they use static ip addresses
On Wed, Sep 06, 2000 at 11:30:13AM -0500, Phil Brutsche wrote:
> dhclient (that's the name of the executable in the dhcp-client package) is
> the best (imo) dhcp client for unix-type systems. That would explain why
> NetBSD, OpenBSD, and FreeBSD use dhclient in their bootup sequence when
> you sel
A long time ago, in a galaxy far, far way, someone said...
> I was able to figure out the problem myself. For some reason, I was
> unable to get Pump to work with the [EMAIL PROTECTED] DHCP servers. I then
> remembered that there was another DHCP client, dhcp-client, which I have
> used earlier on
I'm on @home as well, and pump just failed badly for me. However, dhcpcd
worked out of the box, so to say:
dhcpcd -h XXX did the job right then.
Andrei
--
First there was Explorer...
Then came Expedition.
This summer
C
On Sat, Apr 01, 2000 at 11:02:55AM -0600, matt garman wrote:
> I'm trying to get AT&T @home cable modem service working on my system.
> >From what I have gathered, it seems as though it should be as easy as
> installing a dhcp client package, and let dhcp get everything working for
> me.
> ...
Sor
Add the following line to the bottom of /etc/dhclient.conf...
interface "eth0" {}
Modifying the configuration file (/etc/dhclient.conf) is a much cleaner
solution than modifying the init-script (/etc/init.d/dhcp-client).
Enjoy!
Bryan
On 25-Jan-2000 Sean 'Shaleh' Perry wrote:
>
> On 25-Jan-2
On 25-Jan-2000 Maciej Kalisiak wrote:
> I've just recently switched from 'dhcpcd' to 'dhcp-client' (better
> configuration, lots of docs). I just installed the package, and edited
> '/etc/dhclient.conf' to add a single option (I have to send a "host-name" to
> the server). I startup the client,
On Tue, Jan 11, 2000 at 11:02:48AM -0800, Kenneth Scharf wrote:
> How do I setup my linux box to get it's lan address
> from dhcp-client? I've installed dhcp-client (no
> configuration requested). Looking at
> /etc/init.d/network I see my static ip is defined and
> used in the ifconfig line to s
I also had this problem - I re-ran the post-installation script and it
worked after that.
Martin
From: Dpk <[EMAIL PROTECTED]>
To: "E. S. Venkatraman" <[EMAIL PROTECTED]>
CC: debian-user
Subject: Re: DHCP client
Date: Tue, 5 Oct 1999 14:51:12 -0400
On Tue, Oct 05, 19
On Wed, Sep 29, 1999 at 12:05:00AM -0400, Bryan Scaringe wrote:
Just out of curiosity, are there plans to include dhcpcd in the base
system for Potato?
There has been mention of including *a* dhcp client package, but I
don't think anything is being done on it right now. I don't read the
Just out of curiosity, are there plans to include dhcpcd in the base
system for Potato? When I wanted to do an internet install over my
cable modem, it involved also downloading the dhcpcd and netstd
packages, and installing them in a Virtual Console, after installing
base, but before installing t
On Tue, Oct 05, 1999 at 02:51:12PM -0400, Dpk wrote:
On Tue, Oct 05, 1999 at 10:51:33AM -0400, E. S. Venkatraman wrote:
I have a PC on a network where the IP addresses are assigned
using a DHCP server. I tried installing Debian 2.1 and I have
the following problem. If I s
On Tue, Oct 05, 1999 at 10:51:33AM -0400, E. S. Venkatraman wrote:
I have a PC on a network where the IP addresses are assigned using
a DHCP server. I tried installing Debian 2.1 and I have the
following problem. If I say I am connected to a network it
requires me to type in the IP a
I gave it a try this morning... unfortunately, it exits with a message
to the effect of "interface is not ethernet". There's a patch floating
around for version 0.70 which (mostly) makes it work with token-ring,
but it won't apply against later versions (and a quick browse through
the source seems
-BEGIN PGP SIGNED MESSAGE-
On Thu, 25 Feb 1999, Gregory T. Norris wrote:
> Does a DHCP client exist which can handle token-ring on 2.2.x kernels?
> Neither dhcpcd not dhclient (ISC's client) can deal with it.
Try using dhcpcd v1.3, earlier versions (not remember which versions
exactly) d
92 matches
Mail list logo
