[Chilli] CoovaChilli Kernel Mode issue

Thu Nov 28 11:36:07 UTC 2013

Hi Russell,

I saw your mails to the list regarding the redir error message and hoped I could get some clues. So far, I am still stuck :( In my case, when I see redir_read messages in the server's syslog, it normally means that clients see "The connection was reset" error in their browsers and can't go anywhere. They don't even see the "redirecting" message with the animated circle (www/wait.gif).

I tried different config settings. If I make HS_UAMLISTEN address in the same range as HS_NETWORK, clients do see redirection/login pages but that's all. I don't see any record in /proc/net/coova/chilli (which should happen if the kernel module mode is on) or issue authorize, log out, etc., commands on the server with chilli_query. It's as if the commands don't have any effect on the clients. However, if I make HS_UAMLISTEN address to be on another network range like David mentioned, clients get that connection reset error. But /proc/net/coova/chilli is populated and if I manually authorize a client, he/she can browse the web. It's possible that there is a config problem or the NAT between UAMLISTEN and DHCPLISTEN has a issue. I am trying out all possible things I can think of but so far, I am not getting it right.

Thanks so much for your advice and help.

Regards,
Phyo Wai Soe

----- Original Message -----
From: "Russell Mike" <radius.sir at gmail.com>
To: "Phyo Wai Soe" <phyo.w.soe at frontiir.net>
Sent: Thursday, November 28, 2013 2:04:05 PM
Subject: Re: [Chilli] CoovaChilli Kernel Mode issue

Hi

i use CoovaChilli 1.3.0 in ISP HOSTING environment in multi tenancy mode
using VALNs. I have 27 instances running for chilli on single server. This
message is normal

* (Connection reset by peer) redir_read(0) failed!*

i do serve 230 hotspots across the city from my data center. i also see the
same (* (Connection reset by peer)*) in my logs as well, but cause nothing.
Moreover, i did not even received one trouble ticket in last one year from
any hotspot client, whereas above message is always there.

"Connection reset by peer" is often seen when a TCP communication partner
("peer") resets an initiated or established TCP connection. if a TCP packet
was received, but the peer has no matching socket associated As a result, a
locally invoked TCP receive

When user close browser, shutdown computer, take off network cable or walk
out side the network range with his iPhone, this would be logged. Can you
tell what is actual problem?

Thanks / Regards
RM --

On Thu, Nov 28, 2013 at 2:44 AM, Phyo Wai Soe <phyo.w.soe at frontiir.net>wrote:

> Hi Xabier,
>
> I am following these instructions from David on how to enable the kernel
> module. http://lists.coova.org/pipermail/chilli/2010-April/001239.html
>
> According to him, "Chilli is then also configured with 'uamlisten' of
> 11.0.0.1 and
> this is the IP address that gets assigned to tun0 (so note that
> dhcplisten and uamlisten are different!). The high level concept is that
> subscribers get a 10.1.0.0/24 IP address which is routed (when
> authenticated) through the kernel."
>
> So, I guess my setup is ok. When I installed CoovaChilli in normal mode
> and made UAMLISTEN part of HS_NETWORK, it was ok. This issue happens only
> if I enable the kernel module mode.
>
> Btw, when I looked at the syslogs, I saw the following lines when the
> clients got the resetting issue.
>
> redir.c: 2020: 104 (Connection reset by peer) redir_read(0) failed!
>
> Doing tcpdump on a client (10.99.0.30) when the issue occurred gave me the
> followings.
> ========================
> 16:54:09.921330 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP
> (6), length 40)
> 192.168.99.1.3990 > 10.99.0.30.57235: Flags [R], cksum 0xcb11 (correct),
> seq 2598775956, win 0, length 0
> 16:54:09.922202 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP
> (6), length 40)
> 10.99.0.30.57235 > 192.168.99.1.3990: Flags [R], cksum 0xb372 (correct),
> seq 524533718, win 0, length 0
> 16:54:09.922646 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP
> (6), length 40)
> 10.99.0.30.57235 > 192.168.99.1.3990: Flags [R], cksum 0xb372 (correct),
> seq 524533718, win 0, length 0
> ===============
> I think it probably indicates that the server (192.168.99.1:3990) is
> resetting the connections even before showing the redirection page. I
> tested by creating a test page and put it in /www. A client won't even see
> the contents of that test page.
> HS_UAMHOMEPAGE=http://\$HS_UAMLISTEN:\$HS_UAMPORT/www/testpage.html
>
> I searched the forum and web for solving redir_read issue but didn't get
> any clue.
>
> Thank you.
>
> Regards,
> Phyo
>
> Regards,
> Phyo Wai Soe
>
>
> ------------------------------
> *From: *"Xabier Oneca -- xOneca" <xoneca at gmail.com>
> *To: *"Phyo Wai Soe" <phyo.w.soe at frontiir.net>, chilli at coova.org
> *Sent: *Wednesday, November 27, 2013 1:21:50 AM
> *Subject: *Re: [Chilli] CoovaChilli Kernel Mode issue
>
>
> Hello Phyo,
>
> Are you sure you posted the configuration that you used?
>
> > HS_NETWORK=10.99.0.0       # HotSpot Network (must include HS_UAMLISTEN)
> > HS_NETMASK=255.255.255.0   # HotSpot Network Netmask
> > HS_UAMLISTEN=192.168.99.1  # HotSpot IP Address (on subscriber network
>
> As the comments say, 'HS_UAMLISTEN' must be in 'HS_NEWORK' and your
> isn't...
>
> Cheers,
>
> Xabier Oneca_,,_
>
>
> _______________________________________________
> Chilli mailing list
> Chilli at coova.org
> http://lists.coova.org/cgi-bin/mailman/listinfo/chilli
>
>