From: Valmor de Almeida <val.gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?
Date: Sun, 23 Oct 2011 22:10:59 -0400 [thread overview]
Message-ID: <CAMpmEiG0cepZZm6Tuz8Gc85x1P6_9edpLpL3Rs7hbb27oqCb4Q@mail.gmail.com> (raw)
In-Reply-To: <20111023234550.357b5bea@digimed.co.uk>
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
next prev parent reply other threads:[~2011-10-24 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 5:08 [gentoo-user] why a manual dhcpcd eth0 is needed? Valmor de Almeida
2011-10-22 6:18 ` [gentoo-user] " Nikos Chantziaras
2011-10-22 14:13 ` Valmor de Almeida
2011-10-22 18:18 ` Alan McKinnon
2011-10-22 21:51 ` Valmor de Almeida
2011-10-23 19:21 ` Neil Bothwick
2011-10-23 20:01 ` Valmor de Almeida
2011-10-23 21:19 ` Mick
2011-10-23 21:35 ` Valmor de Almeida
2011-10-23 22:45 ` Neil Bothwick
2011-10-24 2:10 ` Valmor de Almeida [this message]
2011-10-24 7:50 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMpmEiG0cepZZm6Tuz8Gc85x1P6_9edpLpL3Rs7hbb27oqCb4Q@mail.gmail.com \
--to=val.gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox