Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!

Ogłoszenie

Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.

#1  2009-12-08 13:26:21

  pink - Użytkownik

pink
Użytkownik
Skąd: P17PY93
Zarejestrowany: 2005-09-16

wlan0 dhcp nie moze pobrac adresu

mam taki dziwny problem od jakiegos czasu
jak ustawie interfejs wlan0 static i wpisze wszystkie potrzebne dane to jest ok
ale jak ustawie dhcp to nie moze pobrac adresu z serwera wypisuje ze
NODHCPOFFERS recieved i NO WORKING LEASSES
a bylo ok jakis czas temu
nie wiem co jest grane jakies sugestie ??????


T430 think-box 4.9-custom x86_64 Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz GenuineIntel GNU/Linux
"Doktor plama i maharadża są pod złotym leszczem." "Człowieka od zwierzęcia odróżnia ciekawość świata. Patrze słucham i wyciągam wnioski."
https://www.behance.net/przemyslawmamon

Offline

 

#2  2009-12-08 13:38:35

  kamikaze - Administrator

kamikaze
Administrator
Zarejestrowany: 2004-04-16

Re: wlan0 dhcp nie moze pobrac adresu

Serwer DHCP nie działa lub działa nie prawidłowo? Zerknij w logi serwera DHCP.

Ostatnio edytowany przez kamikaze (2009-12-08 14:38:59)

Offline

 

#3  2009-12-08 14:05:29

  pink - Użytkownik

pink
Użytkownik
Skąd: P17PY93
Zarejestrowany: 2005-09-16

Re: wlan0 dhcp nie moze pobrac adresu

tu mam dmesg i wpisy dotyczace wlan

Kod:

b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
pci 0000:00:02.0: setting latency timer to 64
Restarting tasks ... done.
wlan0: direct probe to AP 00:15:2b:22:0a:80 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:15:2b:22:0a:80
wlan0: authenticated
wlan0: associate with AP 00:15:2b:22:0a:80
wlan0: RX AssocResp from 00:15:2b:22:0a:80 (capab=0x421 status=0 aid=33)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
CE: hpet increasing min_delta_ns to 15000 nsec
wlan0: no IPv6 routers present
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:40:96:a6:67:74 try 1
wlan0: direct probe to AP 00:40:96:a6:67:74 try 2
wlan0 direct probe responded
wlan0: authenticate with AP 00:40:96:a6:67:74
wlan0: authenticated
wlan0: associate with AP 00:40:96:a6:67:74
wlan0: RX AssocResp from 00:40:96:a6:67:74 (capab=0x421 status=0 aid=55)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:15:2b:22:0a:30 try 1
wlan0: direct probe to AP 00:15:2b:22:0a:30 try 2
wlan0 direct probe responded
wlan0: authenticate with AP 00:15:2b:22:0a:30
wlan0: authenticated
wlan0: associate with AP 00:15:2b:22:0a:30
wlan0: RX AssocResp from 00:15:2b:22:0a:30 (capab=0x421 status=0 aid=180)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
wlan0: deauthenticated (Reason: 2)
wlan0: direct probe to AP 00:15:2b:22:0a:30 try 1
wlan0: direct probe to AP 00:15:2b:22:0a:30 try 2
wlan0: direct probe to AP 00:15:2b:22:0a:30 try 3
wlan0: direct probe to AP 00:15:2b:22:0a:30 timed out
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:40:96:a6:67:74 try 1
wlan0: direct probe to AP 00:40:96:a6:67:74 try 2
wlan0 direct probe responded
wlan0: authenticate with AP 00:40:96:a6:67:74
wlan0: authenticated
wlan0: associate with AP 00:40:96:a6:67:74
wlan0: RX AssocResp from 00:40:96:a6:67:74 (capab=0x421 status=0 aid=58)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present

nie wiem czy to cos pomoze ja niewiele z tego kaman

tu jest dhcp.conf

Kod:

cat /etc/dhcp3/dhclient.conf 
# Configuration file for /sbin/dhclient, which is included in Debian's
#    dhcp3-client package.
#
# This is a sample configuration file for dhclient. See dhclient.conf's
#    man page for more information about the syntax of this file
#    and a more comprehensive list of the parameters understood by
#    dhclient.
#
# Normally, if the DHCP server provides reasonable information and does
#    not leave anything out (like the domain name, for example), then
#    few changes must be made to this file, if any.
#

option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

send host-name "sid-debian";
send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
request subnet-mask, broadcast-address, time-offset, routers,
    domain-name, domain-name-servers, domain-search, host-name,
    netbios-name-servers, netbios-scope, interface-mtu,
    rfc3442-classless-static-routes, ntp-servers;
#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/etc/dhcp3/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

#alias {
#  interface "eth0";
#  fixed-address 192.168.1.10;
#  option subnet-mask 255.255.255.0;
#}

#alias {
#  interface ¨wlan0¨;
#  fixed-address 192.168.1.10;
#  option subnet-mask 255.255.255.0; 
#}
#lease {
#  interface "eth0";
#  fixed-address 192.33.137.200;
#  medium "link0 link1";
#  option host-name "andare.swiftmedia.com";
#  option subnet-mask 255.255.255.0;
#  option broadcast-address 192.33.137.255;
#  option routers 192.33.137.250;
#  option domain-name-servers 127.0.0.1;
#  renew 2 2000/1/12 00:00:01;
#  rebind 2 2000/1/12 00:00:01;
#  expire 2 2000/1/12 00:00:01;
#}

Kod:

Dec  8 13:52:23 sid-box dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Dec  8 13:52:27 sid-box dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Dec  8 13:52:31 sid-box dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Dec  8 13:52:41 sid-box dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Dec  8 13:52:51 sid-box dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Dec  8 13:53:03 sid-box dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
Dec  8 13:53:22 sid-box dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Dec  8 13:53:24 sid-box dhclient: No DHCPOFFERS received.
Dec  8 13:53:24 sid-box dhclient: No working leases in persistent database - sleeping.

na AP server dziala na pewno prawidlowo, jest to samo na innych AP
poza tym winda pobiera bez problemu z dhcp

Ostatnio edytowany przez pink (2009-12-08 14:54:27)


T430 think-box 4.9-custom x86_64 Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz GenuineIntel GNU/Linux
"Doktor plama i maharadża są pod złotym leszczem." "Człowieka od zwierzęcia odróżnia ciekawość świata. Patrze słucham i wyciągam wnioski."
https://www.behance.net/przemyslawmamon

Offline

 

Stopka forum

Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
Możesz wyłączyć AdBlock — tu nie ma reklam ;-)