On (11/02/06 18:29), Henrique Rennó wrote:
> I'm using static.
>
> ifconfig results:
>
> eth0Encapsulamento do Link: EthernetEndereço de HW 00:C0:9F:88:E6:52
> inet end.: 192.168.0.1 Bcast:192.168.0.255 Masc: 255.255.255.0
> UP BROADCASTRUNNING MULTICAST MTU:1500
Hello Clive!!!
I'm using static.
ifconfig results:
eth0Encapsulamento do Link: EthernetEndereço de HW 00:C0:9F:88:E6:52
inet end.: 192.168.0.1 Bcast:192.168.0.255 Masc: 255.255.255.0
UP BROADCASTRUNNING MULTICAST MTU:1500Métrica: 1
RX packets: 0 er
1
> Is there any service I have to start to enable the network card to
> work fine? I saw some services in /etc/rcS like networking and
> ifupdown but restarting them didn't work.
To start and stop services:
/etc/init.d/networking [start|stop|restart]
>
> When I boo
I tried using "ifup -a" to read all interfaces again from
/etc/network/interfaces but it didn't work, still getting "Destination
Host Unreachable".
--
Henrique
have to use ifconfig if it's better).
Is there any service I have to start to enable the network card to
work fine? I saw some services in /etc/rcS like networking and
ifupdown but restarting them didn't work.
When I boot the system with the network cable connected to the RJ-45
port comes th
Derek Broughton wrote:
> H. S. wrote:
>
>
>>On 10/15/05, H. S. <[EMAIL PROTECTED]> wrote:
>>
>>>
>>>
>>>On 10/15/05, Derek Broughton <[EMAIL PROTECTED]> wrote:
>>>
I can't help with guessnet, but I wonder why you think ifplugd could be
>>>
>>>I don't know for sure. But in the past, I had a si
H. S. wrote:
> On 10/15/05, H. S. <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> On 10/15/05, Derek Broughton <[EMAIL PROTECTED]> wrote:
>> >
>> > I can't help with guessnet, but I wonder why you think ifplugd could be
>>
>> I don't know for sure. But in the past, I had a similar problem (boot
>> stall) a
John O'Hagan wrote:
>
>
>>auto eth0
>
>
> Most likely, the "auto eth0" entry is making the system try to bring up the
> interface too early...in one case I removed that line, and boot returned to
> normal; it will still come up automatically later if you have ifplugd and/or
> some kind of n
H.S. wrote:
>After the upgrade(I recall hotplug was uninstalled
>and udev upgraded), the laptop boot process now stalls at the
>"Configuring network interfaces ..." step. Any idea what could be the
>problem?
I had a similar problem...
>~# cat /etc/network/interfa
On 10/15/05, H. S. <[EMAIL PROTECTED]> wrote:
On 10/15/05, Derek Broughton <
[EMAIL PROTECTED]> wrote:
I can't help with guessnet, but I wonder why you think ifplugd could be
I don't know for sure. But in the past, I had a similar problem (boot
stall) and the problem was solved by putting HOTPLUG_
On 10/15/05, Derek Broughton <[EMAIL PROTECTED]> wrote:
I can't help with guessnet, but I wonder why you think ifplugd could be
I don't know for sure. But in the past, I had a similar problem (boot
stall) and the problem was solved by putting HOTPLUG_INTERFACES="eth0"
in /etc/default/ifplugd.
in
H.S. wrote:
> Hi,
>
> I just dist-upgraded a Dell Inspiron 5160 that was running 2.6.12 kernel
> and Debian Unstable. After the upgrade(I recall hotplug was uninstalled
> and udev upgraded), the laptop boot process now stalls at the
> "Configuring network interfaces .
Hi,
I just dist-upgraded a Dell Inspiron 5160 that was running 2.6.12 kernel
and Debian Unstable. After the upgrade(I recall hotplug was uninstalled
and udev upgraded), the laptop boot process now stalls at the
"Configuring network interfaces ..." step. Any idea what could be the
p
On Mon, Sep 10, 2001 at 05:03:12PM +0200, Chris Halls wrote:
> On Tue, Sep 11, 2001 at 12:09:11AM +1000, Drew Parsons wrote:
> > The thing I'd find autodetection useful for is shuffling /etc/exim.conf
> > around, one configuration for dialup (setting the ISP's SMTP server as
> > mailserver, to avoi
On Mon, Sep 10, 2001 at 05:03:12PM +0200, Chris Halls wrote:
> On Tue, Sep 11, 2001 at 12:09:11AM +1000, Drew Parsons wrote:
> > The thing I'd find autodetection useful for is shuffling /etc/exim.conf
> > around, one configuration for dialup (setting the ISP's SMTP server as
> > mailserver, to avo
On Mon, 10 Sep 2001, Daniel Pittman wrote:
>
> On Mon, 10 Sep 2001, Werner Heuser wrote:
> >> know intuitively and I think thje other is discover. There is at
> >> least two more.
> > `divine' and maybe some of the ARP packages.
>
> `whereami', which is a suite to detect and configure the network.
On Tue, Sep 11, 2001 at 12:09:11AM +1000, Drew Parsons wrote:
> On Mon, Sep 10, 2001 at 04:55:30PM +1000, Daniel Pittman wrote:
> > `whereami', which is a suite to detect and configure the network.
> > Probably requires a little more scripting knowledge than some of the
> > others, though.
> >
>
On Mon, 10 Sep 2001, Daniel Pittman wrote:
>
> On Mon, 10 Sep 2001, Werner Heuser wrote:
> >> know intuitively and I think thje other is discover. There is at
> >> least two more.
> > `divine' and maybe some of the ARP packages.
>
> `whereami', which is a suite to detect and configure the network.
On Mon, Sep 10, 2001 at 04:55:30PM +1000, Daniel Pittman wrote:
> On Mon, 10 Sep 2001, Werner Heuser wrote:
> >> know intuitively and I think thje other is discover. There is at
> >> least two more.
> > `divine' and maybe some of the ARP packages.
>
> `whereami', which is a suite to detect and con
On Tue, Sep 11, 2001 at 12:09:11AM +1000, Drew Parsons wrote:
> On Mon, Sep 10, 2001 at 04:55:30PM +1000, Daniel Pittman wrote:
> > `whereami', which is a suite to detect and configure the network.
> > Probably requires a little more scripting knowledge than some of the
> > others, though.
> >
>
On Mon, Sep 10, 2001 at 04:55:30PM +1000, Daniel Pittman wrote:
> On Mon, 10 Sep 2001, Werner Heuser wrote:
> >> know intuitively and I think thje other is discover. There is at
> >> least two more.
> > `divine' and maybe some of the ARP packages.
>
> `whereami', which is a suite to detect and co
On Mon, 2001-09-10 at 22:35, Hugo van der Merwe wrote:
>
> (discover is a hardware detection system. Don't think it does network
> environment detection too... I know there are others, also don't
> remember what they are.)
divine does network environment detection, as does intuitively. I
maintai
On Sun, Sep 09, 2001 at 11:13:33PM -0700, Sean 'Shaleh' Perry wrote:
> There are several packages in Debian currently which attempt to figure out
> which network you are own and configure your ethernet device accordingly. I
> know intuitively and I think thje other is discover. There is at least
On Mon, 2001-09-10 at 22:35, Hugo van der Merwe wrote:
>
> (discover is a hardware detection system. Don't think it does network
> environment detection too... I know there are others, also don't
> remember what they are.)
divine does network environment detection, as does intuitively. I
mainta
On Sun, Sep 09, 2001 at 11:13:33PM -0700, Sean 'Shaleh' Perry wrote:
> There are several packages in Debian currently which attempt to figure out
> which network you are own and configure your ethernet device accordingly. I
> know intuitively and I think thje other is discover. There is at least
On Mon, 10 Sep 2001, Werner Heuser wrote:
>> know intuitively and I think thje other is discover. There is at
>> least two more.
> `divine' and maybe some of the ARP packages.
`whereami', which is a suite to detect and configure the network.
Probably requires a little more scripting knowledge than
> know intuitively and I think thje other is discover. There is at least two
> more.
`divine' and maybe some of the ARP packages.
Werner
--
|=| Werner Heuser = Keplerstr. 11A = D-10589 Berlin = Germany
|=| <[EMAIL PROTECTED]> T. +49-30-3495386
|=| http://MobiliX.org Linux-Mobile
There are several packages in Debian currently which attempt to figure out
which network you are own and configure your ethernet device accordingly. I
know intuitively and I think thje other is discover. There is at least two
more.
On Mon, 10 Sep 2001, Werner Heuser wrote:
>> know intuitively and I think thje other is discover. There is at
>> least two more.
> `divine' and maybe some of the ARP packages.
`whereami', which is a suite to detect and configure the network.
Probably requires a little more scripting knowledge tha
> know intuitively and I think thje other is discover. There is at least two
> more.
`divine' and maybe some of the ARP packages.
Werner
--
|=| Werner Heuser = Keplerstr. 11A = D-10589 Berlin = Germany
|=| <[EMAIL PROTECTED]> T. +49-30-3495386
|=| http://MobiliX.org Linux-Mobil
There are several packages in Debian currently which attempt to figure out
which network you are own and configure your ethernet device accordingly. I
know intuitively and I think thje other is discover. There is at least two
more.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Hello,
I was wondering what happened to "pcnetconfig" that used to be in the
pcmcia-cs package? What is the simplest way to set up networking now?
Ideally, I would like a way that works with both normal (desktop)
networking and pcmcia... but this isn't a necessity. (I am currently
using etherconf
Hello,
I was wondering what happened to "pcnetconfig" that used to be in the
pcmcia-cs package? What is the simplest way to set up networking now?
Ideally, I would like a way that works with both normal (desktop)
networking and pcmcia... but this isn't a necessity. (I am currently
using etherconf
33 matches
Mail list logo
