compsystems Posted November 27, 2008 Share Posted November 27, 2008 I have a strange problem with my fon, With karma on everything looks ok except it will not accept connections. If i turn on white list with no ssid's and make a bogus ssid on a second laptop and disable\enable the card I see "bogus" ssid not in whitelist message on the jasager log. Seems to work right? Ok so then if i clear the ssid list and change back to blacklist and enable\disable the card nothing happens. I have ICS running and configured. Also have the TFPD running for dhcp server. Do you need to change any of the settings in the openwrt page on webif.html? Maybe I can enable karma via ssh and see if there are any reported errors? New fon .7 R4 all install files are from the bundle on the wiki. Thanks, Completed the openwrt and karma install without any errors. Quote Link to comment Share on other sites More sharing options...
digininja Posted November 27, 2008 Share Posted November 27, 2008 Best way to debug is to boot the fon and let Jasager create the interface, then turn karma on. ssh to the device and run logread -f that should tail the syslog file. Try to associate and see what happens, if you are getting white list messages when you are in white list mode then it shows karma is working and Jasager is working to pull stuff from the logs. The question is why black list stuff isn't working. Try this and see what happens. Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 27, 2008 Author Share Posted November 27, 2008 Thanks for the quick reply, I unplugge the fon and pluged it back in , connected and turned karma on, waited a few minutes to see if anything would happen, it didnt changed to whitelist mode and disabled\enabled the client. the log read SSID "unix" is not in the white list... then cleared the log and set to blacklist, disabled\enabled the card. Thanks for the help. I guess im not allowed to attach files so ill have to post it here 90 $ 1 ports, IRQ sharing disabled Jan 1 00:00:19 (none) user.info kernel: serial8250: ttyS0 at MMIO 0xb1100003 (irq = 37) is a 16550A Jan 1 00:00:19 (none) user.notice kernel: eth0: Dropping NETIF_F_SG since no checksum feature. > Jan 1 00:00:19 (none) user.info kernel: Memory: 13504k/16384k available (1955kkernel code, 2880k reserved, 292k data, 116k init, 0k highmem) > Jan 1 00:00:19 (none) user.debug kernel: Calibrating delay loop... 183.50 BogoMIPS (lpj=917504) > Jan 1 00:00:19 (none) user.warn kernel: Mount-cache hash table entries: 512> Jan 1 00:00:19 (none) user.info kernel: NET: Registered protocol family 16> Jan 1 00:00:19 (none) user.warn kernel: Radio config found at offset 0xf8(0x1f8) > Jan 1 00:00:19 (none) user.info kernel: Time: MIPS clocksource has been install ed. > Jan 1 00:00:19 (none) user.info kernel: NET: Registered protocol family 2 > Jan 1 00:00:19 (none) user.warn kernel: IP route cache hash table entries: 1024 (order: 0, 4096 bytes) > Jan 1 00:00:19 (none) user.warn kernel: TCP established hash table entries: 512 (order: 0, 4096 bytes) > Jan 1 00:00:19 (none) user.warn kernel: TCP bind hash table entries: 512 (order : -1, 2048 bytes) > Jan 1 00:00:19 (none) user.info kernel: TCP: Hash tables configured (establishe d 512 bind 512) > Jan 1 00:00:19 (none) user.info kernel: TCP reno registered > Jan 1 00:00:19 (none) user.info kernel: squashfs: version 3.0 (2006/03/15) Phil lip Lougher > Jan 1 00:00:19 (none) user.warn kernel: Registering mini_fo version $Id$ > Jan 1 00:00:19 (none) user.info kernel: JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. > Jan 1 00:00:19 (none) user.info kernel: io scheduler noop registered > Jan 1 00:00:19 (none) user.info kernel: io scheduler deadline registered (defau lt) > Jan 1 00:00:19 (none) user.info kernel: Serial: 8250/16550 driver $Revision: 1. 90 $ 1 ports, IRQ sharing disabled > Jan 1 00:00:19 (none) user.info kernel: serial8250: ttyS0 at MMIO 0xb1100003 (i rq = 37) is a 16550A > Jan 1 00:00:19 (none) user.notice kernel: eth0: Dropping NETIF_F_SG since no ch ecksum feature. > Jan 1 00:00:19 (none) user.warn kernel: eth0: Atheros AR231x: 00:18:84:18:9e:50 , irq 4 > Jan 1 00:00:19 (none) user.notice kernel: cmdlinepart partition parsing not ava ilable Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: Minstrel automatic r ate control algorithm 1.2 (svn r2568) Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: look around rate set to 10% Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: EWMA rolloff level s et to 75% Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: max segment size in the mrr set to 6000 us Jan 1 00:00:26 (none) user.info kernel: wlan: mac acl policy registered Jan 1 00:00:28 (none) user.info kernel: ath_ahb: 0.9.4.5 (svn r2568) Jan 1 00:00:28 (none) user.info kernel: ath_pci: switching rfkill capability of f > Jan 1 00:00:19 (none) user.notice kernel: Searching for RedBoot partition table in spiflash at offset 0x7d0000 > Jan 1 00:00:19 (none) user.notice kernel: Searching for RedBoot partition table in spiflash at offset 0x7e0000 > Jan 1 00:00:19 (none) user.notice kernel: 5 RedBoot partitions found on MTD dev ice spiflash > Jan 1 00:00:19 (none) user.notice kernel: Creating 5 MTD partitions on "spiflas h": > Jan 1 00:00:19 (none) user.notice kernel: 0x00000000-0x00030000 : "RedBoot" > Jan 1 00:00:19 (none) user.notice kernel: 0x00030000-0x00720000 : "rootfs" > Jan 1 00:00:19 (none) user.notice kernel: 0x00130000-0x00720000 : "rootfs_data" > Jan 1 00:00:19 (none) user.notice kernel: 0x00720000-0x007e0000 : "vmlinux.bin. l7" Jan 1 00:00:28 (none) user.info kernel: ath_pci: switching per-packet transmit power control off Jan 1 00:00:28 (none) user.warn kernel: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 1 1Mbps Jan 1 00:00:28 (none) user.warn kernel: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 1 1Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 1 00:00:28 (none) user.warn kernel: wifi0: H/W encryption support: WEP AES AES_CCM TKIP Jan 1 00:00:28 (none) user.warn kernel: wifi0: mac 11.0 phy 4.8 radio 7.0 Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 1 for WME_AC_BE tra ffic Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 0 for WME_AC_BK tra ffic Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 2 for WME_AC_VI tra ffic Jan 1 00:00:28 (no> Jan 1 00:00:19 (none) user.notice kernel: 0x007e0000-0x007ef000 : "FIS director y" > Jan 1 00:00:19 (none) user.notice kernel: 0x007ef000-0x007f0000 : "RedBoot conf ig" > Jan 1 00:00:19 (none) user.warn kernel: nf_conntrack version 0.5.0 (128 buckets , 1024 max) > Jan 1 00:00:19 (none) user.warn kernel: ip_tables: © 2000-2006 Netfilter Core Team > Jan 1 00:00:19 (none) user.info kernel: TCP vegas registered > Jan 1 00:00:19 (none) user.info kernel: NET: Registered protocol family 1 > Jan 1 00:00:19 (none) user.info kernel: NET: Registered protocol family 17 > Jan 1 00:00:19 (none) user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <gr eearb@candelatech.com> > Jan 1 00:00:19 (none) user.info kernel: All bugs added by David S. Miller <dave m@redhat.com> > Jan 1 00:00:19 (none) user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly. > Jan 1 00:00:19 (none) user.info kernel: Freeing unused kernel memory: 116k free d > Jan 1 00:00:19 (none) user.info kernel: eth0: Configuring MAC for full duplex > Jan 1 00:00:19 (none) user.warn kernel: Warning: unable to open an initial cons ole. > Jan 1 00:00:19 (none) user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5 > Jan 1 00:00:19 (none) user.info kernel: mini_fo: using base directory: / ne) user.warn kernel: wifi0: Use hw queue 3 for WME_AC_VO tra ffic Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 8 for CAB traffic Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 9 for beacons Jan 1 00:00:28 (none) user.warn kernel: wifi0: Driver has Fon Karma 1.0 patches by Robin Wood <dninja@gmail.com> enabled Jan 1 00:00:28 (none) user.info kernel: wifi0: Atheros 2315 WiSoC: mem=0xb00000 00, irq=3 Jan 1 00:00:31 (none) user.info kernel: device ath0 entered promiscuous mode Jan 1 00:00:31 (none) user.info kernel: br-lan: port 2(ath0) entering learning state Jan 1 00:00:31 (none) user.info kernel: br-lan: topology change detected, propa gating Jan 1 00:00:31 (none) user.info kernel: br-lan: port 2(ath0) entering forwardin g state Jan 1 00:00:34 (none) cron.notice crond[471]: crond 2.3.2 dillon, started, log level 8 Jan 1 00:00:35 (none) authpriv.info dropbear[475]: Running in background Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: started, version 2.39 cachesize 150 Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: compile time options: IPv6 GNU- getopt ISC-leasefile no-DBus no-I18N TFTP Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: DHCP, IP range 192.168.1.100 -- > Jan 1 00:00:19 (none) user.info kernel: mini_fo: using storage directory: /jffs > Jan 1 00:00:20 (none) user.info : syslogd has already been started. > Jan 1 00:00:20 (none) user.info : klogd has already been started. > Jan 1 00:00:21 (none) user.info kernel: device eth0 entered promiscuous mode > Jan 1 00:00:21 (none) user.info kernel: br-lan: port 1(eth0) entering learning state > Jan 1 00:00:21 (none) user.info kernel: br-lan: topology change detected, propa gating > Jan 1 00:00:21 (none) user.info kernel: br-lan: port 1(eth0) entering forwardin g state > Jan 1 00:00:23 (none) user.info kernel: PPP generic driver version 2.4.2 > Jan 1 00:00:24 (none) user.info kernel: wlan: 0.8.4.2 (svn r2568) > Jan 1 00:00:25 (none) user.warn kernel: ath_hal: module license 'Proprietary' t aints kernel. > Jan 1 00:00:25 (none) user.info kernel: ath_hal: 0.9.30.13 (AR5212, AR5312, RF2 316, TX_DESC_SWAP) > Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: Minstrel automatic r ate control algorithm 1.2 (svn r2568) > Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: look around rate set to 10% > Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: EWMA rolloff level s et to 75% > Jan 1 00:00:26 (none) user.info kernel: ath_rate_minstrel: max segment size in the mrr set to 6000 us > Jan 1 00:00:26 (none) user.info kernel: wlan: mac acl policy registered > Jan 1 00:00:28 (none) user.info kernel: ath_ahb: 0.9.4.5 (svn r2568) > Jan 1 00:00:28 (none) user.info kernel: ath_pci: switching rfkill capability of f > Jan 1 00:00:28 (none) user.info kernel: ath_pci: switching per-packet transmit power control off > Jan 1 00:00:28 (none) user.warn kernel: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 1 1Mbps > Jan 1 00:00:28 (none) user.warn kernel: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 1 1Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > Jan 1 00:00:28 (none) user.warn kernel: wifi0: H/W encryption support: WEP AES AES_CCM TKIP > Jan 1 00:00:28 (none) user.warn kernel: wifi0: mac 11.0 phy 4.8 radio 7.0 > Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 1 for WME_AC_BE tra ffic > Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 0 for WME_AC_BK tra ffic > Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 2 for WME_AC_VI tra ffic > Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 3 for WME_AC_VO tra ffic > Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 8 for CAB traffic > Jan 1 00:00:28 (none) user.warn kernel: wifi0: Use hw queue 9 for beacons > Jan 1 00:00:28 (none) user.warn kernel: wifi0: Driver has Fon Karma 1.0 patches by Robin Wood <dninja@gmail.com> enabled > Jan 1 00:00:28 (none) user.info kernel: wifi0: Atheros 2315 WiSoC: mem=0xb00000 00, irq=3 > Jan 1 00:00:31 (none) user.info kernel: device ath0 entered promiscuous mode > Jan 1 00:00:31 (none) user.info kernel: br-lan: port 2(ath0) entering learning state > Jan 1 00:00:31 (none) user.info kernel: br-lan: topology change detected, propa gating > Jan 1 00:00:31 (none) user.info kernel: br-lan: port 2(ath0) entering forwardin g state > Jan 1 00:00:34 (none) cron.notice crond[471]: crond 2.3.2 dillon, started, log level 8 > Jan 1 00:00:35 (none) authpriv.info dropbear[475]: Running in background > Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: started, version 2.39 cachesize 150 > Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: compile time options: IPv6 GNU- getopt ISC-leasefile no-DBus no-I18N TFTP > Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: DHCP, IP range 192.168.1.100 -- 192.168.1.250, lease time 12h > Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: using local addresses only for domain lan > Jan 1 00:00:38 (none) daemon.warn dnsmasq[499]: failed to access /tmp/resolv.co nf.auto: No such file or directory > Jan 1 00:00:38 (none) daemon.info dnsmasq[499]: read /etc/hosts - 1 addresses > Jan 1 00:00:38 (none) daemon.err dnsmasq[499]: failed to read /etc/ethers:No su ch file or directory > Jan 1 00:01:12 (none) daemon.info dnsmasq[499]: DHCPDISCOVER(br-lan) 00:16:d4:b 6:32:8d > Jan 1 00:01:12 (none) daemon.info dnsmasq[499]: DHCPOFFER(br-lan) 192.168.1.122 00:16:d4:b6:32:8d > Jan 1 00:01:12 (none) daemon.info dnsmasq[499]: DHCPREQUEST(br-lan) 192.168.1.1 22 00:16:d4:b6:32:8d > Jan 1 00:01:12 (none) daemon.info dnsmasq[499]: DHCPACK(br-lan) 192.168.1.122 0 0:16:d4:b6:32:8d user-4ca4bc9414 > Jan 1 00:03:17 (none) user.warn kernel: KARMA: Whitelist mode > Jan 1 00:04:03 (none) user.warn kernel: KARMA: ssid ["Unix"] not found in white list so rejecting > Jan 1 00:04:03 (none) user.warn kernel: KARMA: ssid ["Unix"] not found in white list so rejecting > Jan 1 00:04:03 (none) user.warn kernel: KARMA: ssid ["Unix"] not found in white list so rejecting > Jan 1 00:04:50 (none) user.warn kernel: KARMA: Blacklist mode > Jan 1 00:06:03 (none) authpriv.info dropbear[667]: Child connection from 192.16 8.1.122:29330 > Jan 1 00:06:06 (none) authpriv.notice dropbear[667]: password auth succeeded fo r 'root' from 192.168.1.122:29330 > > Quote Link to comment Share on other sites More sharing options...
digininja Posted November 27, 2008 Share Posted November 27, 2008 Have you tried adding Unix to the ssid list and putting it in whitelist mode, see if it actually connects? Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 27, 2008 Author Share Posted November 27, 2008 yeah I tried that thinking that id just have to add the found AP's ssid's to the whitelist but that had the same effect as the black list. anything in the logs stand out? Quote Link to comment Share on other sites More sharing options...
digininja Posted November 27, 2008 Share Posted November 27, 2008 Nothing obvious, most people when they have this problem don't have the karma patched drivers but you definitely do. Can you try a different client? Maybe that client is probing but not associating when it gets a probe response. Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 27, 2008 Author Share Posted November 27, 2008 Nothing obvious, most people when they have this problem don't have the karma patched drivers but you definitely do. Can you try a different client? Maybe that client is probing but not associating when it gets a probe response. [/quot Seems to work ok with my ap. Ill try another laptop and see what happens. Also I did get a client to associate when I first got the fon running karma. As soon as I tried to ping it the client was gone.. ill let ya know what happens. Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 27, 2008 Author Share Posted November 27, 2008 Tried another Laptop with a different wireless card. Same thing. Maybe the fon is not running dhcp? What exactly do I need to check to see if thats working? Maybe my options in tftpd for dhcp server are not correct? Its probably something simple im looking over. Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 27, 2008 Author Share Posted November 27, 2008 OK, got something Added my linksys usb wifi to the same laptop as the fon. searched for AP's and found OpenWrt. With Karma on that shouldnt be there right? So i added OpenWrt to the white list and tried to connect. Now Jasager's page shows the connection. So that part works. Looks like karma may not be turning on. Quote Link to comment Share on other sites More sharing options...
digininja Posted November 27, 2008 Share Posted November 27, 2008 You should be able to find openwrt and it will respond to any probe requests. Is it that you aren't getting associations or an ip address? The two are distinct processes. A client has to first associate then it can optionally request an ip address through dhcp. If you add the one you want to associate to to the ssid list and you are in black list mode then it won't associate. Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 27, 2008 Author Share Posted November 27, 2008 Well if I manually try to connect it does associate and I get an ip. I thought with karma on it should mimmic any ssid a wireless card is looking for and automatically connect. Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 27, 2008 Author Share Posted November 27, 2008 OK, Not sure what happened but it started to work. associated, got an ip address. Then the wireless card started switching back and fourth between 2 of the ap's in my prefered list. Then the FON suddenly restarts by itself. !!! So close then it crashes. I tried reloading all the software but im still in the same boat. Ill keep messing with it and see what else i can figure out. Any idea why its restarting? Quote Link to comment Share on other sites More sharing options...
digininja Posted November 27, 2008 Share Posted November 27, 2008 I've never had one reboot on me. Sounds like a hardware problem. Jasager listens to probe requests and replies with a probe response. It is then up to the client whether they try to associate or not. Some clients remember the MAC address of the AP they want to connect to so won't connect if it isn't right. If the AP it is looking for is supposed to be encrypted then some clients won't associate because Jasager isn't encrypted. Basically, Jasager can't force a client to associate but it will be there if the client wants to. Quote Link to comment Share on other sites More sharing options...
compsystems Posted November 29, 2008 Author Share Posted November 29, 2008 FIXED!! When i added the dummy SSID's to my preferred wireless network I left the default security info. For me I needed to change it from wep to disabled. AKA a open network with no security. After that change everything worked as it should. Quote Link to comment Share on other sites More sharing options...
digininja Posted November 29, 2008 Share Posted November 29, 2008 Ye, some client software won't attach to a non-secure if it expects a secure one, some just fall back to unencrypted. Glad it is fixed Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.