On Tue, May 18, 2010 at 1:45 PM, Joe(theWordy)Philbrook <jtwdyp@ttlc.net> wrote:
>
> Currently my pc is a laptop. I don't use a wireless interface. I
> connect to the Internet via cable broadband with a wired Ethernet
> connection and DHCP... This id very reliable. I can usually disconnect
> the laptop from the Ethernet cable and bring it into the livingroom
> for various offline use. Then when I bring it back to my desk, all I
> usually have to to is plug the Ethernet cable back in and wait a few
> seconds and the Internet will start to work again.
>
> BUT that is contingent on the Ethernet cable having been connected
> during boot up. So if for example I were to boot up my laptop in the
> livingroom where there isn't an Ethernet connection the boot process
> will delay at the point where it's screen message says its starting
> the network. Then it says it failed and continues setting everything
> else up.
>
> At this point, if I bring the laptop back to the desk, and plug in the
> Ethernet cable, it doesn't automatically connect. I tried:
>
> # ifconfig eth0 up
>
> but ping still doesn't find my ISP
>
> What am I missing????

Your dhcp process didn't start either, so you need to start one of
those. Something as simple as `dhcpcd -i eth0` might work.

-Dan

Man, I don't that's the point, but here I need to do this:

ifconfig eth0 0.0.0.0
--
*
R*afael *C*orreia


2010/5/18 Joe(theWordy)Philbrook <jtwdyp@ttlc.net>

>
> Currently my pc is a laptop. I don't use a wireless interface. I
> connect to the Internet via cable broadband with a wired Ethernet
> connection and DHCP... This id very reliable. I can usually disconnect
> the laptop from the Ethernet cable and bring it into the livingroom
> for various offline use. Then when I bring it back to my desk, all I
> usually have to to is plug the Ethernet cable back in and wait a few
> seconds and the Internet will start to work again.
>
> BUT that is contingent on the Ethernet cable having been connected
> during boot up. So if for example I were to boot up my laptop in the
> livingroom where there isn't an Ethernet connection the boot process
> will delay at the point where it's screen message says its starting
> the network. Then it says it failed and continues setting everything
> else up.
>
> At this point, if I bring the laptop back to the desk, and plug in the
> Ethernet cable, it doesn't automatically connect. I tried:
>
> # ifconfig eth0 up
>
> but ping still doesn't find my ISP
>
> What am I missing????
>
> --
> | ~^~ ~^~
> | <?> <?> Joe (theWordy) Philbrook
> | ^ J(tWdy)P
> | \___/ <<jtwdyp@ttlc.net>>
>
>

On May 18, 2010, at 1:53 PM, Dan McGee <dpmcgee@gmail.com> wrote:

> On Tue, May 18, 2010 at 1:45 PM, Joe(theWordy)Philbrook <jtwdyp@ttlc.net
> > wrote:
>>
>> Currently my pc is a laptop. I don't use a wireless interface. I
>> connect to the Internet via cable broadband with a wired Ethernet
>> connection and DHCP... This id very reliable. I can usually
>> disconnect
>> the laptop from the Ethernet cable and bring it into the livingroom
>> for various offline use. Then when I bring it back to my desk, all I
>> usually have to to is plug the Ethernet cable back in and wait a few
>> seconds and the Internet will start to work again.
>>
>> BUT that is contingent on the Ethernet cable having been connected
>> during boot up. So if for example I were to boot up my laptop in the
>> livingroom where there isn't an Ethernet connection the boot process
>> will delay at the point where it's screen message says its starting
>> the network. Then it says it failed and continues setting everything
>> else up.
>>
>> At this point, if I bring the laptop back to the desk, and plug in
>> the
>> Ethernet cable, it doesn't automatically connect. I tried:
>>
>> # ifconfig eth0 up
>>
>> but ping still doesn't find my ISP
>>
>> What am I missing????
>
> Your dhcp process didn't start either, so you need to start one of
> those. Something as simple as `dhcpcd -i eth0` might work.
>
> -Dan

You may need to modprobe the module for your Ethernet card. Try lsmod
to get it's name.

Um should he just /etc/rc.d/network restart? That performs everything that
happens when the network interface is brought up on system start.

Kaiting.

On Tue, May 18, 2010 at 5:57 PM, <woldra@fsfe.org> wrote:

> On 2010-05-18 20:45, Joe(theWordy)Philbrook wrote:
>
>> Currently my pc is a laptop. I don't use a wireless interface. I
>> connect to the Internet via cable broadband with a wired Ethernet
>> connection and DHCP... This id very reliable. I can usually disconnect
>> the laptop from the Ethernet cable and bring it into the livingroom
>> for various offline use. Then when I bring it back to my desk, all I
>> usually have to to is plug the Ethernet cable back in and wait a few
>> seconds and the Internet will start to work again.
>>
>> BUT that is contingent on the Ethernet cable having been connected
>> during boot up. So if for example I were to boot up my laptop in the
>> livingroom where there isn't an Ethernet connection the boot process
>> will delay at the point where it's screen message says its starting
>> the network. Then it says it failed and continues setting everything
>> else up.
>>
>> At this point, if I bring the laptop back to the desk, and plug in the
>> Ethernet cable, it doesn't automatically connect. I tried:
>>
>> # ifconfig eth0 up
>>
>> but ping still doesn't find my ISP
>>
>> What am I missing????
>>
>>
>>
> ifplugd is your friend .... it detects the calble being plugged in and
> brings the interface up.
>
>


--
Kiwis and Limes: http://kaitocracy.blogspot.com/

I see I've never heard of ifplugd but it looks like the best solution. What
I was referring to was that /etc/rc.d/network restart is preferable to
ifconfig in that it will start up dhcpcd for you.

Kaiting.

On Tue, May 18, 2010 at 6:32 PM, <woldra@fsfe.org> wrote:

> Hi
>
>
> Um should he just /etc/rc.d/network restart? That performs everything that
>> happens when the network interface is brought up on system start.
>>
>>
> sure you can do that, but why not let the little tool do that for you? A
> little automagic doesn't harm as long as you know whats going on
> Apart from that ifplugd just controls one interface where the network
> script starts/stops the whole networking (including 127.0.0.1)...
>
>
>


--
Kiwis and Limes: http://kaitocracy.blogspot.com/

On 18 May 2010 12:45, Joe(theWordy)Philbrook <jtwdyp@ttlc.net> wrote:
>
> Currently my pc is a laptop. I don't use a wireless interface. I
> connect to the Internet via cable broadband with a wired Ethernet
> connection and DHCP... This id very reliable. I can usually disconnect
> the laptop from the Ethernet cable and bring it into the livingroom
> for various offline use. Then when I bring it back to my desk, all I
> usually have to to is plug the Ethernet cable back in and wait a few
> seconds and the Internet will start to work again.
>
> BUT that is contingent on the Ethernet cable having been connected
> during boot up. So if for example I were to boot up my laptop in the
> livingroom where there isn't an Ethernet connection the boot process
> will delay at the point where it's screen message says its starting
> the network. Then it says it failed and continues setting everything
> else up.
>
> At this point, if I bring the laptop back to the desk, and plug in the
> Ethernet cable, it doesn't automatically connect. I tried:
>
> # ifconfig eth0 up
>
> but ping still doesn't find my ISP
>
> What am I missing????
>
> --
> | *~^~ * ~^~
> | *<?> * <?> * * * Joe (theWordy) Philbrook
> | * * *^ * * * * * * * *J(tWdy)P
> | * *\___/ * * * * <<jtwdyp@ttlc.net>>
>
>

http://wiki.archlinux.org/index.php/Netcfg#net-auto-wired

--
Tavian Barnes