09:18:40.055081 IP 192.168.2.25.4097 > 213.134.45.129.53:  2+ A? download.fon.com. (34)

Risoluzione di download.fon.com utilizzando come DNS 213.134.45.129. Riprova ogni 60 secondi, probabilmente è il crontab che esegue /bin/thinclient cron

09:26:51.452722 IP 192.168.2.25.4205 > 213.134.45.191.80: S 147362619:147362619(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>

Download del file http://download.fon.com/heartbeat.php che contiene la stringa OK. Appena riesce il wget, viene attivata l'interfaccia WiFi ath0.

09:39:46.289010 IP 192.168.2.25.4099 > 213.134.45.129.53:  2+ A? ntp1.linuxmedialabs.com. (41)
09:39:46.525209 IP 213.134.45.129.53 > 192.168.2.25.4099:  2 1/4/0 A 63.247.194.250 (140)
09:39:46.526836 IP 192.168.2.25.4098 > 63.247.194.250.123: NTPv3, Client, length 48

Risoluzione DNS per un server NTP, sincronizzazione NTP. La Fonera non ha un clock interno, parte con Sat Jan 1 00:00:00 UTC 2000.

09:39:47.327100 IP 192.168.2.25.4099 > 213.134.45.129.53:  2+ A? radius01.fon.com. (34)
09:39:47.392463 IP 213.134.45.129.53 > 192.168.2.25.4099:  2 1/5/5 A 213.134.45.160 (232)
09:39:47.394310 IP 192.168.2.25.4099 > 213.134.45.129.53:  3+ A? rad02.hotradius.com. (37)
09:39:47.458687 IP 213.134.45.129.53 > 192.168.2.25.4099:  3 3/2/2 CNAME rad02.chillispot.org., CNAME radius.chillispot.org., A 66.150.225.159 (187)
09:39:47.463027 IP 192.168.2.25.4099 > 213.134.45.160.1812: RADIUS, Access Request (1), id: 0x00 length: 105
09:39:47.463063 IP 192.168.2.2 > 192.168.2.25: ICMP 213.134.45.160 udp port 1812 unreachable, length 141
09:39:52.466730 IP 192.168.2.25.4099 > 66.150.225.159.1812: RADIUS, Access Request (1), id: 0x00 length: 105
09:39:52.466786 IP 192.168.2.2 > 192.168.2.25: ICMP 66.150.225.159 udp port 1812 unreachable, length 141
09:39:57.476365 IP 192.168.2.25.4099 > 66.150.225.159.1812: RADIUS, Access Request (1), id: 0x00 length: 105
09:39:57.476407 IP 192.168.2.2 > 192.168.2.25: ICMP 66.150.225.159 udp port 1812 unreachable, length 141

Autenticazione RADIUS??