Home › Forums › Open-Source Software › CoovaAP Firmware

HEX Conversion failure

Wed, 09/02/2009 - 17:51 — urugn

Hi guys!

First an fore most thanks to coova for such a wonderful product.

Was wondering what could have coursed a HEX Conversion failure in my CoovaAP setup. I received this error after i changed my linksys WRT54G wan setting to reflect a new isp settings then moved the router to a new internet gateway. Other wise it was working fine just fine. Radius is okey only the syslog status shows the error

kern.err coova-chilli[1469]: redir.c: 84: HEX conversion failed!

I have googled for the solution but couldn't find an answer to the HEX. Once again many thanks.

‹ How do I manage user data? Persisent Walled Garden entry ›
Thu, 09/10/2009 - 05:34 — ajmv

HEX Conversion failure & DHCP Server

In some moment I saw on the syslog the HEX Conversion failure in my CoovaAP 1.0-beta.8, running on Buffalo WHR-HP-G54 (openwrt-brcm-2.4-squashfs.trx)

Connect by wire, no wireless by now, my DHCP Server (LAN side) was configured as follow:

Starting Address: 192.168.11.100
Number of Addresses: 150

I perceive that the AP assign the address for the first computer added to the network the address 192.168.11.148, then connect another computer and this assign the 192.168.11.244, unplug one network cable and plugin again and the DHCP server don't assign address.

I don't modified parameters on the DHCP server, it's the default configuration, I don't know what to do. I waiting 100 and 101.

Sorry, my english is poorly

Thu, 09/03/2009 - 15:54 — urugn

Flashed the router then

Flashed the router then reconfigured but still no luck. What could be the problem?

Tue, 09/08/2009 - 10:09 — Beone

I have no idea. I had that

I have no idea.
I had that error too when i tried the new coovaAP, BUT it didn't prevent anything from working.
So yes, i noticed that error, but it didn't break anything for me. Everything was working fine.
Your problem must be somewhere else.

Kind regards
B

Wed, 09/09/2009 - 17:48 — urugn

Thanks men. You mean to say

Thanks men.

You mean to say the Hex conversion failed error wont prevent the login. I would like to be sure so i do some more trouble shooting.
Only worked once upon initial login with radius but then after that the browser gets stack on please wait upon radius authentication with syslog showing the error. Still havent figured out how to solve it.

Thanks

Thu, 09/10/2009 - 10:39 — Beone

We use radius auth with uam

We use radius auth with uam and a php login script.
We haven't seen any problems with the newest version so far. (As mentioned, we've seen this error too, but it didn't break anything we noticed)

Kind regards

Fri, 09/11/2009 - 11:31 — urugn

Well Beone you are write just

Well Beone you are write just did an mtd erase nvram then configured CoovaChilli UAM with Auto Configuration Disabled.

The router showed the Terms and conditions and upon accept i was logged in to the internet. Next step is to customize it with my radius server through a PAP UAM service. then check where i was going wrong. Again Maaannny Thanks.

Fri, 09/11/2009 - 13:06 — urugn

WORKING GOOD!

Still can't tell where i was going wrong but at this very minute the hotspot is working with my custom radius and PAP UAM Service.
Just noticed some miss configuration in /etc/chilli/main.conf which i had to solve manually there after i was good to go. lastly just hacked the PAP UAM Service to run under a jsp/servlet container. And very final is to say manny Thannks!!