[gentoo-user] DHCP on my wireless card

[gentoo-user] DHCP on my wireless card

[Randy Barlow]

Howdy all!  I'm having a tough time getting DHCP to work on my wireless card.  
It's the intel 2200, and I am using wpa_supplicant with it.  The contents of 
my /etc/conf.d/net are:

modules=( "wpa_supplicant" )
config_eth1=( "dhcp" )
wpa_supplicant_eth1="-Dwext"

The problem seems to be that DHCP isn't being used, and the even weirder part 
is that when I bring eth1 up via /etc/init.d/net.eth1 start, ifconfig will 
show eth1 configured with an IPv6 address!  /var/log/messages isn't helpful, 
except to point out that there are no ipv6 routers on my network (duh!).  
When I manually run dhcpcd eth1, then the ip address is obtained correctly 
and it works.  What should I check to see why DHCP doesn't seem to be being 
used on this interface and why I'm getting an IPv6 address?  Thanks!

R
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP on my wireless card

[Sascha Hlusiak]

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

Randy Barlow schrieb:
> Howdy all!  I'm having a tough time getting DHCP to work on my wireless card.  
> It's the intel 2200, and I am using wpa_supplicant with it.  The contents of 
> my /etc/conf.d/net are:
>
> modules=( "wpa_supplicant" )
> config_eth1=( "dhcp" )
> wpa_supplicant_eth1="-Dwext"
>
> The problem seems to be that DHCP isn't being used, and the even weirder part 
> is that when I bring eth1 up via /etc/init.d/net.eth1 start, ifconfig will 
> show eth1 configured with an IPv6 address!  /var/log/messages isn't helpful, 
> except to point out that there are no ipv6 routers on my network (duh!).  
> When I manually run dhcpcd eth1, then the ip address is obtained correctly 
> and it works.  What should I check to see why DHCP doesn't seem to be being 
> used on this interface and why I'm getting an IPv6 address?  Thanks!
>   
With wpa_supplicant the script is run 2 times. Once by you which fires
up wpa_supplicant and once by wpa_cli.sh, which puts up the interface
and runs dhcpcd.
I had this problem once too, and my problem was that a file
/etc/conf.d/net.eth1 existed, which had config_eth1=("null") in it. The
statements in /etc/conf.d/net had no effect then. Maybe that's the same
issue here.

- Sascha


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: [gentoo-user] DHCP on my wireless card

[Randy Barlow]

On Thursday 31 May 2007 14:52, Sascha Hlusiak wrote:
> I had this problem once too, and my problem was that a file
> /etc/conf.d/net.eth1 existed, which had config_eth1=("null") in it. The
> statements in /etc/conf.d/net had no effect then. Maybe that's the same
> issue here.

No, that file doesn't exist on my system.  I filed a bug report about this so 
we'll see if that helps.  Any other ideas?

R
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP on my wireless card

[Sascha Hlusiak]

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


>  and why I'm getting an IPv6 address?  Thanks!
>   
Every link that is up gets a link-local ipv6 address which is used to
find and communicate with direct link partners. It probably starts with
fe80::. So don't worry, that's caused by the ipv6 module and you don't
"get" it, you basically just have it.

Sascha



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: [gentoo-user] DHCP on my wireless card

[Mick]

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

On Thursday 31 May 2007 20:55, Sascha Hlusiak wrote:
> >  and why I'm getting an IPv6 address?  Thanks!
>
> Every link that is up gets a link-local ipv6 address which is used to
> find and communicate with direct link partners. It probably starts with
> fe80::. So don't worry, that's caused by the ipv6 module and you don't
> "get" it, you basically just have it.

You can switch off IPv6 in the kernel.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] DHCP on my wireless card

[Randy Barlow]

On Friday 01 June 2007 04:10, Mick wrote:
> You can switch off IPv6 in the kernel.

I can, but I don't think that will solve the problem that I'm seeing.  Other 
ideas?

-- 
Randy Barlow
http://www.electronsweatshop.com
"Oh me of little faith..."
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP on my wireless card

[Randy Barlow]

On Thursday 31 May 2007 12:05, Randy Barlow wrote:
> Howdy all!  I'm having a tough time getting DHCP to work on my wireless
> card. It's the intel 2200, and I am using wpa_supplicant with it.  The
> contents of my /etc/conf.d/net are:

I've filed a bug report about this problem with a few more details at 
http://bugs.gentoo.org/show_bug.cgi?id=180487  I'll repeat the text I posted 
there here so if anyone can help I would be very grateful!

I am using the intel 2200 wireless card with the in-kernel driver and the
firmware from portage, as well as wpa_supplicant.  When I run the init script
to start the network interface, it reports normally:

lappy786 ~ # /etc/init.d/net.eth1 start
 * Starting eth1
 *   Starting wpa_supplicant on eth1 ...                                  [ok]
 *   Starting wpa_cli on eth1 ...                                         [ok]
 *     Backgrounding ...

However, it seems to get stuck somewhere in the backgrounded stage because the
interface doesn't come up and I don't get an IP address.

lappy786 ~ # /etc/init.d/net.eth1 status
 * status:  inactive
lappy786 ~ # /etc/init.d/net.eth1 start
 * WARNING:  net.eth1 has already been started.
lappy786 ~ # ifconfig
eth1      Link encap:Ethernet  HWaddr 00:0E:35:13:2B:A0
          inet6 addr: fe80::20e:35ff:fe13:2ba0/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:1188 dropped:1488 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:8
          collisions:0 txqueuelen:1000
          RX bytes:10960814 (10.4 Mb)  TX bytes:393094968 (374.8 Mb)
          Interrupt:11 Base address:0x6000 Memory:cffff000-cfffffff

Strangely, it seems to aquire an ipv6 address.  /var/log/messages just
contains:

May 31 15:37:27 lappy786 ADDRCONF(NETDEV_UP): eth1: link is not ready
May 31 15:37:28 lappy786 ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 31 15:37:38 lappy786 eth1: no IPv6 routers present

It does correctly associate with my AP, and I can manually run dhcpcd eth1 to
get an IP address and use the network (how I am writing this bug report!) 
However, other services (such as sshd) that depend on the network will not
start since the init script doesn't think it finished.

My /etc/conf.d/net contains:

modules=( "wpa_supplicant" )
wpa_supplicant_eth1="-Dwext"

And my /etc/wpa_supplicant/wpa_supplicant.conf contains:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

ap_scan=1

network={
  ssid="youThink"
  psk="wouldntYouLikeToKnow"
  priority=5
}

network={
  ssid="ncsu"
  key_mgmt=NONE
}

I am using baselayout version 1.12.9-r2 and wpa_supplicant version 0.5.7.  I
have found a lot of bug reports similar to this, but they are all for 
different
versions of baselayout or wpa_supplicant, and the fixes specified by them
haven't seemed to work.  I do apologize if this turns out to be a duplicate,
but I promise that I spent a fair amount of time reading the related reports
and trying things!  Let me know if there is any additional information I can
offer!

Reproducible: Always

-- 
Randy Barlow
http://www.electronsweatshop.com
"Oh me of little faith..."
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP on my wireless card

[Etaoin Shrdlu]

I can not help you with your problem, but...

On Friday 1 June 2007 18:57, Randy Barlow wrote:

> Strangely, it seems to aquire an ipv6 address.  

The ipv6 address you see is the so-called link-local address, and is 
automatically constructed by the network adapter based on its MAC 
address; hence, it's not "acquired" from some server, and so it's 
perfectly normal that, even though there are other connectivity 
problems, the network adapter has this kind of ipv6 address.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP on my wireless card

[Randy Barlow]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Etaoin Shrdlu wrote:
> The ipv6 address you see is the so-called link-local address, and is 
> automatically constructed by the network adapter based on its MAC 
> address; hence, it's not "acquired" from some server, and so it's 
> perfectly normal that, even though there are other connectivity 
> problems, the network adapter has this kind of ipv6 address.

Thanks for your reply!

R
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGYFSq7So1xaF/eR8RAqCwAJ4vb1r2k6BDQqHzYFEeGB4crtcyeACeJD6s
u+Hqluq8dw2FRd88IU0KyAM=
=ehvL
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP on my wireless card

[Mick]

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

On Friday 01 June 2007 17:57, Randy Barlow wrote:
> On Thursday 31 May 2007 12:05, Randy Barlow wrote:
[snip...]
>           RX packets:4 errors:1188 dropped:1488 overruns:0 frame:0
>           TX packets:3 errors:0 dropped:0 overruns:0 carrier:8
>           collisions:0 txqueuelen:1000
>           RX bytes:10960814 (10.4 Mb)  TX bytes:393094968 (374.8 Mb)
>           Interrupt:11 Base address:0x6000 Memory:cffff000-cfffffff

I'm afraid that I can't really help either, but it is clear from the number of 
received packet errors and dropped packets received that something is amiss 
big time.  Having suffered similarly in the past (with different hardware) 
I'd say that the problem is with the driver.

Good luck.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] DHCP on my wireless card

[Alex Prinsier]

Randy Barlow wrote:
> lappy786 ~ # /etc/init.d/net.eth1 start
>  * Starting eth1
>  *   Starting wpa_supplicant on eth1 ...                                  [ok]
>  *   Starting wpa_cli on eth1 ...                                         [ok]
>  *     Backgrounding ...
> 
> However, it seems to get stuck somewhere in the backgrounded stage because the
> interface doesn't come up and I don't get an IP address.

How sure are you that wpa_supplicant is able to connect to your access
point? It can only do ip stuff (like acquiring an ip) once it's
connected (associated) to your ap.

Run wpa_gui to verify.

Alex
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP on my wireless card

[Mick]

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

On Friday 01 June 2007 19:28, Alex Prinsier wrote:
> Randy Barlow wrote:
> > lappy786 ~ # /etc/init.d/net.eth1 start
> >  * Starting eth1
> >  *   Starting wpa_supplicant on eth1 ...                                 
> > [ok] *   Starting wpa_cli on eth1 ...                                    
> >     [ok] *     Backgrounding ...
> >
> > However, it seems to get stuck somewhere in the backgrounded stage
> > because the interface doesn't come up and I don't get an IP address.
>
> How sure are you that wpa_supplicant is able to connect to your access
> point? It can only do ip stuff (like acquiring an ip) once it's
> connected (associated) to your ap.
>
> Run wpa_gui to verify.

Somebody re-emerged wpa_supplicant earlier today and fixed his problem (second 
time round) - did you try it at all?

-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] DHCP on my wireless card

[Randy Barlow]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Prinsier wrote:
> How sure are you that wpa_supplicant is able to connect to your access
> point? It can only do ip stuff (like acquiring an ip) once it's
> connected (associated) to your ap.
> 
> Run wpa_gui to verify.

I am very sure that it is able, since after calling dhcpcd eth1 manually
I can browse the internet and do other networky type things.  wpa_gui
gives the status 4_WAY_HANDSHAKE until I give this command manually, and
then it says ASSOCIATED.  Interestingly enough, however, I frequently
see Last Message as "Diconnected" for a very brief period, and then it
will say "Associated with <MAC address>"

Another strange thing that I have noticed is that when I try to ping my
laptop from another machine, it sometimes works and sometimes does not.
 It seems that using the laptop to ping the other machine first helps
for some reason, but that may also just be coincidence.

Mick wrote:
>> On Thursday 31 May 2007 12:05, Randy Barlow wrote:
> [snip...]
>>           RX packets:4 errors:1188 dropped:1488 overruns:0 frame:0
>>           TX packets:3 errors:0 dropped:0 overruns:0 carrier:8
>>           collisions:0 txqueuelen:1000
>>           RX bytes:10960814 (10.4 Mb)  TX bytes:393094968 (374.8 Mb)
>>           Interrupt:11 Base address:0x6000 Memory:cffff000-cfffffff
> 
> I'm afraid that I can't really help either, but it is clear from the number of 
> received packet errors and dropped packets received that something is amiss 
> big time.  Having suffered similarly in the past (with different hardware) 
> I'd say that the problem is with the driver.

I agree that something is really wrong here, and the interesting thing
that I've noted is that the errors are always in RX packets and never in
TX packets.  I'm using the kernel provided driver for the Intel 2200.
Perhaps I will try removing encryption from my network temporarily to
see if that helps with the packet errors or not.  This might be a good
test to see if it is a driver problem or if it is an encryption problem
(is the driver involved at all in the encryption, or is that done
outside of the driver code?)

Mick wrote:
> Somebody re-emerged wpa_supplicant earlier today and fixed his problem (second 
> time round) - did you try it at all?

I did just try this and it didn't work, but thanks for the suggestion!

Randy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGYVx17So1xaF/eR8RAs42AKCyZmmVsZh2hrpNNMS5gUm3XSR/3gCfciFN
Tbx26N2bQg7epGzBaqBa2cE=
=tWLq
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list