search

cubieplayer / Cubian

Debian for Cubieboard
http://cubian.org
270 stars 49 forks source link

wireless #63

Closed McBodik closed 11 years ago

McBodik commented 11 years ago

Hi again. I have problems with wifi. I configure /etc/network/interfaces as wiki:

auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wireless-essid mynetwork

but when try sudo ifup wlan0 :

No DHCPOFFERS received. No working leases in persistent database - sleeping.

I have mac filter on router, but add Cubie wifi mac adress .

In router I saw non expected : http://clip2net.com/s/5Bk8ng It's all eth0. Nothing about wifi. But most surprised - all macs are diferent- why/how?

Also I can't understand why Cubian is eth0 connected when there was

auto eth0

In wiki I saw: If you absolutely don't need the wired network,plase disable this feature by comment or delete auto eth0. It is comment by default, why eth0 start working after system start?

ifconfig:

eth0 Link encap:Ethernet HWaddr 4e:e5:30:cc:06:c5
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4ce5:30ff:fecc:6c5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2119 errors:0 dropped:0 overruns:0 frame:0 TX packets:986 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:202605 (197.8 KiB) TX bytes:98022 (95.7 KiB) Interrupt:55 Base address:0xb000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr 14:cf:92:13:47:45
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

P.S. wlan0 mac isn't change after reboot… 

P.S.S. sorry for my English…

zerodamage commented 11 years ago

The eth0 MAC is auto generated, they will stay for 23 hours more as shown. Try using package wicd or NetworkManager instead of manual config (remove interfaces from etc/network/interfaces) You also need wpa-supplicant or similar for WPA networks

McBodik commented 11 years ago

It's mean /etc/network/interfaces isn't the end inet config file? If the NetworkManager have another?

McBodik commented 11 years ago

Ok, but why there is nothing about NetworkManager in wiki?

And about eht0 - but MAC is a unique identifier… I always thought - its hardware address, or is this a specific Cubieboard implementation?

cubieplayer commented 11 years ago

There is no network manager. Please take a look at http://www.debian.org/doc/manuals/debian-reference/ch05.en.html to solve the problem. If you follows the wiki, It should work.

McBodik commented 11 years ago

Ok, if there is no another network utilities, why despite #auto eth0, eth0 connects at startup?

P.S. Sorry for so many questions, I just want to understand...

zerodamage commented 11 years ago

Sorry to have indicated NetworkManager was present @cubieplayer, @McBodik , it was from my LXDE install. However i would still personally recommend using one, if the network is not very simple.

To clairfy: i know there is no manager, but i recommend using one

cubieplayer commented 11 years ago

@zerodamage cubian has no GUI, and no network manager. It uses network configuration file which is /etc/network/interfaces to config the network. If you installed LXDE, you should follow the LXDE's documentation to solve the problem.

McBodik commented 11 years ago

Ok, I try to do this manually. If I will fall, I'll install some gui. But I still don't understand how eth0 connect if auto connect is commented?

zerodamage commented 11 years ago

@McBodik I dont know why/how it does that sorry, have only been using GUI

McBodik commented 11 years ago

@zerodamage, @cubieplayer thanks for this, if I find the answer, or have something new - I'll write:)

McBodik commented 11 years ago

Hi again. I fixed my problem, but have the second. My bad because I have router and repeater with one ssid to cover a larger area, and Cubian doesn't know what to use. Now Cubian remember ap to connect, but maybe you know how can I specify MAC address to connect for feature?

mmplayer commented 11 years ago

@McBodik http://linux-sunxi.org/EMAC and http://www.debian-administration.org/article/501/Working_with_MAC_addresses

McBodik commented 11 years ago

Because I have repeater, I need to tell Cubian where is DHCP thats why

auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wireless-essid My_network_name HWaddr DHCP_MAC_address

cubieplayer commented 11 years ago

This problem might be the same with http://www.debian-administration.org/article/501/Working_with_MAC_addresses

cubieplayer commented 11 years ago

duplicated with https://github.com/cubieplayer/Cubian/issues/47