[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

problemas ao configurar máquina Debian como access point

Olá a todos,
Estou tentando configurar meu Desktop Debian (Dell Dimension, P4HT 2.8GHz, 512MB RAM rodando Debian Debian Lenny kernel 2.6.24-1-686) como um access point (usando uma placa de rede wireless Encore com chip RTL8125) com DHCP, porém não estou tendo sucesso ao conectar meu notebook nesta máquina, o notebook roda Ubuntu 8.04 que eu uso para me conectar normalmente na rede wireless do trabalho e da universidade. Ao tentar conectar usando o ícone de gerenciamento de redes do Ubuntu que mostra o meu desktop-access point como FLAVIO-CASA (como eu configurei) ele mostra o ícone de tentativa de conexão por um tempo considerável (+/-30 s) e por fim desiste 
   As configurações do access point Debian são as seguintes :

/etc/network/interfaces :
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# PPPoE connection
auto dsl-provider
iface dsl-provider inet ppp
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
provider dsl-provider

auto eth0
iface eth0 inet dhcp
#iface eth0 inet static
#address 192.168.2.1
#netmask 255.255.255.0


iface wlan0 inet static
     address 10.0.0.1
     netmask 255.0.0.0
     network 10.0.0.0
     broadcast 10.255.255.255
     wireless-mode Master
     wireless-channel 1
     wireless-key s:ABCDEFG
     wireless-essid FLAVIO-CASA

auto wlan0

E a configuração do DHCP no Debian é a seguinte :

/etc/dhcp3/dhcpd.conf :
# Set DHCPD to answer requests on the wireless interface

DHCPDARGS=wlan0;

# Set some defaults for lease time and DNS update method
ddns-update-style ad-hoc;
default-lease-time 600;
max-lease-time 7200;

# Set the subnet mask for the wireless IP network
option subnet-mask 255.255.255.0;

# Set the Broadcast address. This will be 10.x.x.255,
# the "x.x" will depend upon the network assigned to you by NZWireless.
option broadcast-address 10.255.255.255;

# Set the router address, this will be 10.x.x.1, the address
# of your wireless interface WLAN0
option routers 10.0.0.1;

# Set the Name Server address. This will be the same as your WLAN0 address
# because we intend to run DNS on this machine.
option domain-name-servers 10.0.0.1;

# Set the default domain name for clients on this network.
# i.e. the DNS domain assigned to you by your wireless administrator.
option domain-name "universolocal.org";

# Allocate a network range for dynamic IP addresses to hand out to clients.
# Again, this range will be in 10.x.x.x, depending upon the network allocated 
# to you by your wireless administrator.
subnet 10.0.0.0 netmask 255.0.0.0 {
   range 10.0.0.10 10.0.0.20;
}




   E os syslog's  das máquinas mostram o seguinte :
syslog Máquina Debian
May 15 07:50:10 universolocal kernel: New client associated: 00:17:c4:05:65:24 May 15 07:50:14 universolocal dhcpd: DHCPDISCOVER from 00:17:c4:05:65:24 via wlan0 May 15 07:50:14 universolocal dhcpd: DHCPOFFER on 10.0.0.10 to 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:16 universolocal dhcpd: DHCPDISCOVER from 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:16 universolocal dhcpd: DHCPOFFER on 10.0.0.10 to 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:20 universolocal dhcpd: DHCPDISCOVER from 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:20 universolocal dhcpd: DHCPOFFER on 10.0.0.10 to 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:25 universolocal dhcpd: DHCPDISCOVER from 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:25 universolocal dhcpd: DHCPOFFER on 10.0.0.10 to 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:34 universolocal dhcpd: DHCPDISCOVER from 00:17:c4:05:65:24 (flavio-laptop) via wlan0 May 15 07:50:34 universolocal dhcpd: DHCPOFFER on 10.0.0.10 to 00:17:c4:05:65:24 (flavio-laptop) via wlan0 


syslog Máquina Ubuntu
May 15 07:50:06 flavio-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason May 15 07:50:06 flavio-laptop NetworkManager: <debug> [1210848606.659855] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'FLAVIO-CASA' May 15 07:50:06 flavio-laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / FLAVIO-CASA May 15 07:50:06 flavio-laptop NetworkManager: <info> Deactivating device wlan0. May 15 07:50:08 flavio-laptop NetworkManager: <info> Device wlan0 activation scheduled... May 15 07:50:08 flavio-laptop NetworkManager: <info> Activation (wlan0) started... May 15 07:50:08 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... May 15 07:50:08 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... May 15 07:50:08 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... May 15 07:50:08 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. May 15 07:50:08 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... May 15 07:50:08 flavio-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'FLAVIO-CASA' is unencrypted, no key needed. May 15 07:50:09 flavio-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: response was 'OK' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: response was 'OK' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK' 
May 15 07:50:10 flavio-laptop NetworkManager: <info>  SUP: response was '0'
May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 464c4156494f2d43415341' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: response was 'OK' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: response was 'OK' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' May 15 07:50:10 flavio-laptop NetworkManager: <info> SUP: response was 'OK' May 15 07:50:10 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. May 15 07:50:11 flavio-laptop kernel: [ 118.651327] wlan0: Initial auth_alg=0 May 15 07:50:11 flavio-laptop kernel: [ 118.651333] wlan0: authenticate with AP 00:18:e7:41:3a:48 May 15 07:50:11 flavio-laptop kernel: [ 118.651912] wlan0: RX authentication from 00:18:e7:41:3a:48 (alg=0 transaction=2 status=0) 
May 15 07:50:11 flavio-laptop kernel: [  118.651915] wlan0: authenticated
May 15 07:50:11 flavio-laptop NetworkManager: <info> Supplicant state changed: 1 May 15 07:50:11 flavio-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'FLAVIO-CASA'. May 15 07:50:11 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. May 15 07:50:11 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... May 15 07:50:11 flavio-laptop kernel: [ 118.651917] wlan0: associate with AP 00:18:e7:41:3a:48 May 15 07:50:11 flavio-laptop kernel: [ 118.652808] wlan0: RX AssocResp from 00:18:e7:41:3a:48 (capab=0x401 status=0 aid=19) May 15 07:50:11 flavio-laptop kernel: [ 118.652811] wlan0: invalid aid value 19; bits 15:14 not set 
May 15 07:50:11 flavio-laptop kernel: [  118.652812] wlan0: associated
May 15 07:50:11 flavio-laptop kernel: [ 118.653507] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready May 15 07:50:12 flavio-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. May 15 07:50:12 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. May 15 07:50:12 flavio-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0 May 15 07:50:12 flavio-laptop dhclient: wmaster0: unknown hardware address type 801 May 15 07:50:12 flavio-laptop avahi-daemon[5095]: Registering new address record for fe80::217:c4ff:fe05:6524 on wlan0.*. May 15 07:50:13 flavio-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0 May 15 07:50:13 flavio-laptop dhclient: wmaster0: unknown hardware address type 801 May 15 07:50:14 flavio-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 May 15 07:50:16 flavio-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change. May 15 07:50:17 flavio-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 May 15 07:50:21 flavio-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 May 15 07:50:21 flavio-laptop kernel: [ 122.702469] wlan0: no IPv6 routers present May 15 07:50:26 flavio-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 May 15 07:50:35 flavio-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 
May 15 07:50:36 flavio-laptop pppd[4447]: Timeout waiting for PADO packets
May 15 07:50:36 flavio-laptop pppd[4447]: Unable to complete PPPoE Discovery
May 15 07:50:45 flavio-laptop dhclient: No DHCPOFFERS received.
May 15 07:50:45 flavio-laptop avahi-autoipd(wlan0)[6203]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113). May 15 07:50:45 flavio-laptop avahi-autoipd(wlan0)[6203]: Successfully called chroot(). May 15 07:50:45 flavio-laptop avahi-autoipd(wlan0)[6203]: Successfully dropped root privileges. May 15 07:50:45 flavio-laptop avahi-autoipd(wlan0)[6203]: Starting with address 169.254.3.247 May 15 07:50:50 flavio-laptop avahi-autoipd(wlan0)[6203]: Callout BIND, address 169.254.3.247 on interface wlan0 May 15 07:50:50 flavio-laptop avahi-daemon[5095]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.3.247. May 15 07:50:50 flavio-laptop avahi-daemon[5095]: New relevant interface wlan0.IPv4 for mDNS. May 15 07:50:50 flavio-laptop avahi-daemon[5095]: Registering new address record for 169.254.3.247 on wlan0.IPv4. May 15 07:50:54 flavio-laptop avahi-autoipd(wlan0)[6203]: Successfully claimed IP address 169.254.3.247 May 15 07:50:54 flavio-laptop NetworkManager: <info> DHCP daemon state is now 9 (fail) for interface wlan0 May 15 07:50:54 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled... May 15 07:50:54 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started... May 15 07:50:54 flavio-laptop NetworkManager: <info> Activation (wlan0) failure scheduled... May 15 07:50:54 flavio-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete. May 15 07:50:54 flavio-laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0 
May 15 07:50:54 flavio-laptop dhcdbd: Unrequested down ?:3
May 15 07:50:54 flavio-laptop NetworkManager: <info> Activation (wlan0) failed for access point (FLAVIO-CASA) May 15 07:50:54 flavio-laptop NetworkManager: <info> Activation (wlan0) failed. May 15 07:50:54 flavio-laptop NetworkManager: <info> Deactivating device wlan0. May 15 07:50:54 flavio-laptop kernel: [ 136.166769] wlan0: deauthenticate(reason=3) May 15 07:50:55 flavio-laptop avahi-daemon[5095]: Withdrawing address record for 169.254.3.247 on wlan0. May 15 07:50:55 flavio-laptop avahi-daemon[5095]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.3.247. May 15 07:50:55 flavio-laptop avahi-daemon[5095]: Interface wlan0.IPv4 no longer relevant for mDNS. May 15 07:50:55 flavio-laptop avahi-daemon[5095]: Withdrawing address record for fe80::217:c4ff:fe05:6524 on wlan0. 
May 15 07:51:41 flavio-laptop pppd[4447]: Timeout waiting for PADO packets
May 15 07:51:41 flavio-laptop pppd[4447]: Unable to complete PPPoE Discovery


Alguém tem idéia do que está acontecendo ?
Como a máquina Debian chega a pegar o nome do notebook e chega a oferecer um IP para este eu presumo que a placa de rede do Debian esteja OK (eu acho). 

Agradeço por qualquer dica.

Sucesso a todos

Flávio Alberto Lopes Soares
Reply to: