On Mon, 2004-04-12 at 03:20, Aaron Maxwell wrote:
> What is the 'best' (correct, Debian) way to set things up so that the
> connection is brought up automatically at boot time?
> --
The easiest way is to install etherconf:
apt-get install etherconf
or when it's already installed, just do:
dpkg-
Thanks, it works now. Adding the 'auto eth0' line enables it.
- Aaron
On Sunday 11 April 2004 06:45 pm, Paul Johnson wrote:
> Aaron Maxwell <[EMAIL PROTECTED]> writes:
> > What is the 'best' (correct, Debian) way to set things up so that
> > the connection is brought up automatically at boot tim
On Sun, 11 Apr 2004 18:20:22 -0700
Aaron Maxwell <[EMAIL PROTECTED]> wrote:
...
> What is the 'best' (correct, Debian) way to set things up so that
the
> connection is brought up automatically at boot time?
...
edit /etc/network/interfaces,
add /modify the entry for eth0 (asuming that eth0 is th
Aaron Maxwell <[EMAIL PROTECTED]> writes:
> What is the 'best' (correct, Debian) way to set things up so that the
> connection is brought up automatically at boot time?
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
This HAS to be documented somewhere, and I just can't find it...
My workstation runs testing, kernel 2.6.5, and has the dhcp-client
package installed. The net connection is to our cable modem via a
network card. I can bring up the connection by running
'/sbin/dhclient' as root, which at the m
On Sun, Jan 04, 2004 at 04:22:22AM +0100, Jan Minar wrote:
> On Sat, Jan 03, 2004 at 07:04:08PM -0700, Paul Schwartz wrote:
> > Problem solved. Recompiling with CONFIG_FILTER set lets dhcp work. I
> > think they ought to change the recommendation in menuconfig; it kind of
> > says it's not impo
On Sun, Jan 04, 2004 at 08:19:22AM -0500, Paul Morgan wrote:
> On Sun, 04 Jan 2004 04:22:22 +0100, Jan Minar wrote:
> > Definitively. That's why I quoted it, to expose Edward's advise as a
> > b***CENSORED*** (see bellow). It wasn't apparently. I'll file a bug with the
> > Configure.help's maint
On Sun, 04 Jan 2004 04:22:22 +0100, Jan Minar wrote:
>
> Definitively. That's why I quoted it, to expose Edward's advise as a
> bullshit (see bellow). It wasn't apparently. I'll file a bug with the
> Configure.help's maintainers, pointing them to this thread. Does
> anybody wants to add anyth
On Sat, Jan 03, 2004 at 07:04:08PM -0700, Paul Schwartz wrote:
> Problem solved. Recompiling with CONFIG_FILTER set lets dhcp work. I
> think they ought to change the recommendation in menuconfig; it kind of
> says it's not important and to set it to N if you're not sure. Doesn't
> seem like
Paul Schwartz wrote:
Paul Schwartz wrote:
Paul Schwartz wrote:
On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote:
>Try dhclient(8) manually from the command line. If that doesn't
work,
>try spying on the connection using tcpdump(8). Punch your firewall
>properly. That's what I
Paul Schwartz wrote:
Paul Schwartz wrote:
On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote:
>Try dhclient(8) manually from the command line. If that doesn't
work,
>try spying on the connection using tcpdump(8). Punch your firewall
>properly. That's what I'd do. And please pos
On Fri, Jan 02, 2004 at 11:40:42AM -0700, Paul Schwartz wrote:
> >Thanks for your patience. This is really a response the way you
> >requested. I understand the
>
> Oops. I meant NOT.
not WHAT?
--
Jan Minar "Please don't CC me, I'm subscribed." x 7
pgp0.pgp
Descripti
Paul Schwartz wrote:
On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote:
>Try dhclient(8) manually from the command line. If that doesn't work,
>try spying on the connection using tcpdump(8). Punch your firewall
>properly. That's what I'd do. And please post the useful bits
verb
On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote:
>Try dhclient(8) manually from the command line. If that doesn't work,
>try spying on the connection using tcpdump(8). Punch your firewall
>properly. That's what I'd do. And please post the useful bits verbatim
>(e.g. that interfa
Just FYI, that broadcast junk is typical of what's seen when plugged
into a Cisco switch... it's probably NOT from his machine, but from the
switch above it in the network architecture.
On Thursday, Jan 1, 2004, at 23:14 America/Denver, Jan Minar wrote:
On Thu, Jan 01, 2004 at 09:11:39PM -0700,
On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote:
> >Try dhclient(8) manually from the command line. If that doesn't work,
> >try spying on the connection using tcpdump(8). Punch your firewall
> >properly. That's what I'd do. And please post the useful bits verbatim
> >(e.g. that i
On Fri, Jan 02, 2004 at 11:23:06AM +1300, Edward Murrell wrote:
> Check your /var/log/messages file. The most likely error is that you
> didn't enable Socket Filtering in the networking options. You will need
> to recompile for this option to work.
/usr/src/linux-2.4.23/Documentation/Configure.hel
Try dhclient(8) manually from the command line. If that doesn't work,
try spying on the connection using tcpdump(8). Punch your firewall
properly. That's what I'd do. And please post the useful bits verbatim
(e.g. that interfaces entry--who says it's not malformed?).
The error messages are dm
On Thu, Jan 01, 2004 at 01:48:02PM -0700, Paul Schwartz wrote:
> dhcp is specified for eth0 in the interfaces file. nothing seems to happen.
> Where do I look for an error message?
Try dhclient(8) manually from the command line. If that doesn't work,
try spying on the connection using tcpdump(8)
On Fri, 2004-01-02 at 05:49, Paul Schwartz wrote:
> I just made and installed my first kernel [2.4.18]! and booted too!
> One problem is that the network initialization that used to occur
> [2.4.18-bf24] doesn't.
> The ether net card is recognized but my machine no longer does an
> inquiry to the
Jan Minar wrote:
On Thu, Jan 01, 2004 at 09:49:00AM -0700, Paul Schwartz wrote:
I just made and installed my first kernel [2.4.18]! and booted too!
One problem is that the network initialization that used to occur
[2.4.18-bf24] doesn't.
The ether net card is recognized but my machine no longer
On Thu, Jan 01, 2004 at 09:49:00AM -0700, Paul Schwartz wrote:
> I just made and installed my first kernel [2.4.18]! and booted too!
> One problem is that the network initialization that used to occur
> [2.4.18-bf24] doesn't.
> The ether net card is recognized but my machine no longer does an
> i
I just made and installed my first kernel [2.4.18]! and booted too!
One problem is that the network initialization that used to occur
[2.4.18-bf24] doesn't.
The ether net card is recognized but my machine no longer does an
inquiry to the router to get an address.
Where do I find the stimulus?
N
On Tue, Sep 22, 1998 at 12:02:41PM -0400, Smith, Brian N. wrote:
> I am referring to the client
> What happens to the IP address one assigns during the kernal build?
??? You mean during debian installation? The one in /etc/init.d/network?
Never mind, it gets overwritten anyway.
Nils
--
*
AM
To: debian-user
Subject:Re: DHCP on boot
Are you talking about the client or the server?
If you are talking about the client then you should have installed
(automatically, from dhcpcd*.deb) a script in /etc/init.d/ that will
start the
Are you talking about the client or the server?
If you are talking about the client then you should have installed
(automatically, from dhcpcd*.deb) a script in /etc/init.d/ that will start the
client at boot time. But if you have a PCMCIA network card you should set
DHCP="y" in /etc/pcmcia/networ
How does one get DHCP to initiate on bootup? All the Faqs seem to point to
assigning the IP address when compiling and assume it will never change
Thanks in advance
Brian Smith
27 matches
Mail list logo
