dustbyter Posted April 23, 2014 Share Posted April 23, 2014 Karma seems to be acting up. In the log we can see that a device sucessfully associated, but in the intelligence tab, the information such as IP address in not displayed. Karma log contents Apr 23 12:50:04 KARMA: Successful association of 78:ca:39:b1:83:5F Apr 23 12:50:04 KARMA: Checking SSID for start of association, pass through Luxor Apr 23 12:50:01 KARMA: Probe Request from 78:ca:39:b1:83:5F for SSID 'Luxor' Apr 23 12:50:01 KARMA: Checking SSID for start of association, pass through Luxor Data on intelligence tab Karma Intelligence Report HW Address IP Address hostname SSID Additionally, i checked the /tmp/dhcp.leases file and it is blank. I expected to see something there. Is anyone else having this issue? Quote Link to comment Share on other sites More sharing options...
Foxtrot Posted April 23, 2014 Share Posted April 23, 2014 my dhcp.leases has entrys in it for my clients. Quote Link to comment Share on other sites More sharing options...
TYTechnolust Posted April 23, 2014 Share Posted April 23, 2014 Karma seems to be acting up. In the log we can see that a device sucessfully associated, but in the intelligence tab, the information such as IP address in not displayed. Karma log contents Apr 23 12:50:04 KARMA: Successful association of 78:ca:39:b1:83:5F Apr 23 12:50:04 KARMA: Checking SSID for start of association, pass through Luxor Apr 23 12:50:01 KARMA: Probe Request from 78:ca:39:b1:83:5F for SSID 'Luxor' Apr 23 12:50:01 KARMA: Checking SSID for start of association, pass through Luxor Data on intelligence tab Karma Intelligence Report HW Address IP Address hostname SSID Additionally, i checked the /tmp/dhcp.leases file and it is blank. I expected to see something there. Is anyone else having this issue? Did you update karma? Newest was released yesterday. Before that I was having similar issues. Quote Link to comment Share on other sites More sharing options...
Foxtrot Posted April 23, 2014 Share Posted April 23, 2014 I am actually using an older version of the karma tile and im atleast seeing things in my dhcp, which to me either means that his clients arnt actually connected or there is another issue. Quote Link to comment Share on other sites More sharing options...
TYTechnolust Posted April 23, 2014 Share Posted April 23, 2014 I am actually using an older version of the karma tile and im atleast seeing things in my dhcp, which to me either means that his clients arnt actually connected or there is another issue. I also saw DHCP, it was just the intelligence report for me.....similar to above Quote Link to comment Share on other sites More sharing options...
dustbyter Posted April 23, 2014 Author Share Posted April 23, 2014 (edited) Mine is the latest and greatest version. I have not yet rebooted the MKV. Does it require it? EDIT: Still the same behavior. My configuration is: Firmware: 1.3.0 Karma: 1.9 (at least, based on the handler.php file) <?php ######################### # User Variables # # Please edit these # ######################### $name = 'Karma'; #Name of tile $updatable = 'false'; #Should this tile auto-refresh $version = '1.9'; I am explicitly searching for networks that don't exist through my device to get Karma to associate with them and then checking the intelligence report and dhcp.leases. They are both empty. Edited April 23, 2014 by dustbyter Quote Link to comment Share on other sites More sharing options...
TYTechnolust Posted April 23, 2014 Share Posted April 23, 2014 Mine is the latest and greatest version. I have not yet rebooted the MKV. Does it require it? I believe just refreshing your browser will do it but a reboot cant hurt. Quote Link to comment Share on other sites More sharing options...
dustbyter Posted April 23, 2014 Author Share Posted April 23, 2014 Think i found out part of the issue at least. The connected devices are getting an IP from the router that is connected to the MKV over ethernet. I would expect that the IP address is assigned through the MKV. I can always disable DHCP on the router one hop away from the MKV which is assigning addresses, but would be nice to fix this on pineapple. Quote Link to comment Share on other sites More sharing options...
lunokhod Posted April 23, 2014 Share Posted April 23, 2014 (edited) Think i found out part of the issue at least. The connected devices are getting an IP from the router that is connected to the MKV over ethernet. I would expect that the IP address is assigned through the MKV. I can always disable DHCP on the router one hop away from the MKV which is assigning addresses, but would be nice to fix this on pineapple. Are you connecting the MkV directly to an existing Ethernet based network with it's own DHCP server/router/etc? The DHCP server on the MkV also works on the Ethernet port... it's configured to connect to a computer/laptop/client device and hand out an IP address. I tried changing the erh0 config in my Mk5 by disabling the built in DHCP server and assigning a fixed IP address so it could connect to an exisiting Ethernet network to access the internet. It sort of worked... but this also seemed to break a lot of stuff. It's probably not a good idea to have two fighing DHCP servers on a single wired network. I'm hoping that one day I can plug in a USB-Ethernet adapter into the Mk5 (2nd wired Ethernet eth1) and then connect this to an existing network for internet/admin access. It's the one method of getting internet connectivity to the MkV that has been overlooked. Lunokhod Edited April 23, 2014 by lunokhod 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.