[gentoo-user] why a manual dhcpcd eth0 is needed?

[gentoo-user] why a manual dhcpcd eth0 is needed?

[Valmor de Almeida]

Hello,

On a recent gentoo install using wicd for network configuration, no
connection is established during boot. After logging in, I need to issue

  dhcpcd eth0

to obtain an IP address and access the internet via ethernet. I thought
wicd would take care of that. I did not emerge dhcpcd, it was emerged as
a dependency of wicd.

What am I missing? I have wicd starting during the boot runlevel.

Thanks for inputs.

--
Valmor

[gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Nikos Chantziaras]

On 10/22/2011 08:08 AM, Valmor de Almeida wrote:
>
> Hello,
>
> On a recent gentoo install using wicd for network configuration, no
> connection is established during boot. After logging in, I need to issue
>
>    dhcpcd eth0
>
> to obtain an IP address and access the internet via ethernet. I thought
> wicd would take care of that. I did not emerge dhcpcd, it was emerged as
> a dependency of wicd.
>
> What am I missing? I have wicd starting during the boot runlevel.

You probably don't have a correct /etc/conf.d/net file.  Try:

   modules="dhcpcd"
   config_eth0="dhcp"

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Valmor de Almeida]

On 10/22/2011 02:18 AM, Nikos Chantziaras wrote:
> On 10/22/2011 08:08 AM, Valmor de Almeida wrote:
>>
>> Hello,
>>
>> On a recent gentoo install using wicd for network configuration, no
>> connection is established during boot. After logging in, I need to issue
>>
>>    dhcpcd eth0
>>
>> to obtain an IP address and access the internet via ethernet. I thought
>> wicd would take care of that. I did not emerge dhcpcd, it was emerged as
>> a dependency of wicd.
>>
>> What am I missing? I have wicd starting during the boot runlevel.
> 
> You probably don't have a correct /etc/conf.d/net file.  Try:
> 
>    modules="dhcpcd"
>    config_eth0="dhcp"
> 
> 
I have other gentoo laptops/machines and I typically leave this file
empty. They all work with wicd in wired and wireless mode.

--
Valmor

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Alan McKinnon]

On Sat, 22 Oct 2011 10:13:53 -0400
Valmor de Almeida <val.gentoo@gmail.com> wrote:

> On 10/22/2011 02:18 AM, Nikos Chantziaras wrote:
> > On 10/22/2011 08:08 AM, Valmor de Almeida wrote:
> >>
> >> Hello,
> >>
> >> On a recent gentoo install using wicd for network configuration, no
> >> connection is established during boot. After logging in, I need to
> >> issue
> >>
> >>    dhcpcd eth0
> >>
> >> to obtain an IP address and access the internet via ethernet. I
> >> thought wicd would take care of that. I did not emerge dhcpcd, it
> >> was emerged as a dependency of wicd.
> >>
> >> What am I missing? I have wicd starting during the boot runlevel.
> > 
> > You probably don't have a correct /etc/conf.d/net file.  Try:
> > 
> >    modules="dhcpcd"
> >    config_eth0="dhcp"
> > 
> > 
> I have other gentoo laptops/machines and I typically leave this file
> empty. They all work with wicd in wired and wireless mode.

Correct.

wicd does not use /etc/conf.d/net at all, it has it's own mechanisms.

/etc/conf.d/net is used by the Gentoo network scripts, an entirely
different thing from wicd




-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Valmor de Almeida]

On 10/22/2011 02:18 PM, Alan McKinnon wrote:
> On Sat, 22 Oct 2011 10:13:53 -0400
> Valmor de Almeida <val.gentoo@gmail.com> wrote:
> 
>> On 10/22/2011 02:18 AM, Nikos Chantziaras wrote:
>>> On 10/22/2011 08:08 AM, Valmor de Almeida wrote:
>>>>
>>>> Hello,
>>>>
>>>> On a recent gentoo install using wicd for network configuration, no
>>>> connection is established during boot. After logging in, I need to
>>>> issue
>>>>
>>>>    dhcpcd eth0
>>>>
>>>> to obtain an IP address and access the internet via ethernet. I
>>>> thought wicd would take care of that. I did not emerge dhcpcd, it
>>>> was emerged as a dependency of wicd.
>>>>
>>>> What am I missing? I have wicd starting during the boot runlevel.
>>>
>>> You probably don't have a correct /etc/conf.d/net file.  Try:
>>>
>>>    modules="dhcpcd"
>>>    config_eth0="dhcp"
>>>
>>>
>> I have other gentoo laptops/machines and I typically leave this file
>> empty. They all work with wicd in wired and wireless mode.
> 
> Correct.
> 
> wicd does not use /etc/conf.d/net at all, it has it's own mechanisms.
> 
> /etc/conf.d/net is used by the Gentoo network scripts, an entirely
> different thing from wicd
> 
> 
> 
> 
Any inputs on why I need to issue

 dhcpcd eth0

for this particular install. The ethernet card is Broadcom NetXtreme
BCM5764M Gigabit Ethernet PCIe. I have the right driver built into the
kernel. All works but as I said, wicd does work from boot. After logging
in I need to get an IP address manually.

Don't know what I am missing.

Thanks,

--
Valmor

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

On Sat, 22 Oct 2011 17:51:11 -0400, Valmor de Almeida wrote:

> for this particular install. The ethernet card is Broadcom NetXtreme
> BCM5764M Gigabit Ethernet PCIe. I have the right driver built into the
> kernel. All works but as I said, wicd does work from boot. After logging
> in I need to get an IP address manually.

What happens if you try to connect from the Wicd client after booting?


-- 
Neil Bothwick

Q-Tip: When an omnipotent alien gives you advice.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Valmor de Almeida]

On 10/23/2011 03:21 PM, Neil Bothwick wrote:
> On Sat, 22 Oct 2011 17:51:11 -0400, Valmor de Almeida wrote:
> 
>> for this particular install. The ethernet card is Broadcom NetXtreme
>> BCM5764M Gigabit Ethernet PCIe. I have the right driver built into the
>> kernel. All works but as I said, wicd does work from boot. After logging
>> in I need to get an IP address manually.
> 
> What happens if you try to connect from the Wicd client after booting?
> 
> 
I tried

 -> wicd-cli --wired
 No operation peformed.

So no luck there.

As soon as I do a manual

 dhcpcd eth0

I get an IP address and all work.

I don't have wireless working yet; need to check on the driver (wireless
is also broadcom). So

  wicd-client -n

finds no wireless network.

Thanks,

--
Valmor

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1383 bytes --]

On Sunday 23 Oct 2011 21:01:23 Valmor de Almeida wrote:
> On 10/23/2011 03:21 PM, Neil Bothwick wrote:
> > On Sat, 22 Oct 2011 17:51:11 -0400, Valmor de Almeida wrote:
> >> for this particular install. The ethernet card is Broadcom NetXtreme
> >> BCM5764M Gigabit Ethernet PCIe. I have the right driver built into the
> >> kernel. All works but as I said, wicd does work from boot. After logging
> >> in I need to get an IP address manually.
> > 
> > What happens if you try to connect from the Wicd client after booting?
> 
> I tried
> 
>  -> wicd-cli --wired
>  No operation peformed.
> 
> So no luck there.
> 
> As soon as I do a manual
> 
>  dhcpcd eth0
> 
> I get an IP address and all work.

I assume you have no ifplugd installed - but from what I undestand wicd works 
in a similar fashion (i.e. it runs dhcpcd) - so I can't really explain this.

What do you get in /var/log/messages when you run /etc/init.d/net.eth0 start.  
It should start dhcpcd by default (even without a /etc/conf.d/net).

> I don't have wireless working yet; need to check on the driver (wireless
> is also broadcom). So
> 
>   wicd-client -n
> 
> finds no wireless network.

You'll probably need to install b43-fwcutter and follow the instructions here 
(depending on your wireless NIC):

  http://linuxwireless.org/en/users/Drivers/b43

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Valmor de Almeida]

On 10/23/2011 05:19 PM, Mick wrote:
> On Sunday 23 Oct 2011 21:01:23 Valmor de Almeida wrote:
>> On 10/23/2011 03:21 PM, Neil Bothwick wrote:
>>> On Sat, 22 Oct 2011 17:51:11 -0400, Valmor de Almeida wrote:
>>>> for this particular install. The ethernet card is Broadcom NetXtreme
>>>> BCM5764M Gigabit Ethernet PCIe. I have the right driver built into the
>>>> kernel. All works but as I said, wicd does work from boot. After logging
>>>> in I need to get an IP address manually.
>>>
>>> What happens if you try to connect from the Wicd client after booting?
>>
>> I tried
>>
>>  -> wicd-cli --wired
>>  No operation peformed.
>>
>> So no luck there.
>>
>> As soon as I do a manual
>>
>>  dhcpcd eth0
>>
>> I get an IP address and all work.
> 
> I assume you have no ifplugd installed - but from what I undestand wicd works 
> in a similar fashion (i.e. it runs dhcpcd) - so I can't really explain this.

Correct. I don't have ifplugd.

> 
> What do you get in /var/log/messages when you run /etc/init.d/net.eth0 start.  
> It should start dhcpcd by default (even without a /etc/conf.d/net).

I don't have net.eth0 (I deleted it per wicd installation instructions).
My other machines that use wicd do not have it either and they all work.
Don't seem to find the difference between what I have working and this
MacBook Pro I put Gentoo on wherein wicd will not work out of the box.

> 
>> I don't have wireless working yet; need to check on the driver (wireless
>> is also broadcom). So
>>
>>   wicd-client -n
>>
>> finds no wireless network.
> 
> You'll probably need to install b43-fwcutter and follow the instructions here 
> (depending on your wireless NIC):
> 
>   http://linuxwireless.org/en/users/Drivers/b43

Thanks,

--
Valmor

> 

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 576 bytes --]

On Sun, 23 Oct 2011 17:35:45 -0400, Valmor de Almeida wrote:

> I don't have net.eth0 (I deleted it per wicd installation instructions).
> My other machines that use wicd do not have it either and they all work.
> Don't seem to find the difference between what I have working and this
> MacBook Pro I put Gentoo on wherein wicd will not work out of the box.

Have you tried diffing /etc/wicd/wired-settings.conf from the working and
non-working systems.

Is eth0 actually present at this time?


-- 
Neil Bothwick

I get enough exercise just pushing my luck.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Valmor de Almeida]

On 10/23/2011 06:45 PM, Neil Bothwick wrote:
> On Sun, 23 Oct 2011 17:35:45 -0400, Valmor de Almeida wrote:
>
>> I don't have net.eth0 (I deleted it per wicd installation instructions).
>> My other machines that use wicd do not have it either and they all work.
>> Don't seem to find the difference between what I have working and this
>> MacBook Pro I put Gentoo on wherein wicd will not work out of the box.
>
> Have you tried diffing /etc/wicd/wired-settings.conf from the working and
> non-working systems.
>
> Is eth0 actually present at this time?
>
>

On my wired machine that works out of the box I have:

[wired-default]
afterscript = None
use_static_dns = False
dhcphostname = lpt1
dns3 = None
postdisconnectscript = None
dns1 = None
search_domain = None
dns_domain = None
lastused = True
broadcast = None
default = 1
netmask = None
dns2 = None
beforescript = None
profilename = wired-default
predisconnectscript = None
ip = None
gateway = None
use_global_dns = False

On the machine I have to issue a manual dhcpcd eth0 I have:

[wired-default]
ip
broadcast
netmask
gateway
search_domain
dns_domain
dns1
dns2
dns3
beforescript
afterscript
predisconnectscript
postdisconnectscript
default = True
dhcphostname = mac1

Don't know whether the missing values make a difference. As far as
eth0,  at the moment after dhcpcd eth0 is issued,  it is:

mac1 wicd # ifconfig -a
eth0      Link encap:Ethernet  HWaddr xxxxxxxxxxxxxxxxxx
          inet addr:192.168.10.7  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: xxxxxxxxxxxxxxxxxxxx Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4565 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3102 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5285197 (5.0 MiB)  TX bytes:420643 (410.7 KiB)
          Interrupt:16

Before dhcpcd eth0 is issued eth0 is there, I think, but it does not
have an inet addr: assigned to it. I will need to reboot to confirm
it.

Thanks,

--
Valmor

Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

On Sun, 23 Oct 2011 22:10:59 -0400, Valmor de Almeida wrote:

> On my wired machine that works out of the box I have:
> 
> [wired-default]
[snip]

> On the machine I have to issue a manual dhcpcd eth0 I have:
> 
> [wired-default]
[snip]

> Don't know whether the missing values make a difference.

I assume you have tried using the config fro the working system on the
non-working one.


-- 
Neil Bothwick

A pessimist complains about the noise when opportunity knocks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]