sweetspot-users — This is where the Sweet Support lives

[sweetspot-users] Sweetspot on Ubuntu 14.04 LTS

[Nayantha U. <gwn...@gm...>]

Hi,
Is it possible to install & configure Sweetspot on Ubuntu 14.04 LTS?

I'm trying below instructions.

 URL: http://sweetspot.sourceforge.net/

*Installation*

For a typical setup you might need a stand-alone machine sitting at the
border of your broadband network. Packets from broadband network destined
to whatever Internet host will pass through Sweetspot.

Sweetspot installation is as simple as doing ./configure && make && make
install. Then:

   1. In */usr/local/etc/sweetspot/sweetspot.conf* configure
   *inner-interface* and *outer-interface* settings to point to your
   broadband and Internet network interfaces respectively.
   2. Staying in */usr/local/etc/sweetspot/sweetspot.conf* configure
   *user-networks* to list the range of IPs being assigned to your
   broadband clients. Sweetspot would switch packets for these IPs and drop
   all others.
   3. If you intend to do source NAT for your broadband users, configure
   *snat-public-networks* to list IP address(es) that will act as public
   SNAT endpoints.
   4. In */usr/local/etc/sweetspot/filters/anonymous* configure *dnat* targets
   to make Sweetspot re-directing certain type of traffic (likely http/https)
   to your authentication server.

But there is no Directory in */usr/local/etc/ called "sweetspot"*

What can I do now?

Thank you.
Nayantha Udana
BSc IT(Hons.) Specialized in Computer Systems & Netwoking, CCNA

Re: [sweetspot-users] pass a filter as argument

[Ilya E. <il...@gl...>]

Hi Asoh,

Session filter could be  passed to sweeuam either UP or DN commands:

$ sweetuam 192.168.1.123 DN my-filter
$ sweetuam --help
Usage: sweetuam [ -hV ] [ -d <n> ] event ip [ arg [ arg [...] ] ]
Options:
     -h             this help message
     -V             software version information
     -d debug-what 
[io,snat,dnat,filter,uam,acct,session,relay,tuple,netset,frag,core,relations,gauge,lhstat,breath,all,]
     -c filename    configuration file (default 
/usr/local/etc/sweetspot/sweetuam.conf)
Events:
   UP ip [ filter-name [ interim-interval [ max-octets-in [ 
max-octets-out [ max-bps-in [ max-bps-out [ max-duration [ max-idle [ 
session-context [ event-context ] ] ] ] ] ] ] ] ] ] ] ]
   -> OK ip
   -> ER error-message
   DN ip [ filter-name [ session-context [ event-context ] ] ]
   -> OK ip
   -> ER error-message
   ST ip
   -> OK ip UP|DN session-id filter-name interim-interval session-context
   -> ER error-message
   LI ip
   -> OK ip max-octets-in max-octets-out max-bps-in max-bps-out 
max-duration max-idle
   -> ER error-message
   CN ip
   -> OK ip octets-in octets-out bps-in bps-out duration idle
   -> ER error-message
   PE ip
   -> OK ip bps-in bps-out
   -> ER error-message
   OU ip
   -> OK ip snat-ip low-snat-port high-snat-port
   -> ER error-message
   IN snat-ip snat-port
   -> OK snat-ip snat-port ip
   -> ER error-message
   Arguments:
     [snat-]ip             xxx.xxx.xxx.xxx
     session-id            0..UINT32
     filter-name           string, 0..64
     interim-interval      in seconds, 0..UINT32
     [max-]octets-in       0..UINT64
     [max-]octets-out      0..UINT64
     [max-]bps-in          0..UINT64
     [max-]bps-out         0..UINT64
     [max-]duration        in seconds, 0..UINT32
     [max-]idle            in seconds, 0..UINT32
     [low-|high-]snat-port 0..65535
     session-context       string
     event-context         string

-ilya

On 08/11/13 05:44, Asoh Frank wrote:
> Hi Everyone,
>
> I found in the help file that a filter(e.g anonymous) can be passed as 
> an argument in sweetuam. But my inexperience with linux command 
> doesn't help me understand
> how this is passed as an argument;for example something like "sweetuam 
> filtername" ?
>
> Please can someone explain how it works with some examples ?
>
> Thanks.
>

[sweetspot-users] pass a filter as argument

[Asoh F. <aso...@ya...>]

Hi Everyone,

I found in the help file that a filter(e.g anonymous) can be passed as an argument in sweetuam. But my inexperience with linux command doesn't help me understand 
how this is passed as an argument;for example something like "sweetuam filtername" ?

Please can someone explain how it works with some examples ?

Thanks.

Re: [sweetspot-users] Issues with setting up

[Asoh F. <aso...@ya...>]

Thanks Ilya for taking your time to reply; I shall proceed as you advice. So you say it's ok for the inner interface to be 192.158.5.1 netmask 255.255.255.255,
then the port of the router that connects to this interface should have e.g 192.168.5.2 netmask 255.255.255.0 ? or 255.255.255.255 ?
 
Asoh Frank-Senior
MSc. Computer Science
University of Antwerpen
Belgium


________________________________
 From: Ilya Etingof <il...@gl...>
To: swe...@li... 
Sent: Sunday, July 28, 2013 6:12 PM
Subject: Re: [sweetspot-users] Issues with setting up
 

Hi Frank,

Please find my comments along the lines:

On Jul 24, 2013, at 12:07 AM, <afr...@gm...> <afr...@gm...> wrote:

> Greetings,
>  
> I am a Linux computer that runs Sweetspot with two interfaces [eth0 ] and [eth1]
> Eth0 is  the uplink connected to the public network with IP: 192.168.0.200
> Eth1 is the distribution point(inside interface) with IP : 192.168.5.1
>  
>  
> This Linux computer is connect from the Eth1(network 192.168.5.0) to a Linksys router(OpenWrt WAN port) with a static IP address of 192.168.5.7.
>  
> This Linksys router has 4 ports which are two networks of 192.168.1.0  and  192.168.2.0
>  
>  
> I have static routing on the Linux computer running Sweetspot which is:
> 
> up route add -net 192.168.2.0/24 gw 192.168.5.7 dev eth1
> up route add -net 192.168.1.0/24 gw 192.168.5.7 dev eth1
>  
> The route works and I can access any IP from anywhere on the network.
>  
>  
> Now according to Sweetspot, if I am to change the netmask of Eth1 to 255.255.255.255 , then this network wouldn't work under normal circumstances. How am I suppose to do that ?
>  

In your setup it looks like this is not needed. The idea of a host netmask on inner interface is to disallow clients talking to each other through kernel (e.g. using regular routing). Since you have clients in a local segment behind router they would talk to each other anyway. But maybe that's not an issue.

> And secondly, how am I suppose to set up the IPTABLES ? does Sweetspot do this automatically ?
> because after running the “sweetspot”, I found no changes to the IPTABLES. Here is my configuration file please:

Sweetspot does not use iptables.

> /////////////////////////////////////////////////////////////////////////////////////////////////
> # Sweetspot daemon configuration
>  
> # inner interface name (which is close to users)
> inner-interface eth1
>  
> # outer interface name (which is close to Internet)
> outer-interface eth0
>  
> # user IP CIDR (addresses anyhow assigned to user computers)
> #user-networks 127.0.0.0
> user-networks 192.168.5.0/24 192.168.1.0/24 192.168.2.0/24
>  
> # SNAT public networks
> snat-public-networks 192.168.0.200/24
>  
> # authentication server address
> uam-server-address 127.0.0.1
>  
> # authentication server port
> #uam-server-port 3993
>  
> # authentication server shared secret (auth client must have the same)
> uam-secret 1234567890
>  
> # report UAM errors back to client (obsolete)
> #uam-report-errors 1
>  
> # Detail file accounting
> acct-detail-file /var/sweetspot/detail
>  
> # Interim accounting interval (in secs)
> acct-interim-interval 300
>  
> # NAS-IP-Address to report in acct detail file
> acct-nas-ip-address 127.0.0.1
>  
> # Packet filters directory
> filter-dir /usr/local/etc/sweetspot/filters
>  
> # Captive filter
> #filter-anonymous anonymous
> //////////////////////////////////////////////////////////////////////////////////////////////////////
>  
>  
>  
> I pretty much don’t get anything in the logs. If I change the netmask to 255.255.255.255, there is no pinging anywhere !, If I leave it to 255.255.255.0 there is pinging but no captive control.

Your setup looks good.

There should be no Internet available through your Linux computer if you disable IP forwarding:

echo 0 > /proc/sys/net/ipv4/ip_forward 

Then the only way for packets to travel between eth1 and eth0 if through the sweetspot daemon. 

> 
> I have a script that if I run under normal circumstances to share internet with the networks that works flawlessly. Another doubt it, should this script be run ? or does Sweetspot does something similar ?

Sweetspot does source and destination NAT all by itself. You don't need iptable here.

-ilya


------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
sweetspot-users mailing list
swe...@li...
https://lists.sourceforge.net/lists/listinfo/sweetspot-users

Re: [sweetspot-users] Unsupported protocol IGMP error

[Ilya E. <il...@gl...>]

The best documentation available is on the web site (sweetspot.sf.net).

IGMP support is not implemented to sweetspot's NAT, thus the error in subject.

-ilya

On Jul 23, 2013, at 4:11 AM, Asoh Frank wrote:

> Greetings,
> 
> Are they any people out there who have used and have a full documentation on setting this tool up ?
> 
> Thanks

Re: [sweetspot-users] Issues with setting up

[Ilya E. <il...@gl...>]

Hi Frank,

Please find my comments along the lines:

On Jul 24, 2013, at 12:07 AM, <afr...@gm...> <afr...@gm...> wrote:

> Greetings,
>  
> I am a Linux computer that runs Sweetspot with two interfaces [eth0 ] and [eth1]
> Eth0 is  the uplink connected to the public network with IP: 192.168.0.200
> Eth1 is the distribution point(inside interface) with IP : 192.168.5.1
>  
>  
> This Linux computer is connect from the Eth1(network 192.168.5.0) to a Linksys router(OpenWrt WAN port) with a static IP address of 192.168.5.7.
>  
> This Linksys router has 4 ports which are two networks of 192.168.1.0  and  192.168.2.0
>  
>  
> I have static routing on the Linux computer running Sweetspot which is:
> 
> up route add -net 192.168.2.0/24 gw 192.168.5.7 dev eth1
> up route add -net 192.168.1.0/24 gw 192.168.5.7 dev eth1
>  
> The route works and I can access any IP from anywhere on the network.
>  
>  
> Now according to Sweetspot, if I am to change the netmask of Eth1 to 255.255.255.255 , then this network wouldn't work under normal circumstances. How am I suppose to do that ?
>  

In your setup it looks like this is not needed. The idea of a host netmask on inner interface is to disallow clients talking to each other through kernel (e.g. using regular routing). Since you have clients in a local segment behind router they would talk to each other anyway. But maybe that's not an issue.

> And secondly, how am I suppose to set up the IPTABLES ? does Sweetspot do this automatically ?
> because after running the “sweetspot”, I found no changes to the IPTABLES. Here is my configuration file please:

Sweetspot does not use iptables.

> /////////////////////////////////////////////////////////////////////////////////////////////////
> # Sweetspot daemon configuration
>  
> # inner interface name (which is close to users)
> inner-interface eth1
>  
> # outer interface name (which is close to Internet)
> outer-interface eth0
>  
> # user IP CIDR (addresses anyhow assigned to user computers)
> #user-networks 127.0.0.0
> user-networks 192.168.5.0/24 192.168.1.0/24 192.168.2.0/24
>  
> # SNAT public networks
> snat-public-networks 192.168.0.200/24
>  
> # authentication server address
> uam-server-address 127.0.0.1
>  
> # authentication server port
> #uam-server-port 3993
>  
> # authentication server shared secret (auth client must have the same)
> uam-secret 1234567890
>  
> # report UAM errors back to client (obsolete)
> #uam-report-errors 1
>  
> # Detail file accounting
> acct-detail-file /var/sweetspot/detail
>  
> # Interim accounting interval (in secs)
> acct-interim-interval 300
>  
> # NAS-IP-Address to report in acct detail file
> acct-nas-ip-address 127.0.0.1
>  
> # Packet filters directory
> filter-dir /usr/local/etc/sweetspot/filters
>  
> # Captive filter
> #filter-anonymous anonymous
> //////////////////////////////////////////////////////////////////////////////////////////////////////
>  
>  
>  
> I pretty much don’t get anything in the logs. If I change the netmask to 255.255.255.255, there is no pinging anywhere !, If I leave it to 255.255.255.0 there is pinging but no captive control.

Your setup looks good.

There should be no Internet available through your Linux computer if you disable IP forwarding:

echo 0 > /proc/sys/net/ipv4/ip_forward 

Then the only way for packets to travel between eth1 and eth0 if through the sweetspot daemon. 

> 
> I have a script that if I run under normal circumstances to share internet with the networks that works flawlessly. Another doubt it, should this script be run ? or does Sweetspot does something similar ?

Sweetspot does source and destination NAT all by itself. You don't need iptable here.

-ilya

[sweetspot-users] Issues and doubts with Setting Up;

[Asoh F. <aso...@ya...>]

Greetings,
 
I am a Linux computer that runs Sweetspot with two interfaces [eth0 ] and [eth1]
Eth0 is  the uplink connected to the public network with IP: 192.168.0.200
Eth1 is the distribution point(inside interface) with IP : 192.168.5.1
 
 
This Linux computer is connect from the Eth1(network 192.168.5.0) to a Linksys router(OpenWrt WAN port) with a static IP address of 192.168.5.7.
 
This Linksys router has 4 ports which are two networks of 192.168.1.0  and  192.168.2.0
 
 
I have static routing on the Linux computer running Sweetspot which is:

up route add -net 192.168.2.0/24 gw 192.168.5.7 dev eth1
up route add -net 192.168.1.0/24 gw 192.168.5.7 dev eth1
 
The route works and I can access any IP from anywhere on the network.
 
 
Now according to Sweetspot, if I am to change the netmask of Eth1 to 255.255.255.255 , then this network wouldn't work under normal circumstances. How am I suppose to do that ?
 
 
And secondly, how am I suppose to set up the IPTABLES ? does Sweetspot do this automatically ?
because after running the “sweetspot”, I found no changes to the IPTABLES. Here is my configuration file please:

/////////////////////////////////////////////////////////////////////////////////////////////////
# Sweetspot daemon configuration
 
# inner interface name (which is close to users)
inner-interface eth1
 
# outer interface name (which is close to Internet)
outer-interface eth0
 
# user IP CIDR (addresses anyhow assigned to user computers)
#user-networks 127.0.0.0
user-networks 192.168.5.0/24 192.168.1.0/24 192.168.2.0/24
 
# SNAT public networks
snat-public-networks 192.168.0.200/24
 
# authentication server address
uam-server-address 127.0.0.1
 
# authentication server port
#uam-server-port 3993
 
# authentication server shared secret (auth client must have the same)
uam-secret 1234567890
 
# report UAM errors back to client (obsolete)
#uam-report-errors 1
 
# Detail file accounting
acct-detail-file /var/sweetspot/detail
 
# Interim accounting interval (in secs)
acct-interim-interval 300
 
# NAS-IP-Address to report in acct detail file
acct-nas-ip-address 127.0.0.1
 
# Packet filters directory
filter-dir /usr/local/etc/sweetspot/filters
 
# Captive filter
#filter-anonymous anonymous
//////////////////////////////////////////////////////////////////////////////////////////////////////
 
 
 
I pretty much don’t get anything in the logs. If I change the netmask to 255.255.255.255, there is no pinging anywhere !, If I leave it to 255.255.255.0 there is pinging but no captive control.

I have a script that if I run under normal circumstances to share internet with the networks that works flawlessly. Another doubt it, should this script be run ? or does Sweetspot does something similar ?

/////////////////////////////////////////////////////////////////////////////////
 
#!/bin/sh
echo -e "\n\nSETTING UP IPTABLES PROXY..."
 
INTIF="eth1"
 
#   Enter the external interface's designation for the
#   EXTIF variable:
 
EXTIF="eth0"

 #   IP address for the EXTIP variable:

EXTIP="192.168.0.200"
 

echo "Loading required stateful/NAT kernel modules..."
 
/sbin/depmod -a
/sbin/modprobe ip_tables
/sbin/modprobe ip_conntrack
/sbin/modprobe ip_conntrack_ftp
/sbin/modprobe ip_conntrack_irc
/sbin/modprobe iptable_nat
/sbin/modprobe ip_nat_ftp
/sbin/modprobe ip_nat_irc
 
echo "    Enabling IP forwarding..."
echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_dynaddr
echo "    External interface: $EXTIF"
echo "       External interface IP address is: $EXTIP"
echo "    Loading proxy server rules..."
 
iptables -P INPUT ACCEPT
iptables -F INPUT
iptables -P OUTPUT ACCEPT
iptables -F OUTPUT
iptables -P FORWARD DROP
iptables -F FORWARD
iptables -t nat -F
 
# FWD: Allow all connections OUT and only existing and related ones IN
iptables -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED -j$
iptables -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
 
# Enabling SNAT (MASQUERADE) functionality on $EXTIF
iptables -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
 
echo -e "       Proxy server rule loading complete\n\n"
 
/////////////////////////////////////////////////////////////////////////////////////////////

[sweetspot-users] Issues with setting up

[<afr...@gm...>]

Greetings,


I am a Linux computer that runs Sweetspot with two interfaces [eth0 ] and [eth1]

Eth0 is  the uplink connected to the public network with IP: 192.168.0.200

Eth1 is the distribution point(inside interface) with IP : 192.168.5.1



This Linux computer is connect from the Eth1(network 192.168.5.0) to a Linksys router(OpenWrt WAN port) with a static IP address of 192.168.5.7.


This Linksys router has 4 ports which are two networks of 192.168.1.0  and  192.168.2.0



I have static routing on the Linux computer running Sweetspot which is:


up route add -net 192.168.2.0/24 gw 192.168.5.7 dev eth1
up route add -net 192.168.1.0/24 gw 192.168.5.7 dev eth1


The route works and I can access any IP from anywhere on the network.



Now according to Sweetspot, if I am to change the netmask of Eth1 to 255.255.255.255 , then this network wouldn't work under normal circumstances. How am I suppose to do that ?



And secondly, how am I suppose to set up the IPTABLES ? does Sweetspot do this automatically ?

because after running the “sweetspot”, I found no changes to the IPTABLES. Here is my configuration file please:


/////////////////////////////////////////////////////////////////////////////////////////////////

# Sweetspot daemon configuration


# inner interface name (which is close to users)
inner-interface eth1


# outer interface name (which is close to Internet)
outer-interface eth0


# user IP CIDR (addresses anyhow assigned to user computers)
#user-networks 127.0.0.0
user-networks 192.168.5.0/24 192.168.1.0/24 192.168.2.0/24


# SNAT public networks
snat-public-networks 192.168.0.200/24


# authentication server address
uam-server-address 127.0.0.1


# authentication server port
#uam-server-port 3993


# authentication server shared secret (auth client must have the same)
uam-secret 1234567890


# report UAM errors back to client (obsolete)
#uam-report-errors 1


# Detail file accounting
acct-detail-file /var/sweetspot/detail


# Interim accounting interval (in secs)
acct-interim-interval 300


# NAS-IP-Address to report in acct detail file
acct-nas-ip-address 127.0.0.1


# Packet filters directory
filter-dir /usr/local/etc/sweetspot/filters


# Captive filter
#filter-anonymous anonymous
//////////////////////////////////////////////////////////////////////////////////////////////////////




I pretty much don’t get anything in the logs. If I change the netmask to 255.255.255.255, there is no pinging anywhere !, If I leave it to 255.255.255.0 there is pinging but no captive control.

I have a script that if I run under normal circumstances to share internet with the networks that works flawlessly. Another doubt it, should this script be run ? or does Sweetspot does something similar ?


/////////////////////////////////////////////////////////////////////////////////


#!/bin/sh

echo -e "\n\nSETTING UP IPTABLES PROXY..."


INTIF="eth1"


#   Enter the external interface's designation for the
#   EXTIF variable:


EXTIF="eth0"


 #   IP address for the EXTIP variable:


EXTIP="192.168.0.200"



echo "Loading required stateful/NAT kernel modules..."


/sbin/depmod -a
/sbin/modprobe ip_tables
/sbin/modprobe ip_conntrack
/sbin/modprobe ip_conntrack_ftp
/sbin/modprobe ip_conntrack_irc
/sbin/modprobe iptable_nat
/sbin/modprobe ip_nat_ftp
/sbin/modprobe ip_nat_irc


echo "    Enabling IP forwarding..."
echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_dynaddr

echo "    External interface: $EXTIF"
echo "       External interface IP address is: $EXTIP"

echo "    Loading proxy server rules..."


iptables -P INPUT ACCEPT
iptables -F INPUT
iptables -P OUTPUT ACCEPT
iptables -F OUTPUT
iptables -P FORWARD DROP
iptables -F FORWARD
iptables -t nat -F


# FWD: Allow all connections OUT and only existing and related ones IN
iptables -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED -j$
iptables -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT


# Enabling SNAT (MASQUERADE) functionality on $EXTIF
iptables -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE


echo -e "       Proxy server rule loading complete\n\n"


/////////////////////////////////////////////////////////////////////////////////////////////

[sweetspot-users] Unsupported protocol IGMP error

[Asoh F. <aso...@ya...>]

Greetings,

Are they any people out there who have used and have a full documentation on setting this tool up ?

Thanks

Re: [sweetspot-users] Problem on configuration for FreeRADIUS combine with Sweetspot

[<il...@gl...>]

There is no currently out-of-the box sweetspot integration with 
FreeRADIUS. That piece of code could be written fairly easy once
you grasp the concept behind sweetspot control.

In my environment RADIUS server talks to sweetspot daemon through sweetuam 
utility. That's mostly used in WPA setup where RADIUS server 
enables/disables Internet access by RADIUS accounting start/stop messages.

In case of an open network, it's web-based captive-portal which talks to 
sweetspot allowing or disallowing internet access for particular user 
(identified by its IP).

-ilya

> I have seen Sweetspot manual from here http://sweetspot.sourceforge.net/ 
> but when I click the link RADIUS configuration in this page it will go 
> straight to wikipedia http://en.wikipedia.org/wiki/RADIUS. I would like 
> to know if there is any way for me to combine Sweetspot and FreeRADIUS 
> which is work on the same machine?  I didn't find any manual about 
> RADIUS Server part. Currently, I'm using Ubuntu 10.10 (maverick).

[sweetspot-users] Problem on configuration for FreeRADIUS combine with Sweetspot

[Siti N. M. H. <hai...@mi...>]

Hi Developer,

I have seen Sweetspot manual from here http://sweetspot.sourceforge.net/ but when I click the link RADIUS configuration in this page it will go straight to wikipedia http://en.wikipedia.org/wiki/RADIUS. I would like to know if there is any way for me to combine Sweetspot and FreeRADIUS which is work on the same machine?  I didn't find any manual about RADIUS Server part. Currently, I'm using Ubuntu 10.10 (maverick).

I hope you can help me to fix this problem as soon as possible. Your co-operation is highly appreciated.

Thank you.

Regards,
Haizum
-----------------------------------------------
 A strategic agency under MOSTI
 www.mimos.my
-----------------------------------------------

------------------------------------------------------------------
-
-
DISCLAIMER: 

This e-mail (including any attachments) is for the addressee(s) 
only and may contain confidential information. If you are not the 
intended recipient, please note that any dealing, review, 
distribution, printing, copying or use of this e-mail is strictly 
prohibited. If you have received this email in error, please notify 
the sender  immediately and delete the original message. 
MIMOS Berhad is a research and development institution under 
the purview of the Malaysian Ministry of Science, Technology and 
Innovation. Opinions, conclusions and other information in this e-
mail that do not relate to the official business of MIMOS Berhad 
and/or its subsidiaries shall be understood as neither given nor 
endorsed by MIMOS Berhad and/or its subsidiaries and neither 
MIMOS Berhad nor its subsidiaries accepts responsibility for the 
same. All liability arising from or in connection with computer 
viruses and/or corrupted e-mails is excluded to the fullest extent 
permitted by law.

[sweetspot-users] Error in make

[Raihan -Ul - I. <rai...@gm...>]

HI
I got the following error when i run the make can any one tell me wht is
the problem

Thanks
Raihan


dreamplug-debian:/home/Rai/sweetspot-0.0.20# make
make  all-recursive
make[1]: Entering directory `/home/Rai/sweetspot-0.0.20'
Making all in src
make[2]: Entering directory `/home/Rai/sweetspot-0.0.20/src'
make  all-am
make[3]: Entering directory `/home/Rai/sweetspot-0.0.20/src'
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
uamclt.o -MD -MP -MF ".deps/uamclt.Tpo" -c -o uamclt.o uamclt.c; \
        then mv -f ".deps/uamclt.Tpo" ".deps/uamclt.Po"; else rm -f
".deps/uamclt.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
uammsg.o -MD -MP -MF ".deps/uammsg.Tpo" -c -o uammsg.o uammsg.c; \
        then mv -f ".deps/uammsg.Tpo" ".deps/uammsg.Po"; else rm -f
".deps/uammsg.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT md5.o
-MD -MP -MF ".deps/md5.Tpo" -c -o md5.o md5.c; \
        then mv -f ".deps/md5.Tpo" ".deps/md5.Po"; else rm -f
".deps/md5.Tpo"; exit 1; fi
rm -f libsweetuam.a
ar cru libsweetuam.a uamclt.o uammsg.o md5.o
ranlib libsweetuam.a
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT cfg.o
-MD -MP -MF ".deps/cfg.Tpo" -c -o cfg.o cfg.c; \
        then mv -f ".deps/cfg.Tpo" ".deps/cfg.Po"; else rm -f
".deps/cfg.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
pretty.o -MD -MP -MF ".deps/pretty.Tpo" -c -o pretty.o pretty.c; \
        then mv -f ".deps/pretty.Tpo" ".deps/pretty.Po"; else rm -f
".deps/pretty.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
debug.o -MD -MP -MF ".deps/debug.Tpo" -c -o debug.o debug.c; \
        then mv -f ".deps/debug.Tpo" ".deps/debug.Po"; else rm -f
".deps/debug.Tpo"; exit 1; fi
rm -f libsweetmisc.a
ar cru libsweetmisc.a cfg.o pretty.o debug.o
ranlib libsweetmisc.a
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT if.o
-MD -MP -MF ".deps/if.Tpo" -c -o if.o if.c; \
        then mv -f ".deps/if.Tpo" ".deps/if.Po"; else rm -f ".deps/if.Tpo";
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
session.o -MD -MP -MF ".deps/session.Tpo" -c -o session.o session.c; \
        then mv -f ".deps/session.Tpo" ".deps/session.Po"; else rm -f
".deps/session.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
gauge.o -MD -MP -MF ".deps/gauge.Tpo" -c -o gauge.o gauge.c; \
        then mv -f ".deps/gauge.Tpo" ".deps/gauge.Po"; else rm -f
".deps/gauge.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_src.o -MD -MP -MF ".deps/nat_src.Tpo" -c -o nat_src.o nat_src.c; \
        then mv -f ".deps/nat_src.Tpo" ".deps/nat_src.Po"; else rm -f
".deps/nat_src.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_dst.o -MD -MP -MF ".deps/nat_dst.Tpo" -c -o nat_dst.o nat_dst.c; \
        then mv -f ".deps/nat_dst.Tpo" ".deps/nat_dst.Po"; else rm -f
".deps/nat_dst.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
relay_inward.o -MD -MP -MF ".deps/relay_inward.Tpo" -c -o relay_inward.o
relay_inward.c; \
        then mv -f ".deps/relay_inward.Tpo" ".deps/relay_inward.Po"; else
rm -f ".deps/relay_inward.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
relay_outward.o -MD -MP -MF ".deps/relay_outward.Tpo" -c -o relay_outward.o
relay_outward.c; \
        then mv -f ".deps/relay_outward.Tpo" ".deps/relay_outward.Po"; else
rm -f ".deps/relay_outward.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
filter.o -MD -MP -MF ".deps/filter.Tpo" -c -o filter.o filter.c; \
        then mv -f ".deps/filter.Tpo" ".deps/filter.Po"; else rm -f
".deps/filter.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct.o -MD -MP -MF ".deps/acct.Tpo" -c -o acct.o acct.c; \
        then mv -f ".deps/acct.Tpo" ".deps/acct.Po"; else rm -f
".deps/acct.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_method.o -MD -MP -MF ".deps/acct_method.Tpo" -c -o acct_method.o
acct_method.c; \
        then mv -f ".deps/acct_method.Tpo" ".deps/acct_method.Po"; else rm
-f ".deps/acct_method.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_method_detail.o -MD -MP -MF ".deps/acct_method_detail.Tpo" -c -o
acct_method_detail.o acct_method_detail.c; \
        then mv -f ".deps/acct_method_detail.Tpo"
".deps/acct_method_detail.Po"; else rm -f ".deps/acct_method_detail.Tpo";
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_method_detail_snat.o -MD -MP -MF ".deps/acct_method_detail_snat.Tpo"
-c -o acct_method_detail_snat.o acct_method_detail_snat.c; \
        then mv -f ".deps/acct_method_detail_snat.Tpo"
".deps/acct_method_detail_snat.Po"; else rm -f
".deps/acct_method_detail_snat.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_method_detail_session.o -MD -MP -MF
".deps/acct_method_detail_session.Tpo" -c -o acct_method_detail_session.o
acct_method_detail_session.c; \
        then mv -f ".deps/acct_method_detail_session.Tpo"
".deps/acct_method_detail_session.Po"; else rm -f
".deps/acct_method_detail_session.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_method_detail_gauge.o -MD -MP -MF ".deps/acct_method_detail_gauge.Tpo"
-c -o acct_method_detail_gauge.o acct_method_detail_gauge.c; \
        then mv -f ".deps/acct_method_detail_gauge.Tpo"
".deps/acct_method_detail_gauge.Po"; else rm -f
".deps/acct_method_detail_gauge.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_method_detail_event.o -MD -MP -MF ".deps/acct_method_detail_event.Tpo"
-c -o acct_method_detail_event.o acct_method_detail_event.c; \
        then mv -f ".deps/acct_method_detail_event.Tpo"
".deps/acct_method_detail_event.Po"; else rm -f
".deps/acct_method_detail_event.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_scope.o -MD -MP -MF ".deps/acct_scope.Tpo" -c -o acct_scope.o
acct_scope.c; \
        then mv -f ".deps/acct_scope.Tpo" ".deps/acct_scope.Po"; else rm -f
".deps/acct_scope.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_scope_event.o -MD -MP -MF ".deps/acct_scope_event.Tpo" -c -o
acct_scope_event.o acct_scope_event.c; \
        then mv -f ".deps/acct_scope_event.Tpo"
".deps/acct_scope_event.Po"; else rm -f ".deps/acct_scope_event.Tpo"; exit
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_scope_session.o -MD -MP -MF ".deps/acct_scope_session.Tpo" -c -o
acct_scope_session.o acct_scope_session.c; \
        then mv -f ".deps/acct_scope_session.Tpo"
".deps/acct_scope_session.Po"; else rm -f ".deps/acct_scope_session.Tpo";
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_scope_gauge.o -MD -MP -MF ".deps/acct_scope_gauge.Tpo" -c -o
acct_scope_gauge.o acct_scope_gauge.c; \
        then mv -f ".deps/acct_scope_gauge.Tpo"
".deps/acct_scope_gauge.Po"; else rm -f ".deps/acct_scope_gauge.Tpo"; exit
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
acct_scope_snat.o -MD -MP -MF ".deps/acct_scope_snat.Tpo" -c -o
acct_scope_snat.o acct_scope_snat.c; \
        then mv -f ".deps/acct_scope_snat.Tpo" ".deps/acct_scope_snat.Po";
else rm -f ".deps/acct_scope_snat.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
flog.o -MD -MP -MF ".deps/flog.Tpo" -c -o flog.o flog.c; \
        then mv -f ".deps/flog.Tpo" ".deps/flog.Po"; else rm -f
".deps/flog.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
lhash.o -MD -MP -MF ".deps/lhash.Tpo" -c -o lhash.o lhash.c; \
        then mv -f ".deps/lhash.Tpo" ".deps/lhash.Po"; else rm -f
".deps/lhash.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
filter_scanner.o -MD -MP -MF ".deps/filter_scanner.Tpo" -c -o
filter_scanner.o filter_scanner.c; \
        then mv -f ".deps/filter_scanner.Tpo" ".deps/filter_scanner.Po";
else rm -f ".deps/filter_scanner.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
filter_parser.o -MD -MP -MF ".deps/filter_parser.Tpo" -c -o filter_parser.o
filter_parser.c; \
        then mv -f ".deps/filter_parser.Tpo" ".deps/filter_parser.Po"; else
rm -f ".deps/filter_parser.Tpo"; exit 1; fi
filter_parser.y: In function âsw_filter_parse_rulesetâ:
filter_parser.y:323: warning: assignment makes pointer from integer without
a cast
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
tuple.o -MD -MP -MF ".deps/tuple.Tpo" -c -o tuple.o tuple.c; \
        then mv -f ".deps/tuple.Tpo" ".deps/tuple.Po"; else rm -f
".deps/tuple.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
tuple_ip.o -MD -MP -MF ".deps/tuple_ip.Tpo" -c -o tuple_ip.o tuple_ip.c; \
        then mv -f ".deps/tuple_ip.Tpo" ".deps/tuple_ip.Po"; else rm -f
".deps/tuple_ip.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
tuple_tcp.o -MD -MP -MF ".deps/tuple_tcp.Tpo" -c -o tuple_tcp.o
tuple_tcp.c; \
        then mv -f ".deps/tuple_tcp.Tpo" ".deps/tuple_tcp.Po"; else rm -f
".deps/tuple_tcp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
tuple_udp.o -MD -MP -MF ".deps/tuple_udp.Tpo" -c -o tuple_udp.o
tuple_udp.c; \
        then mv -f ".deps/tuple_udp.Tpo" ".deps/tuple_udp.Po"; else rm -f
".deps/tuple_udp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
tuple_icmp.o -MD -MP -MF ".deps/tuple_icmp.Tpo" -c -o tuple_icmp.o
tuple_icmp.c; \
        then mv -f ".deps/tuple_icmp.Tpo" ".deps/tuple_icmp.Po"; else rm -f
".deps/tuple_icmp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
tuple_checksum.o -MD -MP -MF ".deps/tuple_checksum.Tpo" -c -o
tuple_checksum.o tuple_checksum.c; \
        then mv -f ".deps/tuple_checksum.Tpo" ".deps/tuple_checksum.Po";
else rm -f ".deps/tuple_checksum.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
relay_validate.o -MD -MP -MF ".deps/relay_validate.Tpo" -c -o
relay_validate.o relay_validate.c; \
        then mv -f ".deps/relay_validate.Tpo" ".deps/relay_validate.Po";
else rm -f ".deps/relay_validate.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
relay_validate_ip.o -MD -MP -MF ".deps/relay_validate_ip.Tpo" -c -o
relay_validate_ip.o relay_validate_ip.c; \
        then mv -f ".deps/relay_validate_ip.Tpo"
".deps/relay_validate_ip.Po"; else rm -f ".deps/relay_validate_ip.Tpo";
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
gauge_index.o -MD -MP -MF ".deps/gauge_index.Tpo" -c -o gauge_index.o
gauge_index.c; \
        then mv -f ".deps/gauge_index.Tpo" ".deps/gauge_index.Po"; else rm
-f ".deps/gauge_index.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
gauge_index_ip.o -MD -MP -MF ".deps/gauge_index_ip.Tpo" -c -o
gauge_index_ip.o gauge_index_ip.c; \
        then mv -f ".deps/gauge_index_ip.Tpo" ".deps/gauge_index_ip.Po";
else rm -f ".deps/gauge_index_ip.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_src_endpoint.o -MD -MP -MF ".deps/nat_src_endpoint.Tpo" -c -o
nat_src_endpoint.o nat_src_endpoint.c; \
        then mv -f ".deps/nat_src_endpoint.Tpo"
".deps/nat_src_endpoint.Po"; else rm -f ".deps/nat_src_endpoint.Tpo"; exit
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_src_endpoint_ip.o -MD -MP -MF ".deps/nat_src_endpoint_ip.Tpo" -c -o
nat_src_endpoint_ip.o nat_src_endpoint_ip.c; \
        then mv -f ".deps/nat_src_endpoint_ip.Tpo"
".deps/nat_src_endpoint_ip.Po"; else rm -f ".deps/nat_src_endpoint_ip.Tpo";
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_src_endpoint_tcp.o -MD -MP -MF ".deps/nat_src_endpoint_tcp.Tpo" -c -o
nat_src_endpoint_tcp.o nat_src_endpoint_tcp.c; \
        then mv -f ".deps/nat_src_endpoint_tcp.Tpo"
".deps/nat_src_endpoint_tcp.Po"; else rm -f
".deps/nat_src_endpoint_tcp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_src_endpoint_udp.o -MD -MP -MF ".deps/nat_src_endpoint_udp.Tpo" -c -o
nat_src_endpoint_udp.o nat_src_endpoint_udp.c; \
        then mv -f ".deps/nat_src_endpoint_udp.Tpo"
".deps/nat_src_endpoint_udp.Po"; else rm -f
".deps/nat_src_endpoint_udp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_src_endpoint_icmp.o -MD -MP -MF ".deps/nat_src_endpoint_icmp.Tpo" -c -o
nat_src_endpoint_icmp.o nat_src_endpoint_icmp.c; \
        then mv -f ".deps/nat_src_endpoint_icmp.Tpo"
".deps/nat_src_endpoint_icmp.Po"; else rm -f
".deps/nat_src_endpoint_icmp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_dst_endpoint.o -MD -MP -MF ".deps/nat_dst_endpoint.Tpo" -c -o
nat_dst_endpoint.o nat_dst_endpoint.c; \
        then mv -f ".deps/nat_dst_endpoint.Tpo"
".deps/nat_dst_endpoint.Po"; else rm -f ".deps/nat_dst_endpoint.Tpo"; exit
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_dst_endpoint_ip.o -MD -MP -MF ".deps/nat_dst_endpoint_ip.Tpo" -c -o
nat_dst_endpoint_ip.o nat_dst_endpoint_ip.c; \
        then mv -f ".deps/nat_dst_endpoint_ip.Tpo"
".deps/nat_dst_endpoint_ip.Po"; else rm -f ".deps/nat_dst_endpoint_ip.Tpo";
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_dst_endpoint_tcp.o -MD -MP -MF ".deps/nat_dst_endpoint_tcp.Tpo" -c -o
nat_dst_endpoint_tcp.o nat_dst_endpoint_tcp.c; \
        then mv -f ".deps/nat_dst_endpoint_tcp.Tpo"
".deps/nat_dst_endpoint_tcp.Po"; else rm -f
".deps/nat_dst_endpoint_tcp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_dst_endpoint_udp.o -MD -MP -MF ".deps/nat_dst_endpoint_udp.Tpo" -c -o
nat_dst_endpoint_udp.o nat_dst_endpoint_udp.c; \
        then mv -f ".deps/nat_dst_endpoint_udp.Tpo"
".deps/nat_dst_endpoint_udp.Po"; else rm -f
".deps/nat_dst_endpoint_udp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_tuple.o -MD -MP -MF ".deps/nat_tuple.Tpo" -c -o nat_tuple.o
nat_tuple.c; \
        then mv -f ".deps/nat_tuple.Tpo" ".deps/nat_tuple.Po"; else rm -f
".deps/nat_tuple.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_tuple_ip.o -MD -MP -MF ".deps/nat_tuple_ip.Tpo" -c -o nat_tuple_ip.o
nat_tuple_ip.c; \
        then mv -f ".deps/nat_tuple_ip.Tpo" ".deps/nat_tuple_ip.Po"; else
rm -f ".deps/nat_tuple_ip.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_tuple_icmp.o -MD -MP -MF ".deps/nat_tuple_icmp.Tpo" -c -o
nat_tuple_icmp.o nat_tuple_icmp.c; \
        then mv -f ".deps/nat_tuple_icmp.Tpo" ".deps/nat_tuple_icmp.Po";
else rm -f ".deps/nat_tuple_icmp.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
frag.o -MD -MP -MF ".deps/frag.Tpo" -c -o frag.o frag.c; \
        then mv -f ".deps/frag.Tpo" ".deps/frag.Po"; else rm -f
".deps/frag.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
frag_tuple.o -MD -MP -MF ".deps/frag_tuple.Tpo" -c -o frag_tuple.o
frag_tuple.c; \
        then mv -f ".deps/frag_tuple.Tpo" ".deps/frag_tuple.Po"; else rm -f
".deps/frag_tuple.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
frag_tuple_ip.o -MD -MP -MF ".deps/frag_tuple_ip.Tpo" -c -o frag_tuple_ip.o
frag_tuple_ip.c; \
        then mv -f ".deps/frag_tuple_ip.Tpo" ".deps/frag_tuple_ip.Po"; else
rm -f ".deps/frag_tuple_ip.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
frag_type.o -MD -MP -MF ".deps/frag_type.Tpo" -c -o frag_type.o
frag_type.c; \
        then mv -f ".deps/frag_type.Tpo" ".deps/frag_type.Po"; else rm -f
".deps/frag_type.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
frag_type_ip.o -MD -MP -MF ".deps/frag_type_ip.Tpo" -c -o frag_type_ip.o
frag_type_ip.c; \
        then mv -f ".deps/frag_type_ip.Tpo" ".deps/frag_type_ip.Po"; else
rm -f ".deps/frag_type_ip.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
filter_match.o -MD -MP -MF ".deps/filter_match.Tpo" -c -o filter_match.o
filter_match.c; \
        then mv -f ".deps/filter_match.Tpo" ".deps/filter_match.Po"; else
rm -f ".deps/filter_match.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
filter_match_ip.o -MD -MP -MF ".deps/filter_match_ip.Tpo" -c -o
filter_match_ip.o filter_match_ip.c; \
        then mv -f ".deps/filter_match_ip.Tpo" ".deps/filter_match_ip.Po";
else rm -f ".deps/filter_match_ip.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
filter_match_udp.o -MD -MP -MF ".deps/filter_match_udp.Tpo" -c -o
filter_match_udp.o filter_match_udp.c; \
        then mv -f ".deps/filter_match_udp.Tpo"
".deps/filter_match_udp.Po"; else rm -f ".deps/filter_match_udp.Tpo"; exit
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
filter_match_tcp.o -MD -MP -MF ".deps/filter_match_tcp.Tpo" -c -o
filter_match_tcp.o filter_match_tcp.c; \
        then mv -f ".deps/filter_match_tcp.Tpo"
".deps/filter_match_tcp.Po"; else rm -f ".deps/filter_match_tcp.Tpo"; exit
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
netset.o -MD -MP -MF ".deps/netset.Tpo" -c -o netset.o netset.c; \
        then mv -f ".deps/netset.Tpo" ".deps/netset.Po"; else rm -f
".deps/netset.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
uamsrv.o -MD -MP -MF ".deps/uamsrv.Tpo" -c -o uamsrv.o uamsrv.c; \
        then mv -f ".deps/uamsrv.Tpo" ".deps/uamsrv.Po"; else rm -f
".deps/uamsrv.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
 -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
sweetspot.o -MD -MP -MF ".deps/sweetspot.Tpo" -c -o sweetspot.o
sweetspot.c; \
        then mv -f ".deps/sweetspot.Tpo" ".deps/sweetspot.Po"; else rm -f
".deps/sweetspot.Tpo"; exit 1; fi
/bin/sh ../libtool --tag=CC --mode=link gcc -g -g -O2   -o sweetspot  if.o
session.o gauge.o nat_src.o nat_dst.o relay_inward.o relay_outward.o
filter.o acct.o acct_method.o acct_method_detail.o
acct_method_detail_snat.o acct_method_detail_session.o
acct_method_detail_gauge.o acct_method_detail_event.o acct_scope.o
acct_scope_event.o acct_scope_session.o acct_scope_gauge.o
acct_scope_snat.o flog.o lhash.o filter_scanner.o filter_parser.o tuple.o
tuple_ip.o tuple_tcp.o tuple_udp.o tuple_icmp.o tuple_checksum.o
relay_validate.o relay_validate_ip.o gauge_index.o gauge_index_ip.o
nat_src_endpoint.o nat_src_endpoint_ip.o nat_src_endpoint_tcp.o
nat_src_endpoint_udp.o nat_src_endpoint_icmp.o nat_dst_endpoint.o
nat_dst_endpoint_ip.o nat_dst_endpoint_tcp.o nat_dst_endpoint_udp.o
nat_tuple.o nat_tuple_ip.o nat_tuple_icmp.o frag.o frag_tuple.o
frag_tuple_ip.o frag_type.o frag_type_ip.o filter_match.o filter_match_ip.o
filter_match_udp.o filter_match_tcp.o netset.o uamsrv.o sweetspot.o
libsweetuam.a libsweetmisc.a
mkdir .libs
gcc -g -g -O2 -o sweetspot if.o session.o gauge.o nat_src.o nat_dst.o
relay_inward.o relay_outward.o filter.o acct.o acct_method.o
acct_method_detail.o acct_method_detail_snat.o acct_method_detail_session.o
acct_method_detail_gauge.o acct_method_detail_event.o acct_scope.o
acct_scope_event.o acct_scope_session.o acct_scope_gauge.o
acct_scope_snat.o flog.o lhash.o filter_scanner.o filter_parser.o tuple.o
tuple_ip.o tuple_tcp.o tuple_udp.o tuple_icmp.o tuple_checksum.o
relay_validate.o relay_validate_ip.o gauge_index.o gauge_index_ip.o
nat_src_endpoint.o nat_src_endpoint_ip.o nat_src_endpoint_tcp.o
nat_src_endpoint_udp.o nat_src_endpoint_icmp.o nat_dst_endpoint.o
nat_dst_endpoint_ip.o nat_dst_endpoint_tcp.o nat_dst_endpoint_udp.o
nat_tuple.o nat_tuple_ip.o nat_tuple_icmp.o frag.o frag_tuple.o
frag_tuple_ip.o frag_type.o frag_type_ip.o filter_match.o filter_match_ip.o
filter_match_udp.o filter_match_tcp.o netset.o uamsrv.o sweetspot.o
 libsweetuam.a libsweetmisc.a
nat_src_endpoint_ip.o: In function `__new':
/home/Rai/sweetspot-0.0.20/src/nat_src_endpoint_ip.c:95: undefined
reference to `ceilf'
nat_src_endpoint_tcp.o: In function `__create':
/home/Rai/sweetspot-0.0.20/src/nat_src_endpoint_tcp.c:58: undefined
reference to `ceilf'
nat_src_endpoint_udp.o: In function `__create':
/home/Rai/sweetspot-0.0.20/src/nat_src_endpoint_udp.c:59: undefined
reference to `ceilf'
nat_src_endpoint_icmp.o: In function `__create':
/home/Rai/sweetspot-0.0.20/src/nat_src_endpoint_icmp.c:48: undefined
reference to `ceilf'
collect2: ld returned 1 exit status
make[3]: *** [sweetspot] Error 1
make[3]: Leaving directory `/home/Rai/sweetspot-0.0.20/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/Rai/sweetspot-0.0.20/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/Rai/sweetspot-0.0.20'
make: *** [all] Error 2

[sweetspot-users] AUTO: Rogalski, John is out of the office. (returning 03/23/2011)

[<Joh...@hu...>]

I will be out of the office starting 03/28/2011 and will not return until
03/31/2011.




Note: This is an automated response to your message  "[sweetspot-users]
doubts about sweetspot" sent on 3/15/2011 12:44:07 AM.

This is the only notification you will receive while this person is away.

This e-mail (and/or attachments) is confidential and may be privileged. Use or disclosure of it by anyone other than a designated addressee is unauthorized. 
If you are not an intended recipient, please delete this e-mail from the computer on which you received it. We thank you for notifying us immediately.

[sweetspot-users] doubts about sweetspot

[Nicolas M. <ns...@gm...>]

Hello. We're a group of telecomunications engineering  students, and we´re
developing our degree proyect which is a hotspot. We just discover the linux
and open source world, and we're amazed on the possibilities that it offers.
We have just discovered your Sweetspot project, it has a lot of features
that we need; but we haven't been able to make it work. Which Linux do you
recommend us to make it run? Which are the required dependencies? Does it
need a gateway like the chillispot needs the dd-wrt? Which is the captive
portal for the authentication? Is it possible to make the sweetspot work
with the php-myprepaid? Can you handle several ip segments (/20, /16)?
Is it possible to create a patch that integrates all of your software's
feature, and use it with the chillispot?
 The hotspot that we have working has php myprepaid with free radius,
chillispot, running on a LAMP server, and as a gateway dd-wrt on the access
point.
One of the characteristics that the panel demands is that any computer can
connect to the wireless network. So that when the person logs in the captive
portal, it  allows them to choose between a public ip, in case it has an
static ip and wants to connect to the campus server through the vpn.

We're really ashamed of our ignorance, but we have been investigating for
several months how to integrate both softwares (chilli and sweetspot)
Thank you for your time!

Re: [sweetspot-users] Apache server on OUTSIDE interface

[Ilya E. <il...@gl...>]

Make sure you met the following guidelines (from http://sweetspot.sf.net/)

   1. The inner-interface has host netmask (255.255.255.255) configured, so
      that all locally generated packets will not be routed to directly
      connected broadband network e.g., will always pass through Sweetspot.

If it does not help, please, let me know.

-ilya

>   We are making great progress with our SweetSpot server.  We are
> experiencing troubles running our Apache Capture Portal on the same machine
> as the SweetSpot server.  It seems this has come up before in the past, and
> the trouble was over come by some.
>
>  I was hoping there would be an easy solution for this, or something in the
> road map for SweetSpot. We are able to DNAT to any server OUTSIDE of the
> SweetSpot server, but we are unable to DNAT to even the outside interface of
> the SweetSpot server.

[sweetspot-users] Apache server on OUTSIDE interface

[Robert L. <dar...@gm...>]

Hello,

   We are making great progress with our SweetSpot server.  We are
experiencing troubles running our Apache Capture Portal on the same machine
as the SweetSpot server.  It seems this has come up before in the past, and
the trouble was over come by some.

  I was hoping there would be an easy solution for this, or something in the
road map for SweetSpot. We are able to DNAT to any server OUTSIDE of the
SweetSpot server, but we are unable to DNAT to even the outside interface of
the SweetSpot server.

UAM Works awesome, and we can surf to the login page from the clients if we
type the address in directly.

////OUR FILTER FOR TESTING:
# DNS loophole
pass in proto udp to 64.212.106.84 port eq 53
pass out proto udp from 64.212.106.84 port eq 53

 dnat HTTP
dnat in proto tcp to port eq 80 redir to 172.16.10.9 port 80
dnat out proto tcp from 172.16.10.9 port eq 80

# no connectivity beyond this point
pass in
pass out

////END OF FILTER

///CONFIG FILE
# Sweetspot daemon configuration

# inner interface name (which is close to users)
inner-interface eth0

# outer interface name (which is close to Internet)
outer-interface eth1

# user IP CIDR (addresses anyhow assigned to user computers)
#user-networks 127.0.0.0
user-networks 172.31.18.0/27, 172.31.18.64/27, 172.31.18.32/27

# SNAT public networks
snat-public-networks 172.16.10.10

# authentication server address
uam-server-address 127.0.0.1

# authentication server port
uam-server-port 3993

# authentication server shared secret (auth client must have the same)
#uam-secret n0m0n3yn0hun3y

# report UAM errors back to client (obsolete)
#uam-report-errors 1

# Detail file accounting
acct-detail-file /var/sweetspot/detail

# Interim accounting interval (in secs)
#acct-interim-interval 300

# NAS-IP-Address to report in acct detail file
acct-nas-ip-address 127.0.0.1

# Packet filters directory
filter-dir /usr/local/etc/sweetspot/filters

# Captive filter
filter-anonymous anonymous

///END OF CONFIG FILE

Thanks for any help you can provide,

Robert Lupinek

Re: [sweetspot-users] Problem with TCP sessions resetting for UAM client

[Ilya E. <il...@gl...>]

That also seems to be an inconsistency in 0.0.18 code.

I'm almost sure that you could take the perl part from 0.0.19 and compile 
it with 0.0.18.

Alternatively, please, find relevant patch to 0.0.18 attached to this 
message.

-ilya

> When trying to compile version 0.0.18 the SweetAuth Perl Libraries I get a
> error during make:
>
> hbsvsl04:/usr/src/sweetspot-0.0.18/perl/SweetAuth # perl Makefile.PL
> Warning: -L../../src changed to
> -L/usr/src/sweetspot-0.0.18/perl/SweetAuth/../../src
> Writing Makefile for SweetAuth
> hbsvsl04:/usr/src/sweetspot-0.0.18/perl/SweetAuth # make
> cc -c  -I../../src -D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV
> -DDEBUGGING -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall
> -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
> -fasynchronous-unwind-tables -g -Wall -pipe   -DVERSION=\"0.01\"
> -DXS_VERSION=\"0.01\" -fPIC
> "-I/usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE"   SweetAuth.c
> In file included from SweetAuth.xs:5:
> ppport.h:3042:1: warning: "PERL_UNUSED_DECL" redefined
> In file included from SweetAuth.xs:2:
> /usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE/perl.h:299:1: warning:
> this is the location of the previous definition
> SweetAuth.c: In function âXS_SweetAuth_constantâ:
> const-xs.inc:5: warning: unused variable âtargâ
> SweetAuth.c:37: warning: unused variable âPerl___notusedâ
> SweetAuth.xs: In function âXS_SweetAuth_sweetauthâ:
> SweetAuth.xs:25: error: âSW_UAM_ARG_VECTOR_SIZEâ undeclared (first use in
> this function)
> SweetAuth.xs:25: error: (Each undeclared identifier is reported only once
> SweetAuth.xs:25: error: for each function it appears in.)
> SweetAuth.xs:40: warning: implicit declaration of function âsw_config_loadâ
> SweetAuth.xs:25: warning: unused variable âsw_argvâ
> SweetAuth.c:157: warning: unused variable âtargâ
> SweetAuth.c:156: warning: unused variable âRETVALâ
> SweetAuth.c:148: warning: unused variable âPerl___notusedâ
> SweetAuth.c: In function âboot_SweetAuthâ:
> SweetAuth.c:218: warning: unused variable âPerl___notusedâ
> make: *** [SweetAuth.o] Error 1
>
> I was hoping you would have some insight into the cause of this problem.  We
> are running 0.0.18 due to a bug in the source for 0.0.19 that I believe you
> are already addressing.

Re: [sweetspot-users] Problem with TCP sessions resetting for UAM client

[Robert L. <dar...@gm...>]

ilya,

Your observations were correct!  It does appear that we were having our
packets processed twice!  We were able to resolve the issue by using a
different IP for our SNAT address and our Outside interface, as you
suggested.  Thanks!

As for your question about doing NAT on the sweetspot, our firewall exists
off the sweetspot server, we cannot use internet routable IP's until that
hop.

I have another question that I was saving until we were able to truly route
through the sweetspot daemon.

When trying to compile version 0.0.18 the SweetAuth Perl Libraries I get a
error during make:

hbsvsl04:/usr/src/sweetspot-0.0.18/perl/SweetAuth # perl Makefile.PL
Warning: -L../../src changed to
-L/usr/src/sweetspot-0.0.18/perl/SweetAuth/../../src
Writing Makefile for SweetAuth
hbsvsl04:/usr/src/sweetspot-0.0.18/perl/SweetAuth # make
cc -c  -I../../src -D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV
-DDEBUGGING -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g -Wall -pipe   -DVERSION=\"0.01\"
-DXS_VERSION=\"0.01\" -fPIC
"-I/usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE"   SweetAuth.c
In file included from SweetAuth.xs:5:
ppport.h:3042:1: warning: "PERL_UNUSED_DECL" redefined
In file included from SweetAuth.xs:2:
/usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE/perl.h:299:1: warning:
this is the location of the previous definition
SweetAuth.c: In function âXS_SweetAuth_constantâ:
const-xs.inc:5: warning: unused variable âtargâ
SweetAuth.c:37: warning: unused variable âPerl___notusedâ
SweetAuth.xs: In function âXS_SweetAuth_sweetauthâ:
SweetAuth.xs:25: error: âSW_UAM_ARG_VECTOR_SIZEâ undeclared (first use in
this function)
SweetAuth.xs:25: error: (Each undeclared identifier is reported only once
SweetAuth.xs:25: error: for each function it appears in.)
SweetAuth.xs:40: warning: implicit declaration of function âsw_config_loadâ
SweetAuth.xs:25: warning: unused variable âsw_argvâ
SweetAuth.c:157: warning: unused variable âtargâ
SweetAuth.c:156: warning: unused variable âRETVALâ
SweetAuth.c:148: warning: unused variable âPerl___notusedâ
SweetAuth.c: In function âboot_SweetAuthâ:
SweetAuth.c:218: warning: unused variable âPerl___notusedâ
make: *** [SweetAuth.o] Error 1

I was hoping you would have some insight into the cause of this problem.  We
are running 0.0.18 due to a bug in the source for 0.0.19 that I believe you
are already addressing.

Thank you for your help, and a BIG thank for this software!

Robert Lupinek



On Fri, Sep 25, 2009 at 1:02 PM, Ilya Etingof <il...@gl...> wrote:

>
> My immediate impression is that you are having an IP address conflict
> between eth1's own address and NAT network configured to the sweetspot.
>
> Every packet destined to 172.16.10.10 would be received, and potentially
> processed, by both Linux kernel and sweetspot daemon. That may cause
> mess and glitches. Therefore your interface IPs and NAT IPs should never
> overlap.
>
> BTW, do you really need sweetspot doing source NAT given you seem to have
> a firewall doing NAT as well? Maybe you could do NAT at either of these
> NAT devices?
>
> -ilya
>
> >   We are currently running sweetspot version 0.0.18, and we are having
> > problems with TCP sessions being reset when we route through the
> sweetspot
> > server.  All connectionless protocols complete without error.  Pings and
> DNS
> > lookups work just fine.
> >
> > I am sorry if this is information overload!  I just see you asking for
> these
> > things in your other trouble shooting mails.
> >
> >  When ever we try to ftp on port 21 or surf on port 80 we drop
> connection.
> > *
> >
> > Here is an excerpt from our firewall:*
> >
> > Index    Date/Time            Device        Event
> > 91    2009/09/24 16:00:55.976 CEST    172.16.75.1    Sep 24 2009
> 10:00:55:
> > %PIX-6-302013: Built outbound TCP connection 105790010 for outside:
> > 66.96.134.57/21 (66.96.134.57/21) to DMZ10-chilli-outside:
> 172.16.10.10/12646( <http://172.16.10.10/12646%28>
> > 208.50.251.136/12646)
> > 92    2009/09/24 16:00:56.070 CEST    172.16.75.1    Sep 24 2009
> 10:00:55:
> > %PIX-6-302014: Teardown TCP connection 105790010 for
> > outside:66.96.134.57/21to DMZ10-chilli-outside:
> > 172.16.10.10/12646 duration 0:00:00 bytes 0 TCP Reset-I
> > 93    2009/09/24 16:00:56.070 CEST    172.16.75.1    Sep 24 2009
> 10:00:55:
> > %PIX-6-106015: Deny TCP (no connection) from 172.16.10.10/12646 to
> > 66.96.134.57/21 flags ACK  on interface DMZ10-chilli-outside
> >
> > Message 91: The sweetspot has forwarded a ftp-packet from a client. That
> > initiates a session in the firewall.
> > Message 92: The sweetspot sends a TCP-reset packet which causes the
> firewall
> > to drop the session built before
> > Message 93: The answer-packet from the ftp-server could not be forwarded,
> > because the session has been terminated.
> >
> >
> > We are releasing the IP of the client that connects.  We aren't yet ready
> to
> > test authentication until we can get a client to route all the way
> through.
> >
> > *sweetuam UP 172.31.18.4*
> > Thu Sep 24 10:14:01 2009 [21196] uamsrv.c:310 resolution OK 172.31.18.4
> > Thu Sep 24 10:14:01 2009 [21196] uammsg.c:86 encoding UAM message
> > Thu Sep 24 10:14:01 2009 [21196] uammsg.c:97 UAM arg #0: OK
> > Thu Sep 24 10:14:01 2009 [21196] uammsg.c:97 UAM arg #1: 172.31.18.4
> > Thu Sep 24 10:14:01 2009 [21196] uammsg.c:37 encrypted UAM msg: 15 octets
> > Thu Sep 24 10:14:01 2009 [21196] uamsrv.c:330 sent UAM msg: 15 octets
> >
> >
> >
> >
> > I've included our configuration files and server setup to give you a
> better
> > idea of what I am talking about:
> >
> > *sweetspot.conf*
> > # Sweetspot daemon configuration
> > # inner interface name (which is close to users)
> > inner-interface eth0
> > # outer interface name (which is close to Internet)
> > outer-interface eth1
> > # user IP CIDR (addresses anyhow assigned to user computers)
> > #user-networks 127.0.0.0
> > user-networks 172.31.18.0/27
> > # SNAT public networks
> > snat-public-networks 172.16.10.10/32
> > # authentication server address
> > uam-server-address 127.0.0.1
> > # authentication server port
> > uam-server-port 3993
> > # authentication server shared secret (auth client must have the same)
> > #uam-secret n0m0n3yn0hun3y
> > # report UAM errors back to client (obsolete)
> > #uam-report-errors 1
> > # Detail file accounting
> > acct-detail-file /var/sweetspot/detail
> > # Interim accounting interval (in secs)
> > #acct-interim-interval 300
> > # NAS-IP-Address to report in acct detail file
> > acct-nas-ip-address 127.0.0.1
> > # Packet filters directory
> > filter-dir /usr/local/etc/sweetspot/filters
> > # Captive filter
> > #filter-anonymous anonymous
> >
> > *sweetuam.conf*
> > # Sweetspot UAM client configuration
> > # authentication server group (comma-separated list)
> > uam-server-group 127.0.0.1:3993
> > # originate client message from this address
> > #uam-client-address 0.0.0.0
> > # UAM client receive timeout
> > #uam-client-timeout 1
> > # authentication client shared secret (auth server must have the same)
> > #uam-secret n0m0n3yn0hun3y
> >
> > *Interfaces*
> > eth0   inet addr:172.16.11.10  Bcast:0.0.0.0  Mask:255.255.255.255  <--
> > Inside
> > eth1   inet addr:172.16.10.10  Bcast:172.16.10.255  Mask:255.255.255.0
>  <--
> > Outside
> >
> > ***Kernel IP routing table*
> > Destination     Gateway         Genmask         Flags Metric Ref    Use
> > Iface
> > 172.16.10.0     *               255.255.255.0   U     0      0        0
> eth1
> > 172.31.0.0      *               255.255.0.0     U     0      0        0
> > eth0  <--Route back to wireless clients
> > link-local      *               255.255.0.0     U     0      0        0
> eth0
> > loopback        *               255.0.0.0       U     0      0        0
> lo
> > default         172.16.10.1     0.0.0.0         UG    0      0        0
> eth1
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> sweetspot-users mailing list
> swe...@li...
> https://lists.sourceforge.net/lists/listinfo/sweetspot-users
>
>

Re: [sweetspot-users] Problem with TCP sessions resetting for UAM client

[Ilya E. <il...@gl...>]

My immediate impression is that you are having an IP address conflict 
between eth1's own address and NAT network configured to the sweetspot.

Every packet destined to 172.16.10.10 would be received, and potentially 
processed, by both Linux kernel and sweetspot daemon. That may cause
mess and glitches. Therefore your interface IPs and NAT IPs should never
overlap.

BTW, do you really need sweetspot doing source NAT given you seem to have 
a firewall doing NAT as well? Maybe you could do NAT at either of these 
NAT devices?

-ilya

>   We are currently running sweetspot version 0.0.18, and we are having
> problems with TCP sessions being reset when we route through the sweetspot
> server.  All connectionless protocols complete without error.  Pings and DNS
> lookups work just fine.
>
> I am sorry if this is information overload!  I just see you asking for these
> things in your other trouble shooting mails.
>
>  When ever we try to ftp on port 21 or surf on port 80 we drop connection.
> *
>
> Here is an excerpt from our firewall:*
>
> Index    Date/Time            Device        Event
> 91    2009/09/24 16:00:55.976 CEST    172.16.75.1    Sep 24 2009 10:00:55:
> %PIX-6-302013: Built outbound TCP connection 105790010 for outside:
> 66.96.134.57/21 (66.96.134.57/21) to DMZ10-chilli-outside:172.16.10.10/12646(
> 208.50.251.136/12646)
> 92    2009/09/24 16:00:56.070 CEST    172.16.75.1    Sep 24 2009 10:00:55:
> %PIX-6-302014: Teardown TCP connection 105790010 for
> outside:66.96.134.57/21to DMZ10-chilli-outside:
> 172.16.10.10/12646 duration 0:00:00 bytes 0 TCP Reset-I
> 93    2009/09/24 16:00:56.070 CEST    172.16.75.1    Sep 24 2009 10:00:55:
> %PIX-6-106015: Deny TCP (no connection) from 172.16.10.10/12646 to
> 66.96.134.57/21 flags ACK  on interface DMZ10-chilli-outside
>
> Message 91: The sweetspot has forwarded a ftp-packet from a client. That
> initiates a session in the firewall.
> Message 92: The sweetspot sends a TCP-reset packet which causes the firewall
> to drop the session built before
> Message 93: The answer-packet from the ftp-server could not be forwarded,
> because the session has been terminated.
>
>
> We are releasing the IP of the client that connects.  We aren't yet ready to
> test authentication until we can get a client to route all the way through.
>
> *sweetuam UP 172.31.18.4*
> Thu Sep 24 10:14:01 2009 [21196] uamsrv.c:310 resolution OK 172.31.18.4
> Thu Sep 24 10:14:01 2009 [21196] uammsg.c:86 encoding UAM message
> Thu Sep 24 10:14:01 2009 [21196] uammsg.c:97 UAM arg #0: OK
> Thu Sep 24 10:14:01 2009 [21196] uammsg.c:97 UAM arg #1: 172.31.18.4
> Thu Sep 24 10:14:01 2009 [21196] uammsg.c:37 encrypted UAM msg: 15 octets
> Thu Sep 24 10:14:01 2009 [21196] uamsrv.c:330 sent UAM msg: 15 octets
>
>
>
>
> I've included our configuration files and server setup to give you a better
> idea of what I am talking about:
>
> *sweetspot.conf*
> # Sweetspot daemon configuration
> # inner interface name (which is close to users)
> inner-interface eth0
> # outer interface name (which is close to Internet)
> outer-interface eth1
> # user IP CIDR (addresses anyhow assigned to user computers)
> #user-networks 127.0.0.0
> user-networks 172.31.18.0/27
> # SNAT public networks
> snat-public-networks 172.16.10.10/32
> # authentication server address
> uam-server-address 127.0.0.1
> # authentication server port
> uam-server-port 3993
> # authentication server shared secret (auth client must have the same)
> #uam-secret n0m0n3yn0hun3y
> # report UAM errors back to client (obsolete)
> #uam-report-errors 1
> # Detail file accounting
> acct-detail-file /var/sweetspot/detail
> # Interim accounting interval (in secs)
> #acct-interim-interval 300
> # NAS-IP-Address to report in acct detail file
> acct-nas-ip-address 127.0.0.1
> # Packet filters directory
> filter-dir /usr/local/etc/sweetspot/filters
> # Captive filter
> #filter-anonymous anonymous
>
> *sweetuam.conf*
> # Sweetspot UAM client configuration
> # authentication server group (comma-separated list)
> uam-server-group 127.0.0.1:3993
> # originate client message from this address
> #uam-client-address 0.0.0.0
> # UAM client receive timeout
> #uam-client-timeout 1
> # authentication client shared secret (auth server must have the same)
> #uam-secret n0m0n3yn0hun3y
>
> *Interfaces*
> eth0   inet addr:172.16.11.10  Bcast:0.0.0.0  Mask:255.255.255.255  <--
> Inside
> eth1   inet addr:172.16.10.10  Bcast:172.16.10.255  Mask:255.255.255.0  <--
> Outside
>
> ***Kernel IP routing table*
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 172.16.10.0     *               255.255.255.0   U     0      0        0 eth1
> 172.31.0.0      *               255.255.0.0     U     0      0        0
> eth0  <--Route back to wireless clients
> link-local      *               255.255.0.0     U     0      0        0 eth0
> loopback        *               255.0.0.0       U     0      0        0 lo
> default         172.16.10.1     0.0.0.0         UG    0      0        0 eth1

[sweetspot-users] Problem with TCP sessions resetting for UAM client

[Robert L. <dar...@gm...>]

Hello,

   We are currently running sweetspot version 0.0.18, and we are having
problems with TCP sessions being reset when we route through the sweetspot
server.  All connectionless protocols complete without error.  Pings and DNS
lookups work just fine.

I am sorry if this is information overload!  I just see you asking for these
things in your other trouble shooting mails.

  When ever we try to ftp on port 21 or surf on port 80 we drop connection.
*

Here is an excerpt from our firewall:*

Index    Date/Time            Device        Event
91    2009/09/24 16:00:55.976 CEST    172.16.75.1    Sep 24 2009 10:00:55:
%PIX-6-302013: Built outbound TCP connection 105790010 for outside:
66.96.134.57/21 (66.96.134.57/21) to DMZ10-chilli-outside:172.16.10.10/12646(
208.50.251.136/12646)
92    2009/09/24 16:00:56.070 CEST    172.16.75.1    Sep 24 2009 10:00:55:
%PIX-6-302014: Teardown TCP connection 105790010 for
outside:66.96.134.57/21to DMZ10-chilli-outside:
172.16.10.10/12646 duration 0:00:00 bytes 0 TCP Reset-I
93    2009/09/24 16:00:56.070 CEST    172.16.75.1    Sep 24 2009 10:00:55:
%PIX-6-106015: Deny TCP (no connection) from 172.16.10.10/12646 to
66.96.134.57/21 flags ACK  on interface DMZ10-chilli-outside

Message 91: The sweetspot has forwarded a ftp-packet from a client. That
initiates a session in the firewall.
Message 92: The sweetspot sends a TCP-reset packet which causes the firewall
to drop the session built before
Message 93: The answer-packet from the ftp-server could not be forwarded,
because the session has been terminated.


We are releasing the IP of the client that connects.  We aren't yet ready to
test authentication until we can get a client to route all the way through.

*sweetuam UP 172.31.18.4*
Thu Sep 24 10:14:01 2009 [21196] uamsrv.c:310 resolution OK 172.31.18.4
Thu Sep 24 10:14:01 2009 [21196] uammsg.c:86 encoding UAM message
Thu Sep 24 10:14:01 2009 [21196] uammsg.c:97 UAM arg #0: OK
Thu Sep 24 10:14:01 2009 [21196] uammsg.c:97 UAM arg #1: 172.31.18.4
Thu Sep 24 10:14:01 2009 [21196] uammsg.c:37 encrypted UAM msg: 15 octets
Thu Sep 24 10:14:01 2009 [21196] uamsrv.c:330 sent UAM msg: 15 octets




I've included our configuration files and server setup to give you a better
idea of what I am talking about:

*sweetspot.conf*
# Sweetspot daemon configuration
# inner interface name (which is close to users)
inner-interface eth0
# outer interface name (which is close to Internet)
outer-interface eth1
# user IP CIDR (addresses anyhow assigned to user computers)
#user-networks 127.0.0.0
user-networks 172.31.18.0/27
# SNAT public networks
snat-public-networks 172.16.10.10/32
# authentication server address
uam-server-address 127.0.0.1
# authentication server port
uam-server-port 3993
# authentication server shared secret (auth client must have the same)
#uam-secret n0m0n3yn0hun3y
# report UAM errors back to client (obsolete)
#uam-report-errors 1
# Detail file accounting
acct-detail-file /var/sweetspot/detail
# Interim accounting interval (in secs)
#acct-interim-interval 300
# NAS-IP-Address to report in acct detail file
acct-nas-ip-address 127.0.0.1
# Packet filters directory
filter-dir /usr/local/etc/sweetspot/filters
# Captive filter
#filter-anonymous anonymous

*sweetuam.conf*
# Sweetspot UAM client configuration
# authentication server group (comma-separated list)
uam-server-group 127.0.0.1:3993
# originate client message from this address
#uam-client-address 0.0.0.0
# UAM client receive timeout
#uam-client-timeout 1
# authentication client shared secret (auth server must have the same)
#uam-secret n0m0n3yn0hun3y

*Interfaces*
eth0   inet addr:172.16.11.10  Bcast:0.0.0.0  Mask:255.255.255.255  <--
Inside
eth1   inet addr:172.16.10.10  Bcast:172.16.10.255  Mask:255.255.255.0  <--
Outside

***Kernel IP routing table*
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
172.16.10.0     *               255.255.255.0   U     0      0        0 eth1
172.31.0.0      *               255.255.0.0     U     0      0        0
eth0  <--Route back to wireless clients
link-local      *               255.255.0.0     U     0      0        0 eth0
loopback        *               255.0.0.0       U     0      0        0 lo
default         172.16.10.1     0.0.0.0         UG    0      0        0 eth1


Thank you so much, again!

Robert Lupinek

Re: [sweetspot-users] Make Error - openSUSE 2.6.27.7-9-pae

[Ilya E. <il...@gl...>]

That's because of a piece of stray code lurked into this release. Here's a 
fix:

*** sweetspot-0.0.19/src/nat_src.c%	Wed Jun  3 19:20:32 2009
--- sweetspot-0.0.19/src/nat_src.c	Mon Sep  7 14:40:06 2009
***************
*** 100,115 ****
           sw_log("%s:%d existing relation #%u %s [%s]", __FILE__, __LINE__,
                  r->seq, sw_tuple_pretty(r->prv), sw_tuple_pretty(r->pub));
         *pub = r->pub;
-       seq_distance = global_seq_ticker - r->seq;
-       seq_distance = seq_distance > 0 ? seq_distance : -seq_distance;
-       if (seq_distance > SW_NAT_SRC_RELATIONS_MAX/3) {
-         if (sw_debug_flags & SW_DEBUG_NAT_SRC)
-           sw_log("%s:%d renewing relation #%u %s [%s]", __FILE__, __LINE__,
-                  r->seq, sw_tuple_pretty(r->prv), sw_tuple_pretty(r->pub));
-         lh_delete(global_nat_src_seq_hash, (void *)r);
-         r->seq = global_seq_ticker;
-         lh_insert(global_nat_src_seq_hash, (void *)r);
-       }
     } else {
       if (global_seq_ticker == SW_NAT_SRC_RELATIONS_MAX)
         global_seq_ticker = 0;
--- 100,105 ----

Next sweetspot revision will have this fixed.

-ilya

>   I'm attempting to compile Sweetspot on an openSUSE box running kernel
> 2.6.27.7-9-pae.  My version of GCC is at 4.3.
>
> I get the following error when attempting to run make from the source
> directory of SweetSpot0.0.19:
>
> make[3]: Entering directory `/usr/src/sweetspot-0.0.19/src'
> if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
> -DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
> nat_src.o -MD -MP -MF ".deps/nat_src.Tpo" -c -o nat_src.o nat_src.c; \
>        then mv -f ".deps/nat_src.Tpo" ".deps/nat_src.Po"; else rm -f
> ".deps/nat_src.Tpo"; exit 1; fi
> nat_src.c: In function âsw_nat_src_doâ:
> nat_src.c:103: error: âseq_distanceâ undeclared (first use in this function)
> nat_src.c:103: error: (Each undeclared identifier is reported only once
> nat_src.c:103: error: for each function it appears in.)
> make[3]: *** [nat_src.o] Error 1
> make[3]: Leaving directory `/usr/src/sweetspot-0.0.19/src'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/usr/src/sweetspot-0.0.19/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/sweetspot-0.0.19'
> make: *** [all] Error 2
>
> Let me know if you guys have encountered this, or have a fix.  Really
> appreciate you reading this.

[sweetspot-users] Make Error - openSUSE 2.6.27.7-9-pae

[Robert L. <dar...@gm...>]

Hello,

   I'm attempting to compile Sweetspot on an openSUSE box running kernel
2.6.27.7-9-pae.  My version of GCC is at 4.3.

I get the following error when attempting to run make from the source
directory of SweetSpot0.0.19:

make[3]: Entering directory `/usr/src/sweetspot-0.0.19/src'
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
-DSW_DEFAULT_CONFIG_DIR="\"/usr/local/etc/sweetspot\"" -g -g -O2 -MT
nat_src.o -MD -MP -MF ".deps/nat_src.Tpo" -c -o nat_src.o nat_src.c; \
        then mv -f ".deps/nat_src.Tpo" ".deps/nat_src.Po"; else rm -f
".deps/nat_src.Tpo"; exit 1; fi
nat_src.c: In function âsw_nat_src_doâ:
nat_src.c:103: error: âseq_distanceâ undeclared (first use in this function)
nat_src.c:103: error: (Each undeclared identifier is reported only once
nat_src.c:103: error: for each function it appears in.)
make[3]: *** [nat_src.o] Error 1
make[3]: Leaving directory `/usr/src/sweetspot-0.0.19/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/sweetspot-0.0.19/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/sweetspot-0.0.19'
make: *** [all] Error 2

Let me know if you guys have encountered this, or have a fix.  Really
appreciate you reading this.

Thanks,

Robert Lupinek

Re: [sweetspot-users] Sweetspot Information

[Ilya E. <il...@gl...>]

Daniel,

> Hi Ilya, I am afraid I can not even get my clients to get a dhcp 
> address. I have a centos box with eth0 10.201.0.101/16 as the external 
> device, eth1 is 10.201.0.129/32 (as outlined in your manual) and I

If you choose to use all IPs (inner, outer and clients) from the same
network, make sure your clients won't get the same IP as you assign
to your interfaces.

> followed the instructions on your web pages. I have an internode adsl 
> internet connection going out via eth0 throught a router. I have listed
> all my configurations with notes on the side, I hope you can help me. 
> Thank you for devoting your time on this, it is greatly appreciated.

So far I do not see what makes this setup not working. Could you sniff
some traffic from your client on both eth0 & eth1 interfaces?

For instance, could you run a ping 68.180.206.184 on your client
and then start and leave running the following commands

tcpdump -i eth1 host <your-client-ip>
tcpdump -i eth0 host <your-client-ip>

? Then run

sweetuam UP <your-client-ip>

to enable IP connectivity for this particular client and let me see what 
happens?

Read on:

> 1. Software compiled correctly.
>
> 2. vi /usr/local/etc/sweetspot/sweetspot.conf
> # Sweetspot daemon configuration
>
> # inner interface name (which is close to users)
> inner-interface eth1
>
> # outer interface name (which is close to Internet)
> outer-interface eth0
>
> # user IP CIDR (addresses anyhow assigned to user computers)
>
> #user-networks 127.0.0.0
> user-networks 10.201.0.0/16 (this is the address range I want broadband clients to receive)
>
> # SNAT public networks
>
> #snat-public-networks 192.168.104.0/30 (have no idea if I need this or not)
>
> # authentication server address
> uam-server-address www.moreways2pay.com/LaptopLogin (this is the URL i want all sweetspot wireless users to be directed to)

You have to specify local IP interface here where this daemon would 
listen for controlling commands sent by the sweetuam command line (or 
php or python) tools.

Therefore it may be:

uam-server-address 127.0.0.1

here. Your captive portal site (www.moreways2pay.com/LaptopLogin) should
reside somewhere. If it's going to be on the same server, bind your Apache
to eth0 address.

> # authentication server port
> #uam-server-port 3993
>
> # authentication server shared secret (auth client must have the same)
> uam-secret ht2eb8ej6s4et3rg1ulz
>
> # report UAM errors back to client (obsolete)
>
> #uam-report-errors 1
>
> # Detail file accounting
> acct-detail-file /var/sweetspot/detail
>
> # Interim accounting interval (in secs)
>
> #acct-interim-interval 300
>
> # NAS-IP-Address to report in acct detail file
> #acct-nas-ip-address 127.0.0.1
>
> # Packet filters directory
>
> #filter-dir /usr/local/etc/sweetspot/filters
>
> # Captive filter
> filter-anonymous anonymous
>
>
> 3. vi /usr/local/etc/sweetspot/sweetuam.conf
>
> # Sweetspot UAM client configuration
>
> # authentication server group (comma-separated list)
> uam-server-group 203.38.180.218:3993 (dont know if this is right, 203.38.180.218 is the server for the URL I wrote above , www.moreways2pay.com/LaptopLogin)

This is a way to tell sweetuam client where to send its control commands
to. If you choose to control sweetspot locally, use 127.0.0.1:3993 here.

> # originate client message from this address
> #uam-client-address 0.0.0.0 (what is this?)

This is the address from where sweetuam tool would send its control 
commands to daemon.

> # UAM client receive timeout
> #uam-client-timeout 1
>
> # authentication client shared secret (auth server must have the same)
> uam-secret ht2eb8ej6s4et3rg1ulz
>
>
> 4. vi /usr/local/etc/sweetspot/filters/anonymous
>
> #
> # If this filter is configured as a "filter-anonymous" to Sweetspot
> # daemon, it will be automatically assigned to captured sessions what
> # would cause certain services (HTTP, HTTPS, DNS) to be forced to
> # a Captive Portal authentication page.
> #
> # WARNING: replace 192.168.1.1 with IP address of your DNS and
> #          authentication server (possibly, sweetspot outer interface
> #          address if your DNS and HTTP server live on sweetspot machine)
> #          to make this filter working!
>
>
> # DNS loophole
> pass in proto udp to 192.231.203.132 port eq 53 (my public dns server)
> pass out proto udp from 192.231.203.132 port eq 53
>
>
> # dnat HTTP
> dnat in proto tcp to port eq 80 redir to 10.201.0.129 port 80 (my eth1 ip address)
> dnat out proto tcp from 10.201.0.129 port eq 80
>
> # dnat HTTPS
> dnat in proto tcp to port eq 443 redir to 10.201.0.129 port 443 (my eth1 ip address)
> dnat out proto tcp from 10.201.0.129 port eq 443

This should be the IP address where your authentication page (captive 
portal) lives.. If you choose to put it on the same server and bind your 
Apache to external interface (eth0), you should do DNAT to its IP 
(10.201.0.101).

Please, let me know if it helps.

-ilya

>
> # no connectivity beyond this point
> block in
> block out
>
>
> ________________________________________
> From: Ilya Etingof [il...@gl...]
> Sent: Friday, 26 September 2008 11:08 PM
> To: Daniel Garcia
> Cc: swe...@li...
> Subject: Re: [sweetspot-users] Sweetspot Information
>
> Daniel,
>
> There are some discussions on the Sweetspot issues on the mailing list:
>
> http://sourceforge.net/mailarchive/forum.php?forum_name=sweetspot-users
>
> although it might not cover your issues.
>
> Otherwise, please, let me know what are your problems with this software?
>
> thanks,
> ilya
>
> On Fri, 26 Sep 2008, Daniel Garcia wrote:
>
>> Hi,
>>
>> My name is Daniel and I work for a company that designs and deploys wifi
>> solutions to our clients. We have been using chilli as the software that
>> sends Radius messages to our radius server for our wireless customers to
>> authenticate their accounts. We have an issue where we designed a network
>> topology for a new site in Fiji which went against the MAC address or layer 2
>> based authentication of chilli and in our testing can not access the captive
>> portal that chilli provides.
>>
>> We have had a look at Coovachilli and we came across sweetspot, which seems
>> like would be the ideal software for us to use since its based on layer 3
>> authentication. The problem, however, is that I have run into some issues in
>> regards to setting it up and besides http://sweetspot.sourceforge.net/ there
>> seems to be no other source of help, documentation or forum postings that can
>> guide us through a successful install and trial.
>>
>> It was my hope that you would be able to supply me with a link to other
>> resources or maybe even updated documentation on this software as I would
>> really like to see it work and deployed as a software solution for our needs.
>>
>> Any assistance you could provide would be greatly appreciated.
>>
>> Thanks
>>
>> Daniel Garcia
>> Assistant IT Manager
>> Global Gossip Australia
>>
>

Re: [sweetspot-users] Sweetspot Information

[Ilya E. <il...@gl...>]

Make sure you have IP forwarding turned of in the kernel:

cat /proc/sys/net/ipv4/ip_forward

should return 0. Otherwise, do:

echo 0 > /proc/sys/net/ipv4/ip_forward

To set host netmask on your inner interface you should do something like 
this:

ifconfig eth1 netmask 255.255.255.255

If these measures do not help, please, let me see the output of:

ifconfig -a
netstat -rn

commands and your sweetspot.conf configuration file.

-ilya

> I have installed sweetspot in test Centos machine and I can not get the 
> captive portal part to work. I have set dnat to our public web server 
> for authentication, but the http traffic still goes straight through the 
> router and out to the internet.
>
> My test lab is I have a centos box with an eth0 and eth1 card. Eth0 goes 
> out to the internet and eth1 is where the private network is that had a 
> test laptop as a broadband user. I configured (as much as I could 
> understand for your instructions) the anonymous, sweetspot.conf and 
> sweetuam.conf files and ran /usr/local/etc/sweetspot.
>
> The only thing I can see is that I have set host to subnet 
> (255.255.255.255) netmask on the inner sweetspot interface to force web 
> server response packets going to external interface. I guess Im not 
> really sure what you mean by this or how to implement. Are you able to 
> give me an example how I would implement such a configuration?

Re: [sweetspot-users] Sweetspot Information

[Ilya E. <il...@gl...>]

Daniel,

There are some discussions on the Sweetspot issues on the mailing list:

http://sourceforge.net/mailarchive/forum.php?forum_name=sweetspot-users

although it might not cover your issues.

Otherwise, please, let me know what are your problems with this software?

thanks,
ilya

On Fri, 26 Sep 2008, Daniel Garcia wrote:

> Hi,
> 
> My name is Daniel and I work for a company that designs and deploys wifi 
> solutions to our clients. We have been using chilli as the software that 
> sends Radius messages to our radius server for our wireless customers to 
> authenticate their accounts. We have an issue where we designed a network 
> topology for a new site in Fiji which went against the MAC address or layer 2 
> based authentication of chilli and in our testing can not access the captive 
> portal that chilli provides.
> 
> We have had a look at Coovachilli and we came across sweetspot, which seems 
> like would be the ideal software for us to use since its based on layer 3 
> authentication. The problem, however, is that I have run into some issues in 
> regards to setting it up and besides http://sweetspot.sourceforge.net/ there 
> seems to be no other source of help, documentation or forum postings that can 
> guide us through a successful install and trial.
> 
> It was my hope that you would be able to supply me with a link to other 
> resources or maybe even updated documentation on this software as I would 
> really like to see it work and deployed as a software solution for our needs.
> 
> Any assistance you could provide would be greatly appreciated.
> 
> Thanks
> 
> Daniel Garcia
> Assistant IT Manager
> Global Gossip Australia
>