Author Topic: CoovaAP firmware support  (Read 12546 times)

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
CoovaAP firmware support
« on: February 14, 2007, 12:46:06 pm »
Dear CoovaAP users,

Please upgrade to the latest coova firmware.

Coova is now worldspot recommended firmware.

Note that DD-WRT uses an older version of chillispot that still works well. However, it has a major design flaw that might cause problems to access paypal payment page.
You should NOT use DD-WRT (or chillispot) if you want to use paypal payments. Coova-chilli should be used instead.
« Last Edit: November 29, 2010, 10:41:32 am by WorldSpot »

Offline DenbyWireless

  • Sr. Member
  • ****
  • Posts: 111
Re: CoovaAP firmware support
« Reply #1 on: March 24, 2007, 01:56:44 am »
I'm attempting to run CoovaAp on a BuffaloTech WHR HP G54. 
I've loaded the Brodcom image, and it seems to be working fine.
I can surf via the WLan and Lan UNTIL I configure Hotspot.
I use Worldspots auto configuration, and apply the changes.

When I then connect to the WLan, all I get is time outs, no Worldsport page. LAN sufing is fine.

When I looked at the walled garden I did not see the worldspot servers that I had expected. (There are none)
Should I see WS servers in the Walled garden list ?

CoovaAP is giving me the following wireless address info
cap.coova.org
ip      10.1.1.10
mask 255.255.0.0
gw    10.1.0.1

I can ping 10.1.0.1, but that's about all.  I tried adding the Ws servers in the walled garden without success.

Also, I am getting an error in syslogs.
Mar 24 02:58:28 (none) kern.err chillispot[6711]: redir.c: 1517: 22 (Invalid argument) accept() failed!

I've check Coovachilli is running, but maybe one more Hard Reset, and re-configure will work.


Thanks
Aaron
« Last Edit: March 24, 2007, 04:05:36 am by DenbyWireless »

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: CoovaAP firmware support
« Reply #2 on: March 24, 2007, 10:06:24 am »
Quote
Also, I am getting an error in syslogs.
Mar 24 02:58:28 (none) kern.err chillispot[6711]: redir.c: 1517: 22 (Invalid argument) accept() failed!
I think this should be reported on the coova forum

Offline DenbyWireless

  • Sr. Member
  • ****
  • Posts: 111
Re: CoovaAP firmware support
« Reply #3 on: March 24, 2007, 07:03:59 pm »
Quote
Also, I am getting an error in syslogs.
Mar 24 02:58:28 (none) kern.err chillispot[6711]: redir.c: 1517: 22 (Invalid argument) accept() failed!
I think this should be reported on the coova forum

Yep, I'm posting there this morning.  I was curious about what you thought of the walled garden list being empty.
Is that expected ? I would have expected your radias servers and paypal.

Can you provide any manual setup instructions for Coova?

I'm pretty sure my problem is a gateway issue.

Another day, Another try...  :-*

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: CoovaAP firmware support
« Reply #4 on: March 24, 2007, 10:46:48 pm »
The way automatic configuration work is quite simple.
Coova downloads a chillispot configuration file from worldspot. This file is not fed into the nvram variables that are shown in the coova GUI.
It should work. If not, there is a bug somewhere.
Could you please post the syslog content. Thanks.
Coova works for me, but seems to cause problems to some people.
I forgot, please tell us about your hardware...

Thanks for testing.

Offline DenbyWireless

  • Sr. Member
  • ****
  • Posts: 111
Re: CoovaAP firmware support
« Reply #5 on: March 25, 2007, 12:44:07 am »
The way automatic configuration work is quite simple.
Coova downloads a chillispot configuration file from worldspot. This file is not fed into the nvram variables that are shown in the coova GUI.

Not in the nvram? Question is then is this loaded dynamically on router reboot ?

I've been sucessfull at getting the BuffaloTech WHR HP G54 working with the generic broadcom CoovaAP download.

I believe the 10.1.1.x network was giving me trouble in my home network (which is 3 networks deep).

By Enabling both WLAN and LAN for the Hotspot Mode, it took the LAN IP of 192.168.11.x which is working fine.
I also changed from DHCP to Static on the WAN and will play with it some more.

I'd have expected the Coova UI to display all the walled garden entries, including the config entries.

Also, I've attempted to add my MAC to the CoovaAP Authorized MAC list. Tried Radiaus Auth, and No Auth both fail to give me access.
I did see in WS Connections "not stopped Mac "00-14-A5-27-35-3D" unknown " logged. (from my testing I'm sure)

There are 2 things I need to do, I need to create non auth local logins for hot spot hosts and I need my MAC allowed to roam.
Should I not try and handle these via Coova, but instead use equivelent the WS features.  I tried a MAC ticket, that didnt' seem to work.
Thanks for the help
« Last Edit: March 25, 2007, 05:19:04 am by DenbyWireless »

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: CoovaAP firmware support
« Reply #6 on: March 25, 2007, 05:38:36 pm »
The way automatic configuration work is quite simple.
Coova downloads a chillispot configuration file from worldspot. This file is not fed into the nvram variables that are shown in the coova GUI.

Not in the nvram? Question is then is this loaded dynamically on router reboot ?
Yes I think. It is also reloaded periodically.
Quote
I've been sucessfull at getting the BuffaloTech WHR HP G54 working with the generic broadcom CoovaAP download.

I believe the 10.1.1.x network was giving me trouble in my home network (which is 3 networks deep).
This shouldn't be a problem, except if the 10.1.1.x subnet is already used.
Quote
By Enabling both WLAN and LAN for the Hotspot Mode, it took the LAN IP of 192.168.11.x which is working fine.
I also changed from DHCP to Static on the WAN and will play with it some more.

I'd have expected the Coova UI to display all the walled garden entries, including the config entries.
You can read the configuration by typing the config url in a browser.
Quote
Also, I've attempted to add my MAC to the CoovaAP Authorized MAC list. Tried Radiaus Auth, and No Auth both fail to give me access.
I did see in WS Connections "not stopped Mac "00-14-A5-27-35-3D" unknown " logged. (from my testing I'm sure)
Radius auth is certainly for WPA radius. I don't know if worldspot is compatible with that. This is not using chillispot.
Quote
There are 2 things I need to do, I need to create non auth local logins for hot spot hosts and I need my MAC allowed to roam.
Should I not try and handle these via Coova, but instead use equivelent the WS features.  I tried a MAC ticket, that didnt' seem to work.
Thanks for the help
I don't know if I tried the mac address authentication with coova. Have you enabled the mac address authentication in the hotspot configuration? This is something that I haven't explicitely enabled in the autoconfiguration.
I don't know if local mac address authentication work also. I haven't tested it.
I can't test it until next week, as I'm not at home this week. (vacations... ;-))

Offline DenbyWireless

  • Sr. Member
  • ****
  • Posts: 111
Re: CoovaAP firmware support to include US servers
« Reply #7 on: May 11, 2007, 11:51:13 pm »
Well now that we have some US base servers to use, it would be nice to be able to point to them using Coova firmware.

I do not seem to be able to configure this having used the AUTO settings.

Can we make changes either to the HS config menu to include the servers or have manual instructions for configuring Coova so that we can pick the US Servers.
Thanks
Aa

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: CoovaAP firmware support
« Reply #8 on: May 12, 2007, 08:16:55 am »
The US server still lacks an SSL certificate. I will set it up next week and modify the coova auto config with an option.
Is this server more responsive for you?

To do that manually, you can switch the radius servers, then use https://us.worldspot.net/wk/Uam as the uam page.

Offline DenbyWireless

  • Sr. Member
  • ****
  • Posts: 111
Re: CoovaAP firmware support
« Reply #9 on: May 13, 2007, 04:35:50 am »
tracert us.worldspot.net

Tracing route to us.worldspot.net [75.126.126.145]
over a maximum of 30 hops:

  1     5 ms     5 ms     5 ms  192.168.1.13
  2    10 ms     6 ms    12 ms  192.168.0.1
  3    17 ms    17 ms    12 ms  d207-216-48-254.bchsia.telus.net [207.216.48.254]
  4    15 ms    16 ms    16 ms  NNIMBC01DR01.bb.telus.com [208.181.240.2]
  5    16 ms    16 ms    19 ms  nwmrbc01gr01.bb.telus.com [154.11.4.66]
  6    72 ms    21 ms    19 ms  204.225.243.22
  7    20 ms    20 ms    26 ms  so-3-3-2.cr1.sea1.us.above.net [208.185.175.69]
  8    32 ms    26 ms    21 ms  so-0-0-0.cr2.sea1.us.above.net [64.125.28.186]
  9    48 ms    41 ms    38 ms  so-2-1-0.mpr2.sjc2.us.above.net [64.125.28.21]
 10    88 ms    86 ms   140 ms  so-3-2-0.cr1.dfw2.us.above.net [64.125.29.54]
 11   162 ms    88 ms   100 ms  ge4-14.cer01.dal01.softlayer.com [64.124.79.206]
 12    85 ms   108 ms    90 ms  po51.fcr01.dal01.softlayer.com [66.228.118.150]
 13    86 ms    85 ms    86 ms  vz64bit01.cp40.thtdomains.com [75.126.17.72]
 14   165 ms    84 ms    87 ms  us.worldspot.net [75.126.126.145]

Trace complete.

tracert worldspot.net

Tracing route to worldspot.net [88.191.29.2]
over a maximum of 30 hops:

  1     4 ms     4 ms     4 ms  192.168.1.13
  2    42 ms     4 ms     5 ms  192.168.0.1
  3    16 ms    17 ms    17 ms  d207-216-48-254.bchsia.telus.net [207.216.48.254]
  4    16 ms    17 ms    17 ms  NNIMBC01DR02.bb.telus.com [208.181.240.6]
  5    17 ms    17 ms    17 ms  nwmrbc01gr01.bb.telus.com [154.11.4.98]
  6    19 ms    20 ms    26 ms  204.225.243.22
  7    21 ms    20 ms    19 ms  bpr4-so-4-0-0.SeattleSwitchDesign.savvis.net [208.173.50.
  8    22 ms    22 ms    19 ms  acr2-as0-0.seattle.savvis.net [208.172.83.66]
  9    24 ms    19 ms    78 ms  acr1-ae0.Seattle.savvis.net [208.172.83.45]
 10    43 ms    35 ms    97 ms  dcr1-so-0-2-0.SanFranciscosfo.savvis.net [204.70.193.66]
 11    50 ms    54 ms    38 ms  dcr2-so-5-0-0.SanFranciscosfo.savvis.net [204.70.192.150]
 12    36 ms    39 ms    36 ms  cpr2-pos-6-0.sanjoseequinix.savvis.net [204.70.194.154]
 13    53 ms    50 ms    50 ms  bpr2-so-3-0-0.sanjoseequinix.savvis.net [208.175.172.174]
 14    44 ms    39 ms    42 ms  if-3-0.mcore3.PDI-PaloAlto.teleglobe.net [216.6.33.6]
 15   150 ms   200 ms   212 ms  if-6-0.mcore4.PDI-PaloAlto.teleglobe.net [216.6.86.21]
 16   110 ms   104 ms   112 ms  if-4-0.mcore4.NQT-NewYork.teleglobe.net [216.6.86.14]
 17   212 ms   223 ms   185 ms  if-3-0.core2.PG1-Paris.teleglobe.net [216.6.87.26]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   185 ms   185 ms   185 ms  bzn-6k-4-po3-t.intf.routers.proxad.net [212.27.58.42]
 21   191 ms   185 ms   185 ms  88.191.2.25
 22   183 ms   186 ms   185 ms  88.191.2.21
 23   193 ms   185 ms   185 ms  worldspot.net [88.191.29.2]

Trace complete.

Offline DenbyWireless

  • Sr. Member
  • ****
  • Posts: 111
Re: CoovaAP firmware support
« Reply #10 on: March 06, 2008, 12:26:06 am »
I'm planning my summer roll out of hotspots and realized that there are new versions of Coova.

Can I ask what version of Coova you would suggest (currently) for 'stable' worldspot/Coova hotspots ?

I think I'm running Beta 4 from last year.

Thanks..
I also thought I'd include a current trace route list for both worldspot servers from here in BC Canada.
Actually less hops to the UK than US server. Funny as we are only about 200mi from Seattle.

>tracert us.worldspot.net

Tracing route to www2.worldspot.net [72.36.188.97]
over a maximum of 30 hops:

  1     6 ms     7 ms     3 ms  192.168.1.13
  2     7 ms     5 ms     5 ms  home [192.168.0.1]
  3    17 ms    16 ms    14 ms  d207-216-48-254.bchsia.telus.net [207.216.48.254]
  4    19 ms    16 ms    15 ms  c2-0.kntaonacdr01.bb.telus.com [154.11.88.193]
  5    21 ms    19 ms    19 ms  204.225.243.22
  6    24 ms    20 ms    24 ms  bpr4-so-4-0-0.SeattleSwitchDesign.savvis.net [208.173.50
  7    21 ms    23 ms    23 ms  cr2-pos-0-3-0-1.Seattle.savvis.net [204.70.200.77]
  8    85 ms   109 ms     *     cr1-loopback.dan.savvis.net [208.172.130.70]
  9    74 ms    75 ms    75 ms  204.70.193.26
 10    77 ms    77 ms    75 ms  216.39.69.206
 11     *        *        *     Request timed out.
 12    92 ms    88 ms    84 ms  server.thelegender.com [72.36.176.202]
 13    76 ms    82 ms    78 ms  usa2.worldspot.net [72.36.188.97]

Trace complete.

>tracert worldspot.net

Tracing route to worldspot.net [213.251.168.19]
over a maximum of 30 hops:

  1     7 ms     4 ms     6 ms  192.168.1.13
  2     5 ms     5 ms     5 ms  home [192.168.0.1]
  3    15 ms    17 ms    17 ms  d207-216-48-254.bchsia.telus.net [207.216.48.254]
  4    25 ms    17 ms    16 ms  c2-0.kntaonacdr01.bb.telus.com [154.11.88.193]
  5    80 ms    81 ms    77 ms  toroonxngr00.bb.telus.com [154.11.11.54]
  6    85 ms    79 ms    78 ms  212.184.27.21
  7   174 ms   171 ms   169 ms  217.239.38.162
  8   169 ms   166 ms   167 ms  010G.th2-1-6k.routers.ovh.net [213.186.32.205]
  9   166 ms   167 ms   166 ms  040G.p19-2-6k.routers.ovh.net [213.186.32.150]
 10   170 ms   167 ms   165 ms  p19-25-m1.routers.ovh.net [213.251.130.206]
 11   166 ms   171 ms   168 ms  ovh.worldspot.net [213.251.168.19]

Trace complete.

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: CoovaAP firmware support
« Reply #11 on: March 06, 2008, 02:29:58 pm »
I tried latest coova beta 7d without any problem.
I think you should upgrade.

About the traceroute, it seems that you are 21ms from seattle.
But the geo localisation of the server ip seems to be new york.
This explains why...