From: Don Gould <don@bowenvale.co.nz>
To: "Gáspár Lajos" <swifty@freemail.hu>
Cc: netfilter@lists.netfilter.org
Subject: Re: IPTables script problem...
Date: Fri, 27 Oct 2006 12:12:01 +1300 [thread overview]
Message-ID: <454140C1.6010201@bowenvale.co.nz> (raw)
In-Reply-To: <4540A4DB.6080001@freemail.hu>
Thanks :)
With help from a few others I found the answer...
you need sudo to do this.
See: www.tcn.bowenvale.co.nz - my web site, if you're interested in
following the progress.
What I'm working on will be gpl
Cheers Don
Gáspár Lajos wrote:
> Don Gould írta:
>> Can anyone tell me why this isn't working?
>>
> ...
>>
>> [root@bowenvale shared]# cat dhcp.src
>> #!/bin/sh
> For debug try this:
>
> #!/bin/bash -x
>
>> nowdate=$(date)
>> # echo $nowdate, $0, $1, $2, $3 >> /home/shared/dhcpconnect.log
>>
>> echo $nowdate, $2, $3 >> /home/shared/dhcpconnect.log
>>
>> echo "Start" >> /home/shared/dhcpconnect.log
>>
>> mysql -h bowenvale -u oncs -pbutterfly -e "INSERT INTO
>> oncs.tblSessionRequest (MACAddress, IPAddress) VALUES('$2', '$3
>> ');" &> /home/shared/dhcpconnect.log
> hmm...
> You mean:
> &>>/home
> ???
>> echo "Done - database log" >> /home/shared/dhcpconnect.log
>>
>> # Now we start the data accounting bit using IP tables...
>> # Make sure the iptables rules exist! This should return errors because
>> these rules should always already exist.
>> iptables -N traffic_in >> /home/shared/dhcpconnect.log
>> iptables -N traffic_out >> /home/shared/dhcpconnect.log
>>
>> echo $nowdate, $2, $3 >> /home/shared/dhcpconnect.log
>>
>> echo "Done - rule create" >> /home/shared/dhcpconnect.log
>>
>> # Create Rule for IP to count the data.
>> iptables -A traffic_in -d $3 >> /home/shared/dhcpconnect.log
>> iptables -A traffic_out -s $3 >> /home/shared/dhcpconnect.log
>>
>> echo "Done - counter add" >> /home/shared/dhcpconnect.log
>>
>> #add chains as target to FORWARD rule - after the first time, this
>> should always be already done.
>> iptables -I FORWARD 1 -j traffic_in >> /home/shared/dhcpconnect.log
>> iptables -I FORWARD 2 -j traffic_out >> /home/shared/dhcpconnect.log
>>
>>
>> echo "Done forward rule add" >> /home/shared/dhcpconnect.log
>>
>> echo "Done", $2, $3 >> /home/shared/dhcpconnect.log
>>
> What is in dhcpconnect.log ??? :)
> Could you post it? :)
>
> Swifty
--
Don Gould
www.thinkdesignprint.co.nz - www.tcn.bowenvale.co.nz -
www.bowenvale.co.nz - www.hearingbooks.co.nz - www.buxtonsquare.co.nz -
SkypeMe: ThinkDesignPrint - Good ideas: www.solarking.co.nz
prev parent reply other threads:[~2006-10-26 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:48 IPTables script problem Don Gould
2006-10-26 12:06 ` Gáspár Lajos
2006-10-26 23:12 ` Don Gould [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=454140C1.6010201@bowenvale.co.nz \
--to=don@bowenvale.co.nz \
--cc=netfilter@lists.netfilter.org \
--cc=swifty@freemail.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox