FON Boards

Hi,

I have noticed that FON wireless keeps jumping up and down. It never stayed for more than 5 mins. Here is the output of logread:
==============
Oct 30 23:59:40 Fonera user.crit fonstated: enqueue --> hotspot_wdt_stop
Oct 30 23:59:40 Fonera user.crit fonstated: running fast event hotspot_wdt_stop
Oct 30 23:59:40 Fonera user.crit fonstated: stopping chilli wdt
Oct 30 23:59:40 Fonera user.crit fonstated: enqueue --> hotspot_wdt_start
Oct 30 23:59:40 Fonera user.crit fonstated: running fast event hotspot_wdt_start
Oct 30 23:59:40 Fonera user.crit fonstated: starting chilli wdt
Oct 31 00:00:30 Fonera user.alert fonstated: redirector returned invalid data
Oct 31 00:00:30 Fonera user.crit fonstated: enqueue --> RestartChilli
Oct 31 00:00:30 Fonera user.crit fonstated: running event /etc/fonstated/RestartChilli
Oct 31 00:00:45 Fonera user.err syslog: main-radconfig.c: 34: Radius request timed out
Oct 31 00:01:31 Fonera local6.info chillispot[16705]: tun.c: 664: 2 (No such file or directory) TX queue length set to 100
Oct 31 00:01:31 Fonera user.crit fonstated: finished running /etc/fonstated/RestartChilli
Oct 31 00:01:31 Fonera local6.info chillispot[16705]: ChilliSpot 1.0-coova.4. Copyright 2002-2005 Mondru AB. Licensed under GPL. Copyright 2006 Coova Technologies Ltd. Licensed under GPL. See http://www.chillispot.org for credits.
Oct 31 00:01:31 Fonera user.crit fonstated: enqueue --> hotspot_wdt_stop
Oct 31 00:01:31 Fonera user.crit fonstated: running fast event hotspot_wdt_stop
Oct 31 00:01:31 Fonera user.crit fonstated: stopping chilli wdt
Oct 31 00:01:31 Fonera user.crit fonstated: enqueue --> hotspot_wdt_start
Oct 31 00:01:31 Fonera user.crit fonstated: running fast event hotspot_wdt_start
Oct 31 00:01:31 Fonera user.crit fonstated: starting chilli wdt
Oct 31 00:02:21 Fonera user.alert fonstated: redirector returned invalid data
Oct 31 00:02:21 Fonera user.crit fonstated: enqueue --> RestartChilli
Oct 31 00:02:21 Fonera user.crit fonstated: running event /etc/fonstated/RestartChilli
Oct 31 00:02:37 Fonera user.err syslog: main-radconfig.c: 34: Radius request timed out
Oct 31 00:03:21 Fonera local6.info chillispot[16839]: tun.c: 664: 2 (No such file or directory) TX queue length set to 100
Oct 31 00:03:21 Fonera user.crit fonstated: finished running /etc/fonstated/RestartChilli
Oct 31 00:03:21 Fonera local6.info chillispot[16839]: ChilliSpot 1.0-coova.4. Copyright 2002-2005 Mondru AB. Licensed under GPL. Copyright 2006 Coova Technologies Ltd. Licensed under GPL. See http://www.chillispot.org for credits.
Oct 31 00:03:21 Fonera user.crit fonstated: enqueue --> hotspot_wdt_stop
Oct 31 00:03:21 Fonera user.crit fonstated: running fast event hotspot_wdt_stop
Oct 31 00:03:21 Fonera user.crit fonstated: stopping chilli wdt
Oct 31 00:03:21 Fonera user.crit fonstated: enqueue --> hotspot_wdt_start
Oct 31 00:03:21 Fonera user.crit fonstated: running fast event hotspot_wdt_start
Oct 31 00:03:21 Fonera user.crit fonstated: starting chilli wdt
Oct 31 00:04:08 Fonera user.warn kernel: Rcv Wcid(1) AddBAReq
Oct 31 00:04:08 Fonera user.warn kernel: Start Seq = 00000f8f
Oct 31 00:04:12 Fonera user.alert fonstated: redirector returned invalid data
Oct 31 00:04:12 Fonera user.crit fonstated: enqueue --> RestartChilli
Oct 31 00:04:12 Fonera user.crit fonstated: running event /etc/fonstated/RestartChilli
Oct 31 00:04:27 Fonera user.err syslog: main-radconfig.c: 34: Radius request timed out
Oct 31 00:04:36 Fonera authpriv.info dropbear[16946]: Child connection from 192.168.2.197:63136
==================

Does anyone have the same experience? Am I doing something wrong with configuration? I did reboot, restore to manufacture setting and etc.

It looks to me like it is unable to reach (or losing it's connection to) Fon's RADIUS server. Could be you have ports blocked, could be the router isn't getting a (stable) connection to the Internet.

What port does it need? I can set port forwarding.

Thanks for your help.

Is your Fonera plugged in after another router? If so, i'm amazed that you didn't think to mention that.

Sorry, I should have mentioned about it. It is sitting behind Version FIOS router. I used to have FON Fonera G router, it used to work and I didn't change anything except replacing Fonera G with 2.0N.

I am not so sure this will help but it seems the cthulhu.fon.com is not pingable.
=================
root@Fonera:/etc/fon# cat fonsmcd.conf
# fonsmcd configuration file
# $Id$
suffix .sm.fon.com
period_online 60
period_offline 5
rsapath "/etc/public_sm_rsa_key.pem"
aespath "/etc/aes_key"
host cthulhu.fon.com 54 UDP
timeout 3000
retries 5
trigger 1 "/bin/thinclient config 'DATA'"
trigger 2 "/bin/thinclient upgrade 'DATA'"
trigger online "fs -l HotspotStart"
trigger offline "fs -l HotspotStop"
root@Fonera:/etc/fon# ping cthulhu.fon.com
PING cthulhu.fon.com (213.134.45.88): 56 data bytes
=================

Here's the latest list of ports which La Foneras need open/forwarded... this is a little more up to date than even the wiki

Port Protocol Description
53 TCP/UDP FON DNS Heartbeat
80 TCP HTTP FON web server
123 TCP/UDP NTP
443 TCP HTTPS FON web server
1645 UDP CHILI RADIUS
1812 UDP CHILI RADIUS Authentication
1813 UDP CHILI RADIUS Accounting
1937 TCP Fon SSH Heartbeat/updates
1938 TCP Fon SSH Heartbeat/updates
3990 TCP Coofachilli port normally internal but may be needed depending on firewall/router

http://wiki.fon.com/wiki/Installation_&_Registration#Which_ports_do_La_Fonera_needs.3F
http://wiki.fon.com/wiki/Firewall

And, yeah I know you can't ping cthulhu or reverse-lookup on it.

Of course... one should count his blessings... the day the Great Old One answers your call, you will have bigger problems than getting a crappy router to work!

I put the Fon in DMZ, reboot the router and then still getting same error with some new error:
=============
Nov 5 04:07:59 Fonera local6.info chillispot[1907]: options.c: 782: Rereading configuration file and doing DNS lookup
Nov 5 04:08:00 Fonera user.crit fonstated: enqueue --> HotspotStop
Nov 5 04:08:00 Fonera user.crit fonstated: running event /etc/fonstated/HotspotStop
Nov 5 04:08:00 Fonera local6.err chillispot[1907]: dhcp.c: 2260: 127 (Network is down) recv(fd=12, len=1534) failed
Nov 5 04:08:00 Fonera local6.err chillispot[1907]: chilli.c: 3339: dhcp_decaps() failed!
Nov 5 04:08:00 Fonera local6.err chillispot[1907]: dhcp.c: 2471: 127 (Network is down) recv(fd=13, len=42) failed
Nov 5 04:08:00 Fonera local6.err chillispot[1907]: chilli.c: 3344: dhcp_arpind() failed!
Nov 5 04:08:00 Fonera user.crit fonstated: finished running /etc/fonstated/HotspotStop
Nov 5 04:08:00 Fonera user.crit fonstated: enqueue --> hotspot_wdt_stop
Nov 5 04:08:00 Fonera user.crit fonstated: running fast event hotspot_wdt_stop
Nov 5 04:08:00 Fonera user.crit fonstated: stopping chilli wdt
Nov 5 04:08:00 Fonera user.crit fonstated: enqueue --> hotspot_wdt_stop
Nov 5 04:08:00 Fonera user.crit fonstated: running fast event hotspot_wdt_stop
Nov 5 04:08:00 Fonera user.crit fonstated: stopping chilli wdt
Nov 5 04:08:05 Fonera authpriv.info dropbear[2049]: Child connection from 192.168.2.197:49888
Nov 5 04:08:13 Fonera authpriv.notice dropbear[2049]: password auth succeeded for 'root' from 192.168.2.197:49888
root@Fonera:~# logread -f
Nov 5 04:09:09 Fonera authpriv.info dropbear[2070]: Child connection from 192.168.2.197:49903
Nov 5 04:09:15 Fonera authpriv.notice dropbear[2070]: password auth succeeded for 'root' from 192.168.2.197:49903
Nov 5 04:09:47 Fonera daemon.info dnsmasq[1809]: DHCPDISCOVER(br-lan) 192.168.1.6 00:21:29:66:48:22
Nov 5 04:09:47 Fonera daemon.info dnsmasq[1809]: DHCPOFFER(br-lan) 192.168.2.11 00:21:29:66:48:22
Nov 5 04:10:30 Fonera user.err syslog: main-radconfig.c: 34: Radius request timed out
Nov 5 04:11:15 Fonera user.crit fonstated: enqueue --> hotspot_wdt_stop
Nov 5 04:11:15 Fonera user.crit fonstated: running fast event hotspot_wdt_stop
Nov 5 04:11:15 Fonera user.crit fonstated: stopping chilli wdt
Nov 5 04:11:30 Fonera user.err syslog: main-radconfig.c: 34: Radius request timed out
Nov 5 04:12:16 Fonera local6.info chillispot[2214]: tun.c: 664: 2 (No such file or directory) TX queue length set to 100
Nov 5 04:12:16 Fonera local6.info chillispot[2214]: ChilliSpot 1.0-coova.4. Copyright 2002-2005 Mondru AB. Licensed under GPL. Copyright 2006 Coova Technologies Ltd. Licensed under GPL. See http://www.chillispot.org for credits.
Nov 5 04:12:16 Fonera user.crit fonstated: enqueue --> hotspot_wdt_start
Nov 5 04:12:16 Fonera user.crit fonstated: running fast event hotspot_wdt_start
Nov 5 04:12:16 Fonera user.crit fonstated: starting chilli wdt
Nov 5 04:12:18 Fonera user.warn kernel: Rcv Wcid(1) AddBAReq
Nov 5 04:12:18 Fonera user.warn kernel: Start Seq = 000005b0
Nov 5 04:12:20 Fonera daemon.info dnsmasq[1809]: DHCPDISCOVER(br-lan) 169.254.186.183 00:21:29:66:48:22
Nov 5 04:12:20 Fonera daemon.info dnsmasq[1809]: DHCPOFFER(br-lan) 192.168.2.11 00:21:29:66:48:22
Nov 5 04:12:57 Fonera user.alert fonstated: redirector returned invalid data
Nov 5 04:12:57 Fonera user.crit fonstated: enqueue --> RestartChilli
Nov 5 04:12:57 Fonera user.crit fonstated: running event /etc/fonstated/RestartChilli
Nov 5 04:13:13 Fonera user.err syslog: main-radconfig.c: 34: Radius request timed out
Nov 5 04:13:32 Fonera daemon.info dnsmasq[1809]: DHCPDISCOVER(br-lan) 169.254.186.183 00:21:29:66:48:22
Nov 5 04:13:32 Fonera daemon.info dnsmasq[1809]: DHCPOFFER(br-lan) 192.168.2.11 00:21:29:66:48:22
Nov 5 04:13:32 Fonera daemon.info dnsmasq[1809]: DHCPREQUEST(br-lan) 192.168.2.11 00:21:29:66:48:22
Nov 5 04:13:32 Fonera daemon.info dnsmasq[1809]: DHCPACK(br-lan) 192.168.2.11 00:21:29:66:48:22 torrent
Nov 5 04:13:35 Fonera daemon.info dnsmasq[1809]: DHCPREQUEST(br-lan) 192.168.2.11 00:21:29:66:48:22
Nov 5 04:13:35 Fonera daemon.info dnsmasq[1809]: DHCPACK(br-lan) 192.168.2.11 00:21:29:66:48:22 torrent

===============

Hmmmmmmmm......... What else I could try to narrow down the problem.

DMZ is not the same as forwarding ports. You need to actually forward those ports.

I don't understand what it is with people. Every time I've asked folks to forward ports this month, they configured DMZ instead and then came back, bewildered.

Same problem here on the 2.0g:



Every minute or two.
Fonera is behind a router, outbound ports are all open. Even if I connect it directly into the modem, the effect would be the same - ISP blocks all incoming requests.

Same effect on flipper 2.2.5 and on latest RC 20090922 2.3.0.1.
I bought a used fonera from a friend and fon support changed ownership to me.

could you checkout : netstat -an | grep "TCP"
I guess there are some "time_wait"?
I believe the radius is something like 1812/udp & tcp
and it's towards radconfig02.fon.com
and radconfig01.fon.com
can you ping those url's from eg the fonera?

One TIME_WAIT



Hosts resolve, but no ping responses.

PING radconfig02.fon.com (213.134.45.163): 56 data bytes
PING radconfig01.fon.com (213.134.45.162): 56 data bytes

I also tried telnet to those two servers port 1812 and no success from anywhere (even on a machine directly connected to the internet).

they never give ping responses...Can't even telnet them
they resolve fine...strange

I believe Iurgi allready saw this happenning once...perhaps you could pm him for more info?
he doesn't often look at the forums
perhaps tell him name/country of your isp & modem type/model so he can cross reference?

can you perform some kind of wireshark on that fios router?
perhaps there is some kind of "nat" issue...
eg the radius config is going out...without proper nat....and the response ends upon your internet modem....it will never arrive on your fonera due to improper nat...

no such issue on regular networks...but in your case?

your lan is 192.168.1.*
your dmz is 192.168.2.* ?

I'll try sending him a PM. Good thing is it's limited to chilli restarts so my private wifi works fine.
Thanks for the help so far.


My setup is really simple, my linksys router is connected to my vdsl modem and gets the public ip via DHCP from my ISP. Inside I got a 192.168.2.1 ip on the router and a static ip of 192.168.2.2 on the fonera (with gateway 192.168.2.1 and properly entered dns server).

I can try putting the fonera into dmz maybe it will help, but afaik there isn't any outgoing filtering. Also my ISP blocks all incoming requests.

Edit: restarts happen in DMZ too.

perhaps it's an MTU issue ?

MTU is set to auto on the linksys. Any particular value I should try?

anything lower than 1500?