ROBIN -  Open Source Mesh Network Forum Index ROBIN - Open Source Mesh Network
users community forum
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

User unable to authencate to gateway, Odd DHCP reqs in log

 
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> beta-1.21
View previous topic :: View next topic  
Author Message
Ads






Posted: Sun Aug 20, 2017 10:07 pm    Post subject: Ads

Back to top
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Wed Oct 08, 2008 5:09 pm    Post subject: User unable to authencate to gateway, Odd DHCP reqs in log Reply with quote

I got a call saying a user was unable to connect to a node. I was able to get logged into the gateway to see what was going on. The gateway wireless networks were showing up, but the user could not connect. The client is a Macbook. This happened about 30 mins ago.

This got my attention in the log, first because the date and time are wrong and second the strange DHCP entries:

Quote:
Jan 3 02:47:45 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Jan 3 02:47:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: deauthenticated due to local deauth request
Jan 3 02:47:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Jan 3 02:47:59 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Jan 3 02:48:01 Office cron.notice crond[2498]: USER root pid 26139 cmd /sbin/tts-check
Jan 3 02:48:01 Office cron.notice crond[2498]: USER root pid 26140 cmd /sbin/hw-heartbeat
Jan 3 02:48:02 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: deauthenticated due to local deauth request
Jan 3 02:48:02 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated


I issued an update command and shortly after that the gateway rebooted. After that I saw more strange DHCP entries:

Quote:
Oct 8 15:48:42 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 15:48:42 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 15:48:42 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)
Oct 8 15:48:44 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 192.168.254.209 00:1f:5b:bc:74:d6
Oct 8 15:48:44 Office daemon.info dnsmasq[2493]: DHCPNAK(ath2) 192.168.254.209 00:1f:5b:bc:74:d6 wrong network
Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:48:48 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:48 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:48:52 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:52 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:00 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:00 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:01 Office cron.notice crond[2498]: USER root pid 2951 cmd ( /sbin/preupdate ; /bin/sleep 50 ; /sbin/watchout4node && /sbin/update )
Oct 8 15:49:09 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:09 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:10 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:10 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:11 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:11 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:13 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:13 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:17 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:17 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:25 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:25 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6


Oct 8 15:49:27 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:27 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:30 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:30 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:35 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:35 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:43 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:43 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:51 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:51 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:50:00 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:50:00 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:50:01 Office cron.notice crond[2498]: USER root pid 3131 cmd /sbin/tts-check
Oct 8 15:50:09 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:50:09 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:50:12 Office user.notice update: dashboard succesfully updated
Oct 8 15:50:17 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:50:17 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:50:24 Office user.notice update: nothing to update for this node
Oct 8 15:50:26 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:50:26 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:50:41 Office user.notice update: dashboard succesfully updated
Oct 8 15:50:53 Office user.notice update: nothing to update for this node
Oct 8 15:51:01 Office cron.notice crond[2498]: USER root pid 5895 cmd /sbin/hw-heartbeat
Oct 8 15:51:32 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 15:51:34 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 15:51:36 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 15:51:36 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)
Oct 8 15:51:41 Office daemon.info dnsmasq[2480]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 15:51:41 Office daemon.info dnsmasq[2480]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:43 Office daemon.info dnsmasq[2480]: DHCPREQUEST(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:43 Office daemon.info dnsmasq[2480]: DHCPACK(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:47 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 15:51:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 15:51:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 15:51:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)
Oct 8 15:51:48 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:48 Office daemon.info dnsmasq[2493]: DHCPNAK(ath2) 101.103.182.24 00:1f:5b:bc:74:d6 wrong address
Oct 8 15:51:49 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:51:49 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:51 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:51 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:52:01 Office cron.notice crond[2498]: USER root pid 5952 cmd /sbin/tts-check


In the past I have had issues like this where the user could see the wireless network, but would not let him attach. I have also had an issue where the user could attach to the gateway, but was unable to browse the web. I have the full log file if needed. Also, I had another strange DHCP entry that resulted when I was attaching with my Dell laptop. I was able to attach and browse the web.

Quote:
Jan 2 10:46:42 Office daemon.info hostapd: ath2: STA 00:1c:26:39:ef:ac IEEE 802.11: associated
Jan 2 10:46:42 Office daemon.info hostapd: ath2: STA 00:1c:26:39:ef:ac WPA: pairwise key handshake completed (WPA)
Jan 2 10:46:42 Office daemon.info hostapd: ath2: STA 00:1c:26:39:ef:ac WPA: group key handshake completed (WPA)
Jan 2 10:46:46 Office daemon.info dnsmasq[2488]: DHCPDISCOVER(ath2) 00:1c:26:39:ef:ac
Jan 2 10:46:46 Office daemon.info dnsmasq[2488]: DHCPOFFER(ath2) 102.103.182.16 00:1c:26:39:ef:ac
Jan 2 10:46:46 Office daemon.warn dnsmasq[2488]: Ignoring DHCP host name st-mprind.puffer.com because it has an illegal domain part
Jan 2 10:46:46 Office daemon.info dnsmasq[2488]: DHCPREQUEST(ath2) 102.103.182.16 00:1c:26:39:ef:ac
Jan 2 10:46:46 Office daemon.info dnsmasq[2488]: DHCPACK(ath2) 102.103.182.16 00:1c:26:39:ef:ac

_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Wed Oct 08, 2008 5:50 pm    Post subject: Reply with quote

macbook requests an IP presenting itself as 192.168.254.209 and AP2 says "wrong network" and
doesn't allow that IP:
Code:

Oct 8 15:48:44 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 192.168.254.209 00:1f:5b:bc:74:d6
Oct 8 15:48:44 Office daemon.info dnsmasq[2493]: DHCPNAK(ath2) 192.168.254.209 00:1f:5b:bc:74:d6 wrong network


macbook continues to request an IP and AP2 offers 102.103.182.24
but macbook seems don't like this address and ask again
AP2 offers 102.103.182.24
but macbook seems don't like this address and ask again (and so on)
Code:

Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:47 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:48:48 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:48 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:48:52 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:48:52 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:49:00 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:49:00 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
...
...


macbook disassociates itself from AP2 and associates with AP1, exchanging WPA:
Code:

Oct 8 15:51:32 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 15:51:34 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 15:51:36 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 15:51:36 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)


macbook ask AP1 for an IP and AP1 offers 101.103.182.24:
Code:

Oct 8 15:51:41 Office daemon.info dnsmasq[2480]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 15:51:41 Office daemon.info dnsmasq[2480]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6


macbook get 101.103.182.24 and AP1 allow its choice:
Code:

Oct 8 15:51:43 Office daemon.info dnsmasq[2480]: DHCPREQUEST(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:43 Office daemon.info dnsmasq[2480]: DHCPACK(ath1) 101.103.182.24 00:1f:5b:bc:74:d6


but macbook disacciates itself from AP1 and associate with AP2:
Code:

Oct 8 15:51:47 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 15:51:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 15:51:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 15:51:48 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)


macbook presents itself with the IP address goy by AP1, but AP2 doesn't allow this IP
Code:

Oct 8 15:51:48 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:48 Office daemon.info dnsmasq[2493]: DHCPNAK(ath2) 101.103.182.24 00:1f:5b:bc:74:d6 wrong address


then starts again the cycle, AP2 offer, macbook doesn't like and request, AP2 offer,... :
Code:

Oct 8 15:51:49 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 15:51:49 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:51 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 15:51:51 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Wed Oct 08, 2008 6:29 pm    Post subject: Reply with quote

Is there any particular reason why this would happen? My wife has a macbook that we use at home on our wireless network and she never has an issue getting an IP from the wireless router. Of course I'm not using Open-Mesh at home.

_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
dalenorman
Ultimate User
Ultimate User


Joined: 24 Mar 2008
Posts: 379
Location: Toronto, Ontario

PostPosted: Wed Oct 08, 2008 6:48 pm    Post subject: Reply with quote

Mac OSX lets you request an IP by "DHCP with manual address". Doing so pulls netmask, default gateway and dns info from DHCP server, but lets the user manually enter an IP address.



Only registered users can see links on this forum!
Register or Login on forum!




Only registered users can see links on this forum!
Register or Login on forum!




Only registered users can see links on this forum!
Register or Login on forum!



Sounds to me like someone thinks they're being clever and trying to manually change their IP address in hopes of bypassing your authentication.
Back to top
View user's profile Send private message
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Wed Oct 08, 2008 7:37 pm    Post subject: Reply with quote

What is odd though is he changed to AP1 and it connected, he then changed back to the Private AP2 and all of a sudden he got connected and was working. Then he called and said he was unable to get to the net about 20 mins later.

I just got off the phone with him and the gateway is not even accepting his laptop. It's saying connection failed. I looked at the log and I'm not even seeing the connection attempt. The process list is below since I'm not sure what processes should be running.

I've had this issue with my Dell laptop also where it would connect to the AP, but wouldn't be issued an address. At that point I didn't know about the logread so I didn't look at the log to see what it was saying, but to me this seems like there maybe something funky with the DHCP server that the clients don't like. The dell is running XP SP2 and the Macbook is running 10.5.

I have also had the problem where it wouldn't even connect to the access point at all. I would keep getting a message that I could not connect. I would finally reboot the access point and it would start to work. There is some bug that must be going on here cause this problem has occurred several times before on several versions.

Here's the log file from the user attempt...

Quote:
Oct 8 18:13:46 Office daemon.info hostapd: ath2: STA 00:1d:4f:07:36:b8 IEEE 802.11: associated
Oct 8 18:13:48 Office daemon.info hostapd: ath2: STA 00:1d:4f:07:36:b8 WPA: pairwise key handshake completed (WPA)
Oct 8 18:13:48 Office daemon.info hostapd: ath2: STA 00:1d:4f:07:36:b8 WPA: group key handshake completed (WPA)
Oct 8 18:13:51 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1d:4f:07:36:b8
Oct 8 18:13:51 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.90 00:1d:4f:07:36:b8
Oct 8 18:13:51 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1d:4f:07:36:b8
Oct 8 18:13:51 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.90 00:1d:4f:07:36:b8
Oct 8 18:13:51 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1d:4f:07:36:b8
Oct 8 18:13:51 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.90 00:1d:4f:07:36:b8
Oct 8 18:13:55 Office daemon.info dnsmasq[2493]: DHCPDISCOVER(ath2) 00:1d:4f:07:36:b8
Oct 8 18:13:55 Office daemon.info dnsmasq[2493]: DHCPOFFER(ath2) 102.103.182.90 00:1d:4f:07:36:b8
Oct 8 18:13:56 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.90 00:1d:4f:07:36:b8
Oct 8 18:13:56 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.90 00:1d:4f:07:36:b8 Josh-s-iPod
Oct 8 18:13:57 Office daemon.info dnsmasq[2493]: DHCPREQUEST(ath2) 102.103.182.90 00:1d:4f:07:36:b8
Oct 8 18:13:57 Office daemon.info dnsmasq[2493]: DHCPACK(ath2) 102.103.182.90 00:1d:4f:07:36:b8 Josh-s-iPod

Oct 8 18:15:03 Office daemon.info hostapd: ath2: STA 00:1d:4f:07:36:b8 IEEE 802.11: deauthenticated due to local deauth request
Oct 8 18:15:03 Office daemon.info hostapd: ath2: STA 00:1d:4f:07:36:b8 IEEE 802.11: disassociated
Oct 8 18:15:03 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: deauthenticated due to local deauth request
Oct 8 18:15:03 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 18:15:05 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 18:15:08 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: deauthenticated due to local deauth request
Oct 8 18:15:08 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 18:15:09 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 18:15:12 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: deauthenticated due to local deauth request
Oct 8 18:15:12 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated


Quote:
PID Uid VmSize Stat Command
1 root 408 S init
2 root SWN [ksoftirqd/0]
3 root SW< [events/0]
4 root SW< [khelper]
5 root SW< [kthread]
17 root SW< [kblockd/0]
28 root SW [pdflush]
29 root SW [pdflush]
30 root SW< [kswapd0]
31 root SW< [aio/0]
41 root SW [mtdblockd]
150 root SWN [jffs2_gcd_mtd1]
283 root 416 S logger -s -p 6 -t
285 root 248 S init
292 root 348 S syslogd -C16
295 root 288 S klogd
303 root 268 S /sbin/hotplug2 --override --persistent --max-children
723 root 152 S /sbin/udhcpc -i eth0 -t 10 -n -s /usr/share/udhcpc/ro
2162 root 716 S hostapd -B /var/run/hostapd-ath1.conf
2256 root 720 S hostapd -B /var/run/hostapd-ath2.conf
2263 root 328 S /usr/sbin/dropbear -p 22
2405 root 436 S /usr/sbin/batmand -o 1500 -g 5000 --hop-penalty 10 at
2406 root 436 S /usr/sbin/batmand -o 1500 -g 5000 --hop-penalty 10 at
2408 root 436 S /usr/sbin/batmand -o 1500 -g 5000 --hop-penalty 10 at
2409 root 436 S /usr/sbin/batmand -o 1500 -g 5000 --hop-penalty 10 at
2444 root 172 S /usr/sbin/httpd -p 8080 -h /www
2464 root 144 S duende /usr/sbin/maradns
2465 nobody 648 S /usr/sbin/maradns
2467 66 216 S duende /usr/sbin/maradns
2480 nobody 384 S /usr/sbin/dnsmasq -C /etc/dnsmasq.ap.conf --bind-inte
2493 nobody 384 S /usr/sbin/dnsmasq -C /etc/dnsmasq.Myap.conf --bind-in
2498 root 392 S crond -c /etc/crontabs
2559 root 504 S /usr/bin/nodogsplash
2746 root 504 S /usr/bin/nodogsplash
2747 root 504 S /usr/bin/nodogsplash
2749 root 504 S /usr/bin/nodogsplash
2888 nobody 648 S /usr/sbin/maradns
22048 root 556 R /usr/sbin/dropbear -p 22
22054 root 576 S -ash
29010 root 396 S /bin/sh -c ( /sbin/preupdate ; /bin/sleep 50 ; /sbin/
29014 root 256 S /bin/sh -c ( /sbin/preupdate ; /bin/sleep 50 ; /sbin/
29019 root 300 S /bin/sleep 50
29034 root 392 R ps -A

_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Wed Oct 08, 2008 7:51 pm    Post subject: More Info Reply with quote

I just rebooted the gateway using the reboot command from the command line. The gateway appears to have rebooted fine, but there is still a problem issuing the client an IP address.

Quote:
Oct 8 18:44:00 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 18:44:00 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 18:44:00 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)
Oct 8 18:42:01 Office cron.warn crond[2495]: time disparity of 4613440 minutes detected
Oct 8 18:44:00 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 18:44:00 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 18:44:00 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)
Oct 8 18:44:01 Office cron.notice crond[2495]: USER root pid 2934 cmd /sbin/tts-check
Oct 8 18:44:01 Office cron.notice crond[2495]: USER root pid 2936 cmd ( /sbin/preupdate ; /bin/sleep 39 ; /sbin/watchout4node && /sbin/update )
Oct 8 18:44:01 Office daemon.info dnsmasq[2485]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:01 Office daemon.info dnsmasq[2485]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:04 Office daemon.info dnsmasq[2485]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:04 Office daemon.info dnsmasq[2485]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:09 Office daemon.info dnsmasq[2485]: DHCPDISCOVER(ath2) 00:1f:5b:bc:74:d6
Oct 8 18:44:09 Office daemon.info dnsmasq[2485]: DHCPOFFER(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:14 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 18:44:15 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 18:44:15 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 18:44:15 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)
Oct 8 18:44:17 Office daemon.info dnsmasq[2477]: DHCPREQUEST(ath1) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:17 Office daemon.info dnsmasq[2477]: DHCPNAK(ath1) 102.103.182.24 00:1f:5b:bc:74:d6 wrong network
Oct 8 18:44:20 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:44:20 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:20 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:44:20 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:21 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:44:21 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:25 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:44:25 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:34 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:44:34 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:42 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:44:42 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:44:54 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:44:54 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:45:00 Office daemon.info dnsmasq[2477]: DHCPDISCOVER(ath1) 00:1f:5b:bc:74:d6
Oct 8 18:45:00 Office daemon.info dnsmasq[2477]: DHCPOFFER(ath1) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:45:01 Office cron.notice crond[2495]: USER root pid 3557 cmd /sbin/hw-heartbeat
Oct 8 18:45:01 Office user.notice update: dashboard succesfully updated
Oct 8 18:45:01 Office daemon.info hostapd: ath1: STA 00:1f:5b:bc:74:d6 IEEE 802.11: disassociated
Oct 8 18:45:03 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 IEEE 802.11: associated
Oct 8 18:45:03 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: pairwise key handshake completed (WPA)
Oct 8 18:45:03 Office daemon.info hostapd: ath2: STA 00:1f:5b:bc:74:d6 WPA: group key handshake completed (WPA)
Oct 8 18:45:04 Office daemon.info dnsmasq[2485]: DHCPREQUEST(ath2) 101.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:45:04 Office daemon.info dnsmasq[2485]: DHCPNAK(ath2) 101.103.182.24 00:1f:5b:bc:74:d6 wrong address
Oct 8 18:45:07 Office daemon.info dnsmasq[2485]: DHCPREQUEST(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:45:07 Office daemon.info dnsmasq[2485]: DHCPACK(ath2) 102.103.182.24 00:1f:5b:bc:74:d6
Oct 8 18:45:13 Office user.notice update: nothing to update for this node

_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Wed Oct 08, 2008 11:25 pm    Post subject: Reply with quote

More odd behavior...

Quote:
Oct 8 21:45:18 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:21 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:21 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:21 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:24 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:24 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:24 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:27 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:27 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:27 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:30 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:30 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:30 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:33 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:33 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:33 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:36 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:36 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:36 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:40 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:40 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:40 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:43 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:43 Office daemon.info hostapd: ath2: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:43 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:46 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:46 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated
Oct 8 21:45:46 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: associated
Oct 8 21:45:49 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: deauthenticated due to local deauth request
Oct 8 21:45:49 Office daemon.info hostapd: ath1: STA 00:1f:3b:7e:e3:db IEEE 802.11: disassociated

_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Thu Oct 09, 2008 4:26 am    Post subject: Reply with quote

This is what I expect to see. This is was a Dell laptop connecting and then disconnecting.

Quote:
Oct 9 02:10:31 open-mesh daemon.info hostapd: ath2: STA 00:1b:fc:7d:df:4b IEEE 802.11: associated
Oct 9 02:10:32 open-mesh daemon.info hostapd: ath2: STA 00:1b:fc:7d:df:4b WPA: pairwise key handshake completed (WPA)
Oct 9 02:10:32 open-mesh daemon.info hostapd: ath2: STA 00:1b:fc:7d:df:4b WPA: group key handshake completed (WPA)
Oct 9 02:10:36 open-mesh daemon.info dnsmasq[2572]: DHCPDISCOVER(ath2) 00:1b:fc:7d:df:4b
Oct 9 02:10:36 open-mesh daemon.info dnsmasq[2572]: DHCPOFFER(ath2) 102.103.182.103 00:1b:fc:7d:df:4b
Oct 9 02:10:36 open-mesh daemon.info dnsmasq[2572]: DHCPREQUEST(ath2) 102.103.182.103 00:1b:fc:7d:df:4b
Oct 9 02:10:36 open-mesh daemon.info dnsmasq[2572]: DHCPACK(ath2) 102.103.182.103 00:1b:fc:7d:df:4b MONTY
Oct 9 02:10:53 open-mesh daemon.info dnsmasq[2572]: DHCPRELEASE(ath2) 102.103.182.103 00:1b:fc:7d:df:4b
Oct 9 02:10:53 open-mesh daemon.info hostapd: ath2: STA 00:1b:fc:7d:df:4b IEEE 802.11: disassociated

_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
hyperllc
User
User


Joined: 18 May 2008
Posts: 39
Location: St Augustine FL - Albany GA - Birmingham AL

PostPosted: Sun Nov 09, 2008 6:27 pm    Post subject: Reply with quote

Client cannot get an IP address. This has been the number one issue on all my networks. I get calls all the time about this. Very Good to Excellent signals but yet the client cannot get a ip address. Limited or no connectivity or hunts for an ip for a very long time. The SSID's may even dissapear or jam and disable the laptop wireless device for a bit. I'll switch the network back to BATMAN and then it seems to connect easier again for a bit but them stops giving ip's so I go back to OLSR. Also a channel change for reboot via SSH works somtimes.

Were using Accton MR3201A's and Wiligear/Deliberant WBD-500's with robin firmware. I have not had any router lock ups since putting the WBD-500 as the gateway which is fantastic! I used to have the gateway plugged directly into the cable modem but since have installed a dd-wrt broadcom device between it. Thought this might help eliminate some issues.

I wish I could connect to open-meshes as qiuck as dd-wrt's and linksys' that would complete me Smile

Chris

r1388-23/nB 0.3-rv964
r1388-23/nO 0.5.6-r2
r1408-23/nB 0.3-rv964
r1408-23/nO 0.5.6-r2
Back to top
View user's profile Send private message Visit poster's website
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Sun Nov 09, 2008 6:48 pm    Post subject: Reply with quote

this is really unexpected: all your cients cannot get DHCP info from any node?
Can you post a logread capture related to a DHCP session between a node and a client?
Back to top
View user's profile Send private message Send e-mail Visit poster's website
hyperllc
User
User


Joined: 18 May 2008
Posts: 39
Location: St Augustine FL - Albany GA - Birmingham AL

PostPosted: Sun Nov 09, 2008 6:59 pm    Post subject: Reply with quote

Thanks for the quick response Antonio.
I was just going to ask the process on how to do that.

What command do I issue in the command line to get results like Kage.
Back to top
View user's profile Send private message Visit poster's website
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Sun Nov 09, 2008 7:04 pm    Post subject: Reply with quote

logread

(but be sure that logread logs the DHCP session as logread is a circular buffer)
Back to top
View user's profile Send private message Send e-mail Visit poster's website
hyperllc
User
User


Joined: 18 May 2008
Posts: 39
Location: St Augustine FL - Albany GA - Birmingham AL

PostPosted: Sun Nov 09, 2008 7:32 pm    Post subject: Reply with quote

ok thanks Antonio

I will wait for some clients to connect and check the gateway from here and soon I will head out there on site and do some logreads on the rest of the nodes. This will be huge if we can figure this out, maybe I'm doing somthing simply wrong on all my networks. The logs will tell.

**UPDATE
I am not seeing any DHCP info in the logs in any nodes and gateway. The dashboard says I have 17 users throughout mall.

i just run "logread" and nothing else?

Thanks!
Back to top
View user's profile Send private message Visit poster's website
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Sun Nov 09, 2008 11:22 pm    Post subject: Reply with quote

I have noticed that the new versions have no DHCP entries in logread. I posted a thread in the C1xxx forum about it. The logs have seem to have stopped when Antonio switched over to DHCPd.

Only registered users can see links on this forum!
Register or Login on forum!


_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
hyperllc
User
User


Joined: 18 May 2008
Posts: 39
Location: St Augustine FL - Albany GA - Birmingham AL

PostPosted: Mon Nov 10, 2008 12:58 am    Post subject: Reply with quote

This is what I saw in some of the logs on my Wiligear 500 gateway. Is it anything to worry about.

Nov 9 21:24:35 FOODCOURT user.err kernel: wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
Nov 9 21:24:41 FOODCOURT user.notice update: dashboard succesfully updated
Nov 9 21:24:57 FOODCOURT user.notice update: nothing to update for this node
Nov 9 21:26:01 FOODCOURT cron.notice crond[2094]: USER root pid 3685 cmd /sbin/tts-check
Nov 9 21:27:01 FOODCOURT cron.notice crond[2094]: USER root pid 3725 cmd /sbin/hw-heartbeat
Nov 9 21:27:41 FOODCOURT user.err kernel: wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
Nov 9 21:27:50 FOODCOURT user.err kernel: wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
Nov 9 21:28:01 FOODCOURT cron.notice crond[2094]: USER root pid 3735 cmd /sbin/tts-check
Nov 9 21:29:01 FOODCOURT cron.notice crond[2094]: USER root pid 3752 cmd ( /sbin/preupdate ; /bin/sleep 17 ; /sbin/watchout4node && /sbin/update )


Also I tried to see the leases on some nodes and I get:

"cat /tmp/dhcp.ap.leases" and my reply is:
-ash: root@BOOKS-A-MILLION:~#: not found
root@BOOKS-A-MILLION:~# cat: can't open '/tmp/dhcp.ap.leases': No such file or d irectory
> root@BOOKS-A-MILLION:~#

I know there should be leases because there are a few people on this node. It took me lots of "Repair" my network connections on both my MSI Mini U100 and Dell 1405 to get connected.

Feel free to SSH in
12.214.230.79 password is the Open-Mesh default right now.
I can't figure out whats going on.
Back to top
View user's profile Send private message Visit poster's website
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Mon Nov 10, 2008 3:49 am    Post subject: Reply with quote

I'm poking around right now... Interestingly enough I just got home and when i tried to connect to my test node at home it wouldn't let me connect.

Update: I looked around and didn't see much. I did see you have several users connected to the network now and you've had up to 46 users that have xfered 326 megs.

I know my test node at home I've had it twice now where it wouldn't let me connect to the node and little to nothing in the log. I've had to reboot it to get it to let me back in again. I was able to ssh into the node from my main network.

Update 2: One other thing I just remembered, there is a well documented power issue with the current model Accton nodes. If there is a micro power blip it can cause the node to lockup. It can be as simple as the power plug being loose or it could be the circuit the node is plugged into could have something that causes it to blip. Once the node locks up the only way to recover it is to remove power. There is a hardware mod that can be done on the nodes, but it requires soldering skills and the parts. The urls below are the links to the mod thread and to the thread where everyone was discussing the mod.

Only registered users can see links on this forum!
Register or Login on forum!


Only registered users can see links on this forum!
Register or Login on forum!


_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Mon Nov 10, 2008 5:53 am    Post subject: Reply with quote

I have a thread in the Cxxx forum with pretty much the same issue your seeing. Here's the URL:
Only registered users can see links on this forum!
Register or Login on forum!


_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Mon Nov 10, 2008 8:09 am    Post subject: Reply with quote

How many Accton routers do yo have?

How many have yot modified with MCP120 reset?

I guess we will only know the answer when you modify the rest of your accton routers!
Back to top
View user's profile Send private message
Kage_
Moderator
Moderator


Joined: 31 Jul 2008
Posts: 592
Location: Texas, USA

PostPosted: Mon Nov 10, 2008 3:40 pm    Post subject: Reply with quote

The issue I'm seeing isn't power related. When the power glitch hits the nodes they lockup. The wireless APs disappear from the scanner and you can't ssh into the nodes. I had one node that kept doing this and I did mod that one. That node has been solid ever since.

With this issue I can see the APs, I can ssh into the APs, but none of the clients can connect to the AP. The attempt to connect, but fail. Ever since the switch to the new DHCPd service there are no longer any entries into the log regarding anything related to DHCP.

_________________
Production Network: r2693-26/nO 0.5.6-r8
Test Network: r2693-26/nO 0.5.6-r8
Open-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
hyperllc
User
User


Joined: 18 May 2008
Posts: 39
Location: St Augustine FL - Albany GA - Birmingham AL

PostPosted: Mon Nov 10, 2008 4:41 pm    Post subject: Reply with quote

At the office building this morning, we have 1 Accton gateway and 1 node 2 SSID.
It took me 3 tries and 10 minutes with my MSI 100U Laptop to connect this morning. Could not get an IP on the Private network. Windows XP stops and gives up before an address is handed out. I just then let it sit there for a few minutes on SSID 1 saying "Limited or no connectivity" then finally connected after 2 mins.
My business partner has a Acer Aspire 3610 and we are still trying to connect. It seems the internal wireless adapter just shuts down, I see this alot on other laptops trying to connect to our networks. Now it will not connect to any SSID's even though they are visible full signal.. There is no attempt to even negotiate. Even after issuing a repair. We see a whole page of SSID's but the laptop refuses to connect to any network including non open-mesh.
My other employee just infomed me his Dell with an Intel wireless card connected instantly.

Going to reset the gateway.....
Back to top
View user's profile Send private message Visit poster's website
sronan
Skilled User
Skilled User


Joined: 17 Feb 2008
Posts: 211

PostPosted: Mon Nov 10, 2008 5:43 pm    Post subject: Reply with quote

When discussing DHCP problems, it may be helpful to specify what OS the client machine(s) experiencing difficulties are running particularly if some laptops are connecting okay and others not. In particular it can help rule out issues like this one affecting machines running VISTA.
Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
hyperllc
User
User


Joined: 18 May 2008
Posts: 39
Location: St Augustine FL - Albany GA - Birmingham AL

PostPosted: Mon Nov 10, 2008 6:04 pm    Post subject: Reply with quote

I agree, but it's a range of OS and hardware configs that are having these same issues and it's so random. I watch the general public shaking their heads as they struggle to get connected to my network.

Here is what were using:
Dell E1405,Vista Ultimate SP1, Dell Wireless
MSI Wind U100, XP Home SP3, Realtek Wireless b/g
Dell E1405, Vista Ultimate SP1, Intel Wireless
Acer Aspire 3610, Windows XP Pro SP3

Chris
Back to top
View user's profile Send private message Visit poster's website
drntcm
User
User


Joined: 27 Jun 2009
Posts: 30
Location: Canada

PostPosted: Sun Sep 13, 2009 3:59 am    Post subject: Reply with quote

Has this issue been addressed in the current R2453+? Or is it still recommended to implement the Microsoft Vista DHCP Broadcast Flag workaround?
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Sun Sep 13, 2009 4:31 am    Post subject: Reply with quote

Quote:
Has this issue been addressed in the current R2453+? Or is it still recommended to implement the Microsoft Vista DHCP Broadcast Flag workaround?


The original post was made many moons ago

I'd be surprised it that fault was still around (just new ones)

_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

!
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> beta-1.21 All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
c d
e



Powered by phpBB © 2001, 2005 phpBB Group

Abuse - Report Abuse - TOS & Privacy.
Powered by forumup.it free forum, create your free forum! Created by Hyarbor & Qooqoa
Confirmed

Page generation time: 0.301