-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
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
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...
--
[EMAIL PROTECTED] mailing list
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
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;
-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,
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
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
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] *
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
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
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
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
13 matches
Mail list logo
