[Chilli] different landing page (Captive Portal Login Page) for each customer
Russell Mike
radius.sir at gmail.com
Wed Feb 6 10:49:45 UTC 2013
> Hi Sir, i wanted to come back and think you for the great assistance.
> Finally, i have Coova-Chilli running in multi tenant mode. i have tested up
> to five instances simultaneous up and serving service with different
> landing pages. is there any limit to it? i work with ISP, we may run 100
> coova daemons simultaneously. i would like to hear about it.
>
> root at captive:~# netstat -ntlp | grep chilli
> tcp 0 0 192.168.40.40:3300 0.0.0.0:*
> LISTEN 9256/chilli
> tcp 0 0 192.168.10.10:4100 0.0.0.0:*
> LISTEN 8719/chilli
> tcp 0 0 192.168.50.50:3400 0.0.0.0:*
> LISTEN 9404/chilli
> tcp 0 0 192.168.30.30:4200 0.0.0.0:*
> LISTEN 9081/chilli
> tcp 0 0 192.168.40.40:4300 0.0.0.0:*
> LISTEN 9256/chilli
> tcp 0 0 192.168.50.50:4400 0.0.0.0:*
> LISTEN 9404/chilli
> tcp 0 0 192.168.20.20:3990 0.0.0.0:*
> LISTEN 8897/chilli
> tcp 0 0 192.168.10.10:3100 0.0.0.0:*
> LISTEN 8719/chilli
> tcp 0 0 192.168.20.20:4990 0.0.0.0:*
> LISTEN 8897/chilli
> tcp 0 0 192.168.30.30:3200 0.0.0.0:*
> LISTEN 9081/chilli
>
>
>
> root at captive:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:0c:29:8a:1f:4f
> inet addr:41.211.31.77 Bcast:41.211.31.127 Mask:255.255.255.128
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:92472 errors:0 dropped:10 overruns:0 frame:0
> TX packets:2449 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:5882116 (5.8 MB) TX bytes:318397 (318.3 KB)
>
> eth1 Link encap:Ethernet HWaddr 00:0c:29:8a:1f:59
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:5922 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1479 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:497130 (497.1 KB) TX bytes:371163 (371.1 KB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:626 errors:0 dropped:0 overruns:0 frame:0
> TX packets:626 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:76411 (76.4 KB) TX bytes:76411 (76.4 KB)
>
> tun0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.10.10 P-t-P:192.168.10.10 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:164 errors:0 dropped:0 overruns:0 frame:0
> TX packets:167 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:20079 (20.0 KB) TX bytes:56865 (56.8 KB)
>
> tun1 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.20.20 P-t-P:192.168.20.20 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:227 errors:0 dropped:0 overruns:0 frame:0
> TX packets:233 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:24555 (24.5 KB) TX bytes:64511 (64.5 KB)
>
> tun2 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.30.30 P-t-P:192.168.30.30 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:98 errors:0 dropped:0 overruns:0 frame:0
> TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:12812 (12.8 KB) TX bytes:41056 (41.0 KB)
>
> tun3 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.40.40 P-t-P:192.168.40.40 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:112 errors:0 dropped:0 overruns:0 frame:0
> TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:14261 (14.2 KB) TX bytes:45107 (45.1 KB)
>
> tun4 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.50.50 P-t-P:192.168.50.50 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:290 errors:0 dropped:0 overruns:0 frame:0
> TX packets:298 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:33525 (33.5 KB) TX bytes:96547 (96.5 KB)
>
> vlan10 Link encap:Ethernet HWaddr 00:0c:29:8a:1f:59
> UP BROADCAST RUNNING MULTICAST MTU:1490 Metric:1
> RX packets:789 errors:0 dropped:0 overruns:0 frame:0
> TX packets:239 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:60359 (60.3 KB) TX bytes:66913 (66.9 KB)
>
> vlan20 Link encap:Ethernet HWaddr 00:0c:29:8a:1f:59
> UP BROADCAST RUNNING MULTICAST MTU:1490 Metric:1
> RX packets:838 errors:0 dropped:0 overruns:0 frame:0
> TX packets:274 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:63852 (63.8 KB) TX bytes:71206 (71.2 KB)
>
> vlan30 Link encap:Ethernet HWaddr 00:0c:29:8a:1f:59
> UP BROADCAST RUNNING MULTICAST MTU:1490 Metric:1
> RX packets:713 errors:0 dropped:0 overruns:0 frame:0
> TX packets:141 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:52814 (52.8 KB) TX bytes:45715 (45.7 KB)
>
> vlan40 Link encap:Ethernet HWaddr 00:0c:29:8a:1f:59
> UP BROADCAST RUNNING MULTICAST MTU:1490 Metric:1
> RX packets:740 errors:0 dropped:0 overruns:0 frame:0
> TX packets:151 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:55315 (55.3 KB) TX bytes:49746 (49.7 KB)
>
> vlan50 Link encap:Ethernet HWaddr 00:0c:29:8a:1f:59
> UP BROADCAST RUNNING MULTICAST MTU:1490 Metric:1
> RX packets:1269 errors:0 dropped:0 overruns:0 frame:0
> TX packets:556 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:95409 (95.4 KB) TX bytes:116239 (116.2 KB)
>
>
>
> Thanks / Thanks / Thanks
>
> RM --
>
> It 's limited by your hardware ram and cpu which can hold many process.
> you can check with htop.
>
> if you run squid proxy together on the same server, it mays use many cpu.
>
> Regards
> Chuan
>
>
>
Thanks dear all once again --
The only problem left that i cannot stop chilli (Coova_1.3.0 & UBUNTU 12.4
LTS x64). I can modify the start/stop script and use "kill -9" but really
do not want to do that. perhaps there is better way to handle this.
because i read that kill -9 doesn't give the process a chance to cleanly:
1) shut down socket connections
2) clean up temp files
3) inform its children that it is going away
4) reset its terminal characteristics
and so on and so on and so on.
*PROBLEM:*
root at captive:~# /etc/init.d/chilli stop
Found configuration /usr/local/etc/chilli/coova-vlan10/chilli.conf
Running DHCPIF=coova-vlan10 /etc/init.d/chilli stop
Shutting down chilli: No process in pidfile
'/usr/local/var/run/chilli.coova-vlan10.pid' found running; none killed.
Found configuration /usr/local/etc/chilli/coova-vlan20/chilli.conf
Running DHCPIF=coova-vlan20 /etc/init.d/chilli stop
Shutting down chilli: No process in pidfile
'/usr/local/var/run/chilli.coova-vlan20.pid' found running; none killed.
Found configuration /usr/local/etc/chilli/coova-vlan30/chilli.conf
Running DHCPIF=coova-vlan30 /etc/init.d/chilli stop
Shutting down chilli: No process in pidfile
'/usr/local/var/run/chilli.coova-vlan30.pid' found running; none killed.
Found configuration /usr/local/etc/chilli/coova-vlan40/chilli.conf
Running DHCPIF=coova-vlan40 /etc/init.d/chilli stop
Shutting down chilli: No process in pidfile
'/usr/local/var/run/chilli.coova-vlan40.pid' found running; none killed.
Found configuration /usr/local/etc/chilli/coova-vlan50/chilli.conf
Running DHCPIF=coova-vlan50 /etc/init.d/chilli stop
Shutting down chilli: No process in pidfile
'/usr/local/var/run/chilli.coova-vlan50.pid' found running; none killed.
Thanks / Regards
RM --R
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20130206/fdc5f67b/attachment-0001.html>
More information about the Chilli
mailing list