ipcop-devel Mailing List for IPCop Firewall

Mark,

Is this alpha stable enough for me to grab it and get good screen 
captures for the installation manual?

Harry
At 9:19 PM +0100 2/28/03, Mark Wormgoor wrote:
>Hi,
>
>The v1.3 alpha5 iso is online right now.
>http://prdownloads.sourceforge.net/ipcop/ipcop-1.3alpha5.iso
>         MD5: 2ea2e61465292a9b8a74d52984b3c1ed
>http://prdownloads.sourceforge.net/ipcop/ipcop-1.3alpha5.tar.gz
>         MD5: ea0891fecd46a498d71482cda218b8fe
>
>MAJOR CHANGES SINCE alpha3:
>- Rewrite of portforwarding code (thanks to Darren Critchley)
>- Lots and lots of fixes
>- Unicode support in the installer
>- Update of Speedtouch code.
>- Upgrade to Linux 2.4.20
>- New pppd, with filter on outgoing traffic for dial-on-demand
>- Added custom dyndns support to dynamic dns support
>- Logs are now saved for 52 weeks and can be queried back that far
>- You can change languages online
>- New partitioning scheme
>- Connection speed reporting for modems
>
>TESTING:
>If anyone has a Speedtouch 330 at home, could you please test it 
>with this release.  I think we need one minor change to get it to 
>work, but am not sure yet.  Please contact me personally.
>Also, if you have an ECI compatible modem or know someone with such 
>a modem, please test if you can get a connections (see 
>http://eciadsl.flashtux.org/).
>
>BUGS:
>If you do find a bug, please try to narrow it down as far as 
>possible. If at all possible, provide a bug fix ;-)
>I don't have every type of connection and can't test all of the 
>above changes myself.  Report bugs on the sourceforge.net website 
>under the bugs section (1.3 alpha).
>
>FUTURE:
>For the future, there are some small patches still waiting:
>- Port forwarding a range of ports
>- Small layout change in time setting
>I hope to get these in soon and get to beta withint 1-2 weeks. If 
>you have any changes that you want to put into 1.3 (and are willing 
>to write!), please let me know now.
>
>Kind regards,
>
>Mark Wormgoor
>--
>***************************************************************
>* |\    /|      |  /|  /       Mark Wormgoor                  *
>* | \  / |      | / | /        mailto:ma...@wo...       *
>* |  \/  |ark   |/  |/ormgoor  http://www.wormgoor.com/mark/  *
>***************************************************************
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>IPCop-devel mailing list
>IPC...@li...
>https://lists.sourceforge.net/lists/listinfo/ipcop-devel

Hi,

The v1.3 alpha5 iso is online right now.
http://prdownloads.sourceforge.net/ipcop/ipcop-1.3alpha5.iso
         MD5: 2ea2e61465292a9b8a74d52984b3c1ed
http://prdownloads.sourceforge.net/ipcop/ipcop-1.3alpha5.tar.gz
         MD5: ea0891fecd46a498d71482cda218b8fe

MAJOR CHANGES SINCE alpha3:
- Rewrite of portforwarding code (thanks to Darren Critchley)
- Lots and lots of fixes
- Unicode support in the installer
- Update of Speedtouch code.
- Upgrade to Linux 2.4.20
- New pppd, with filter on outgoing traffic for dial-on-demand
- Added custom dyndns support to dynamic dns support
- Logs are now saved for 52 weeks and can be queried back that far
- You can change languages online
- New partitioning scheme
- Connection speed reporting for modems

TESTING:
If anyone has a Speedtouch 330 at home, could you please test it with 
this release.  I think we need one minor change to get it to work, but 
am not sure yet.  Please contact me personally.
Also, if you have an ECI compatible modem or know someone with such a 
modem, please test if you can get a connections (see 
http://eciadsl.flashtux.org/).

BUGS:
If you do find a bug, please try to narrow it down as far as possible. 
If at all possible, provide a bug fix ;-)
I don't have every type of connection and can't test all of the above 
changes myself.  Report bugs on the sourceforge.net website under the 
bugs section (1.3 alpha).

FUTURE:
For the future, there are some small patches still waiting:
- Port forwarding a range of ports
- Small layout change in time setting
I hope to get these in soon and get to beta withint 1-2 weeks. If you 
have any changes that you want to put into 1.3 (and are willing to 
write!), please let me know now.

Kind regards,

Mark Wormgoor
-- 
***************************************************************
* |\    /|      |  /|  /       Mark Wormgoor                  *
* | \  / |      | / | /        mailto:ma...@wo...       *
* |  \/  |ark   |/  |/ormgoor  http://www.wormgoor.com/mark/  *
***************************************************************

----- Original Message -----
From: Sinitsyn Valentine
To: ipc...@li...
Sent: Friday, February 28, 2003 5:41 AM
Subject: [IPCop-devel] Re: Re: Tariffing


>>Can you go into more detail as to what a tariffing scrip does? I don't
>>believe I am familiar with the terminology.

>Okay, may be I've found a wrong word in a dictionary. In a few words: it's
>a convenient tool for those who pay on per-MB basis and need to distribute
>ISP's bill over several clients.

>Details are the following:

>By default, IpCop only accounts incoming/outgoing data for
>every interface (and draws some nice graphs). But what I need is
>something more: I need per-client accounting and not only in MBytes
>but in USDs (or other currency). So I wrote the script I've called
>"tarriffing".

It sounds like this keeps track of traffic through the orange network, does
it monitor usage of each individual IP through the green network. While I
know it is a feature of QoS in the 2.4 kernel, I would really like to track
internet usage in Kilobytes or MB for each user on a network. Many clients
have complained of internet abuse by employees but can't pin it down to an
individual.

If your script does this, then I am very interested, can you please
elaborate a little more?

Darren

----- Original Message -----
From: Jesse Goerz
To: Darren Critchley
Sent: Friday, February 28, 2003 4:30 AM
Subject: Re: [IPCop-devel] Help with C


On Thu, 2003-02-27 at 22:09, Darren Critchley wrote:
>> Sure, I would love the source. While I have trouble with C strings -
>> mainly from being rusty - nine years since I last coded C, I have been
>> able to work enough C to redo the setportfw.c program and several
>> other programs.

>I'm sorry if I came off sounding high and mighty.  I didn't mean to
>imply that you couldn't code C.
You never came across as high and mighty, the thougt never crossed my mind.
Sometimes emails lose the sentinment or send a message they shouldn't. I
wasn't upset at all.

>> If you need help with interfaces, etc I can help you - while not  a
>> perl expert, I can hold my own and have already accomplished quite a
>> few major improvements to the interface.
>

>That's cool.  I'd love to have that opportunity.  I've attached the
>tarball, you can use any way you see fit.  You might even be able to get
>it into IPCop.  If you have any questions about the way I did things let
>me know.

Thanks, when time permits - probably this weekend, I will have a look and
see what we can do.

We actually don't need to use SSH to restore the settings - the dev team has
already shown us how to upload a file onto Ipcop using the gui interface -
we can do the same for a restore. You already have the download side, so all
we really need is someway of figuring out how to get it onto a floppy in the
correct format, or live with having to install a vanilla ipcop and then
upload the recovery file.

What I would really like to see is a backup that allows you to select
items - sometimes it would be nice to backup everything but the network
card. In a couple of cases I have seen an ethernet card die and be replaced
with another brand - Ipcop doesn't like this and trying to recover from it -
well you might as well re-install. If you had a backup with everything but
the ethernet cards in it, that would be nice.


Anyways, thanks, and I will be in touch.
Darren

>Can you go into more detail as to what a tariffing scrip does? I don't
>believe I am familiar with the terminology.

Okay, may be I've found a wrong word in a dictionary. In a few words: it's
a convenient tool for those who pay on per-MB basis and need to distribute
ISP's bill over several clients.

Details are the following:

By default, IpCop only accounts incoming/outgoing data for
every interface (and draws some nice graphs). But what I need is
something more: I need per-client accounting and not only in MBytes
but in USDs (or other currency). So I wrote the script I've called
"tarriffing".

Features are the following:
* You may set different prices for different kind of sites (for example,
several subnets of my ISP are free, traffic from proxy server is 2.69
RUR/Mb and other kinds of traffic are 2.99RUR/Mb)

* You may explore different time periods (eg. 02/01/03 - 02/01/28,
01/01/02 - 12/31/02 and so on).

Similar functionality is provided by ipac-ng package which is
scheduled to IpCop 1.4 if I'm not mistaken

Regards,
Valentine

Hello all,

I need to modify IPCop to accept two red interfaces, one inbound and one
outbound and I am wondering where I should start looking. Has anyone made
any changes along these lines? Does anyone have any suggestions on where to
start?


Regards,


Stephen.
x 5125




-------------------------------------------------------------------------------------------

Copyright material and/or confidential and/or privileged information may be contained in this e-mail and any attached documents.  The material and information is intended for the use of the intended addressee only.  If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you may not copy, disclose, distribute, disseminate or deliver it to anyone else or use it in any unauthorised manner or take or omit to take any action in reliance on it. To do so is prohibited and may be unlawful.   The views expressed in this e-mail may not be official policy but the personal views of the originator.  If you receive this e-mail in error, please advise the sender immediately by using the reply facility in your e-mail software, or contact pos...@bm....  Please also delete this e-mail and all documents attached immediately.  
Many thanks for your co-operation.

BMW Financial Services (GB) Limited is registered in England and Wales under company number 01288537.
Registered Offices : Europa House, Bartley Way, Hook, Hants, RG27 9UF
------------------------------------------------------------------------------------------

Can you go into more detail as to what a tariffing scrip does? I don't
believe I am familiar with the terminology.

Thanks!
Sam

-----Original Message-----
From: ipc...@li...
[mailto:ipc...@li...]On Behalf Of Sinitsyn
Valentine
Sent: Friday, February 28, 2003 6:12 AM
To: ipc...@li...
Subject: [IPCop-devel] Tariffing


Hi to all,

I've made a simple tariffing package for IpCop 1.2 (a cgi script which
runs on the top of ipacsum). As it is required by GPL, I'll provide the
complete source code for anyone willing to use or modify it. If you
are interested in, please write me a letter.

Regards,
Valentine



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
IPCop-devel mailing list
IPC...@li...
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

Hi to all,

I've made a simple tariffing package for IpCop 1.2 (a cgi script which
runs on the top of ipacsum). As it is required by GPL, I'll provide the
complete source code for anyone willing to use or modify it. If you
are interested in, please write me a letter.

Regards,
Valentine

Have you looked at the Road Map?
http://www.ipcop.org/cgi-bin/twiki/view/IPCop/RoadMap

Or are you looking for something more specific-- like
http://developer.postgresql.org/todo.php ?

Sam

-----Original Message-----
From: ipc...@li...
[mailto:ipc...@li...]On Behalf Of Jason Louie
Sent: Thursday, February 27, 2003 10:43 PM
To: ipc...@li...
Subject: Re: [IPCop-devel] Bug: Port-forwarding


	I think might have misinterpreted my point.  I was suggesting having a
list on the web-site that has a simple list of things that are being
worked on or added to the next version.  See I wasn't quite sure if my
question has been asked before.  A simple list that is easy to get to
would be sufficient.  BTW I am by far not asking to have a current
version in iso downloadable every other day.  Just a list.  ;P

Jason

Arnt Karlsen wrote:
><snip>

	I think might have misinterpreted my point.  I was suggesting having a
list on the web-site that has a simple list of things that are being
worked on or added to the next version.  See I wasn't quite sure if my
question has been asked before.  A simple list that is easy to get to
would be sufficient.  BTW I am by far not asking to have a current
version in iso downloadable every other day.  Just a list.  ;P

Jason

Arnt Karlsen wrote:
> 
> On Thu, 27 Feb 2003 08:56:41 -0800,
> Darren Critchley <da...@kd...> wrote in message
> <003d01c2de81$33981eb0$0a0a10ac@darrenc>:
> 
> >
> > ----- Original Message -----
> > From: "Arnt Karlsen" <ar...@c2...>
> > To: <ipc...@li...>
> > Sent: Thursday, February 27, 2003 4:09 AM
> > Subject: Re: [IPCop-devel] Bug: Port-forwarding
> >
> >
> > > > > ..url's, to speed up testing?  ;-)
> > > > Usual place you find a CVS.
> > >
> > > ..and Jason knows?  ;-)
> > From the main Ipcop website, go to latest cvs link (the bottom one I
> > think)
> >
> > >
> > > > You will have to wait for Mark to release an ISO if you don't
> > > > compile your own.
> > >
> > > ..sounds like a worthy cron job candidate.  I have a few boxes
> > > available at a clients site, I need 802.11 and pcmcia support,
> > > at least "in progress", to warrant using one of my clients boxes
> > > for this.  His current mirror has Red Hat 7.3 and 8.0, I'd like
> > > to stop there, and go straight for the LSF-based 1.4x, possibly
> > > making a "late" 1.3 based on RH-7.3.  Further, the cron job
> > > should log to a file and put that and the iso online, takers
> > > on the script mod?
> >
> > That would be a really bad idea, it would generate a new ISO every
> > day, would be a support nightmare for the developers. Sometimes the
> > code in the CVS is broken - I recompile every couple of days,
> > depending on what is added - serveral times this month, I have had a
> > version that didn't run, or didn't install. It was usually fixed
> > within a day, but if something like that got out to the users, they
> > would be pretty upset, which is why when the code reaches a certain
> > stability, that an ISO is realeased.
> 
> ..we disagree.  First, much of the testing can be automated.
> Second, "We wanna know _how_ it crashed, so we can fix it.".
> Third, this is a project for _volonteers_.  Fourth, "If you
> need something fixed, fix it, or pay someone to fix it.".
> Fifth, few users have both the skills and time and drive etc
> to compile their own iso.  Sixth, iso compilation crashes are
> largely irrelevant for ipcop users, they just want ipcop working
> good.  Seventh, lack of user feed back, _slows_ development.
> 
> > Now it looks like we may have a small wait as Mark has a new family
> > member to contend with - however, I have seen from the list that he
> > has snuck a couple of fixes into the CVS so we haven't totally lost
> > him.
> >
> > Darren
> 
> ..Mark and his wife might appreciate easing the tow load on Mark.
> 
> --
> ..med vennlig hilsen = with Kind Regards from Arnt... ;-)
> ...with a number of polar bear hunters in his ancestry...
>   Scenarios always come in sets of three:
>   best case, worst case, and just in case.
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel

On Thu, 27 Feb 2003 21:34:01 +0000, 
Eric Oberlander <er...@ob...> wrote in message 
<BA8434C7.314A%er...@ob...>:

> Hi Darren
> 
> on 27/2/03 6:29 pm, Darren Critchley at da...@kd... wrote:
> 
> I ran it for a while, but it didn't like my dial up connection (or
> rather, I couldn't configure it properly) It's the risk vs utility
> equation. Without it, it's one less thing to worry about. But I'd
> still find it useful myself, as IPCop is the only server running
> non-stop on my (rather small) network.
> 

..on dial up time servers:  at least for isdn, the 16 kb or so 
"D-channel" can be accessed for free, and is used for control 
of the 2 "B-channels", my isdn telephone-with-integral-modem 
reads network time off the D-channel according to the manual, 
but only after a call.  ;-)

..is this a viable option for a time service source for the 
dialup people?

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

On Thu, 27 Feb 2003 08:56:41 -0800, 
Darren Critchley <da...@kd...> wrote in message 
<003d01c2de81$33981eb0$0a0a10ac@darrenc>:

> 
> ----- Original Message -----
> From: "Arnt Karlsen" <ar...@c2...>
> To: <ipc...@li...>
> Sent: Thursday, February 27, 2003 4:09 AM
> Subject: Re: [IPCop-devel] Bug: Port-forwarding
> 
> 
> > > > ..url's, to speed up testing?  ;-)
> > > Usual place you find a CVS.
> >
> > ..and Jason knows?  ;-)
> From the main Ipcop website, go to latest cvs link (the bottom one I
> think)
> 
> >
> > > You will have to wait for Mark to release an ISO if you don't
> > > compile your own.
> >
> > ..sounds like a worthy cron job candidate.  I have a few boxes
> > available at a clients site, I need 802.11 and pcmcia support,
> > at least "in progress", to warrant using one of my clients boxes
> > for this.  His current mirror has Red Hat 7.3 and 8.0, I'd like
> > to stop there, and go straight for the LSF-based 1.4x, possibly
> > making a "late" 1.3 based on RH-7.3.  Further, the cron job
> > should log to a file and put that and the iso online, takers
> > on the script mod?
> 
> That would be a really bad idea, it would generate a new ISO every
> day, would be a support nightmare for the developers. Sometimes the
> code in the CVS is broken - I recompile every couple of days,
> depending on what is added - serveral times this month, I have had a
> version that didn't run, or didn't install. It was usually fixed
> within a day, but if something like that got out to the users, they
> would be pretty upset, which is why when the code reaches a certain
> stability, that an ISO is realeased.

..we disagree.  First, much of the testing can be automated. 
Second, "We wanna know _how_ it crashed, so we can fix it.".  
Third, this is a project for _volonteers_.  Fourth, "If you 
need something fixed, fix it, or pay someone to fix it.".
Fifth, few users have both the skills and time and drive etc 
to compile their own iso.  Sixth, iso compilation crashes are 
largely irrelevant for ipcop users, they just want ipcop working 
good.  Seventh, lack of user feed back, _slows_ development. 


> Now it looks like we may have a small wait as Mark has a new family
> member to contend with - however, I have seen from the list that he
> has snuck a couple of fixes into the CVS so we haven't totally lost
> him.
> 
> Darren

..Mark and his wife might appreciate easing the tow load on Mark.


-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

Hi Darren

on 27/2/03 6:29 pm, Darren Critchley at da...@kd... wrote:

> I did not know anyone was working on the time piece.

I was just 'improving' the layout of the page, moving the server fields into
the 'server' box.

> I adjusted my time page to allow one to turn the ntpd server on and off. I
> added ntpd back in from the rpm, and now other computers on the green only
> can set their time to match the ipcop time. This is handy when you have a
> bunch of servers on the green or orange and you want to keep the logs in
> sync. I also added an entry on the status page for it as well.
> 
> Are you interested in the code?
> 
> Darren

The decision to include ntpd would be one for the lead developers. A long
time ago I think it was planned for a later release, and there's been a lot
of discussion about it in the past. Those that need it have tended to add it
into IPCop, like yourself, (ie see MultiThread's instructions at
http://www.multithread.co.uk/ipcop/ and various threads on the
http://ipcop.hopto.org site).

I ran it for a while, but it didn't like my dial up connection (or rather, I
couldn't configure it properly) It's the risk vs utility equation. Without
it, it's one less thing to worry about. But I'd still find it useful myself,
as IPCop is the only server running non-stop on my (rather small) network.

I'm sure there are others that will be interested in your code. If it
doesn't make it into the official iso, perhaps it would be a good one for
Gavin's Add-Onz system?

Eric

I did not know anyone was working on the time piece.
I adjusted my time page to allow one to turn the ntpd server on and off. I
added ntpd back in from the rpm, and now other computers on the green only
can set their time to match the ipcop time. This is handy when you have a
bunch of servers on the green or orange and you want to keep the logs in
sync. I also added an entry on the status page for it as well.

Are you interested in the code?

Darren

  ----- Original Message -----
  From: Eric Oberlander
  To: ipc...@li...
  Sent: Thursday, February 27, 2003 10:21 AM
  Subject: [IPCop-cvs] CVS: ipcop/html/cgi-bin time.cgi,1.1.2.4,1.1.2.5


  Update of /cvsroot/ipcop/ipcop/html/cgi-bin
  In directory sc8-pr-cvs1:/tmp/cvs-serv17369/ipcop/html/cgi-bin

  Modified Files:
        Tag: IPCOP_v1
  time.cgi
  Log Message:
  Rearrange web interface

  Index: time.cgi
  ===================================================================
  RCS file: /cvsroot/ipcop/ipcop/html/cgi-bin/Attic/time.cgi,v
  retrieving revision 1.1.2.4
  retrieving revision 1.1.2.5
  diff -C2 -d -r1.1.2.4 -r1.1.2.5
  *** time.cgi 10 Oct 2002 21:46:38 -0000 1.1.2.4
  --- time.cgi 27 Feb 2003 18:21:08 -0000 1.1.2.5
  ***************
  *** 9,13 ****
    # (c) Eric Oberlander June 2002
    #
  ! # /home/httpd/cgi-bin/time.cgi for IPCop 0.1.2

    require 'CONFIG_ROOT/header.pl';
  --- 9,13 ----
    # (c) Eric Oberlander June 2002
    #
  ! # /home/httpd/cgi-bin/time.cgi for IPCop 1.3

    require 'CONFIG_ROOT/header.pl';
  ***************
  *** 111,115 ****
    {
    unlink "${swroot}/time/enable";
  ! unlink "${swroot}/time/settimenow"; # added to v0.0.4
    &log($tr{'ntp syncro disabled'})
    }
  --- 111,115 ----
    {
    unlink "${swroot}/time/enable";
  ! unlink "${swroot}/time/settimenow";
    &log($tr{'ntp syncro disabled'})
    }
  ***************
  *** 165,170 ****
    <TABLE WIDTH='100%'>
    <TR>
  !    <TD WIDTH='25%' CLASS='base'>$tr{'enabled'} &nbsp; <INPUT
TYPE='checkbox' NAME='ENABLENTP' $checked{'ENABLENTP'}{'on'}></TD>
  ! <TD WIDTH='75%' CLASS='base'>
    END
    ;
  --- 165,170 ----
    <TABLE WIDTH='100%'>
    <TR>
  ! <TD WIDTH='25%' CLASS='base'>$tr{'enabled'} &nbsp; <INPUT
TYPE='checkbox' NAME='ENABLENTP' $checked{'ENABLENTP'}{'on'}></TD>
  ! <TD WIDTH='75%' COLSPAN='3' CLASS='base'>
    END
    ;
  ***************
  *** 181,186 ****

    print <<END
  ! </TD></TR>
    </TABLE>
    END
    ;
  --- 181,195 ----

    print <<END
  ! </TR>
  ! <TR>
  ! <TD CLASS='base'>$tr{'primary ntp server'}:</TD>
  ! <TD><INPUT TYPE='text' NAME='NTP_ADDR_1'
VALUE='$timesettings{'NTP_ADDR_1'}'></TD>
  ! <TD CLASS='base'>$tr{'secondary ntp server'}: &nbsp;<IMG SRC='/blob.gif'
VALIGN='top'></TD>
  ! <TD><INPUT TYPE='text' NAME='NTP_ADDR_2'
VALUE='$timesettings{'NTP_ADDR_2'}'></TD>
  ! </TR>
    </TABLE>
  + <BR>
  + <IMG SRC='/blob.gif' VALIGN='top'>&nbsp;
  + <FONT CLASS='base'>$tr{'this field may be blank'}</FONT>
    END
    ;
  ***************
  *** 191,217 ****
    <TABLE WIDTH='100%'>
    <TR>
  ! <TD WIDTH='25%' CLASS='base'><INPUT TYPE='radio' NAME='UPDATE_METHOD'
VALUE='manually' $checked{'UPDATE_METHOD'}{'manually'}>$tr{'manually'}:</TD>
  ! <TD WIDTH='25%'> &nbsp; </TD>
  ! <TD WIDTH='25%'> &nbsp; </TD>
    <TD WIDTH='25%'> &nbsp; </TD>
    </TR>
    <TR>
    <TD CLASS='base'><INPUT TYPE='radio' NAME='UPDATE_METHOD'
VALUE='periodically'
$checked{'UPDATE_METHOD'}{'periodically'}>$tr{'every'}:</TD>
  ! <TD><INPUT TYPE='text' NAME='UPDATE_VALUE'
VALUE='$timesettings{'UPDATE_VALUE'}'></TD>
  ! <TD>
    <SELECT NAME='UPDATE_PERIOD'>
  !         <OPTION VALUE='hourly'
$selected{'UPDATE_PERIOD'}{'hourly'}>$tr{'hours'}
  !         <OPTION VALUE='daily'
$selected{'UPDATE_PERIOD'}{'daily'}>$tr{'days'}
  !         <OPTION VALUE='weekly'
$selected{'UPDATE_PERIOD'}{'weekly'}>$tr{'weeks'}
  !        <OPTION VALUE='monthly'
$selected{'UPDATE_PERIOD'}{'monthly'}>$tr{'months'}
  !        </SELECT></TD>
  ! </TR>
  ! <TR>
  ! <TD CLASS='base'>$tr{'primary ntp server'}:</TD>
  ! <TD><INPUT TYPE='text' NAME='NTP_ADDR_1'
VALUE='$timesettings{'NTP_ADDR_1'}'></TD>
  ! <TD CLASS='base'>$tr{'secondary ntp server'}: &nbsp;<IMG SRC='/blob.gif'
VALIGN='top'></TD>
  ! <TD><INPUT TYPE='text' NAME='NTP_ADDR_2'
VALUE='$timesettings{'NTP_ADDR_2'}'></TD>
    </TR>
  -
    <TR>
    <TD ALIGN='CENTER'><INPUT TYPE='submit' NAME='ACTION' VALUE='$tr{'set
time now'}'></TD>
  --- 200,217 ----
    <TABLE WIDTH='100%'>
    <TR>
  ! <TD WIDTH='25%' CLASS='base'><INPUT TYPE='radio' NAME='UPDATE_METHOD'
VALUE='manually' $checked{'UPDATE_METHOD'}{'manually'}>$tr{'manually'}</TD>
  ! <TD WIDTH='50%'> &nbsp; </TD>
    <TD WIDTH='25%'> &nbsp; </TD>
    </TR>
    <TR>
    <TD CLASS='base'><INPUT TYPE='radio' NAME='UPDATE_METHOD'
VALUE='periodically'
$checked{'UPDATE_METHOD'}{'periodically'}>$tr{'every'}:</TD>
  ! <TD><INPUT TYPE='text' NAME='UPDATE_VALUE'
VALUE='$timesettings{'UPDATE_VALUE'}'>
    <SELECT NAME='UPDATE_PERIOD'>
  ! <OPTION VALUE='hourly' $selected{'UPDATE_PERIOD'}{'hourly'}>$tr{'hours'}
  ! <OPTION VALUE='daily' $selected{'UPDATE_PERIOD'}{'daily'}>$tr{'days'}
  ! <OPTION VALUE='weekly' $selected{'UPDATE_PERIOD'}{'weekly'}>$tr{'weeks'}
  ! <OPTION VALUE='monthly'
$selected{'UPDATE_PERIOD'}{'monthly'}>$tr{'months'}
  ! </SELECT></TD>
    </TR>
    <TR>
    <TD ALIGN='CENTER'><INPUT TYPE='submit' NAME='ACTION' VALUE='$tr{'set
time now'}'></TD>
  ***************
  *** 220,226 ****
    ;

  - # added to v0.0.4
    if ( -e "${swroot}/time/settimenow") {
  ! print "<FONT COLOR='RED'>$tr{'waiting to synchronize
clock'}</FONT></TD><TD><IMG SRC='/images/clock.gif'>\n";
    }

  --- 220,225 ----
    ;

    if ( -e "${swroot}/time/settimenow") {
  ! print "<FONT COLOR='RED'>$tr{'waiting to synchronize
clock'}...</FONT></TD><TD><IMG SRC='/images/clock.gif'>\n";
    }

  ***************
  *** 229,235 ****
    </TR>
    </TABLE>
  - <BR>
  - <IMG SRC='/blob.gif' VALIGN='top'>&nbsp;
  - <FONT CLASS='base'>$tr{'this field may be blank'}</FONT>
    END
    ;
  --- 228,231 ----



  -------------------------------------------------------
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  _______________________________________________
  IPCop-cvs mailing list
  IPC...@li...
  https://lists.sourceforge.net/lists/listinfo/ipcop-cvs

----- Original Message -----
From: "Arnt Karlsen" <ar...@c2...>
To: <ipc...@li...>
Sent: Thursday, February 27, 2003 4:09 AM
Subject: Re: [IPCop-devel] Bug: Port-forwarding


> > > ..url's, to speed up testing?  ;-)
> > Usual place you find a CVS.
>
> ..and Jason knows?  ;-)
From the main Ipcop website, go to latest cvs link (the bottom one I think)

>
> > You will have to wait for Mark to release an ISO if you don't compile
> > your own.
>
> ..sounds like a worthy cron job candidate.  I have a few boxes
> available at a clients site, I need 802.11 and pcmcia support,
> at least "in progress", to warrant using one of my clients boxes
> for this.  His current mirror has Red Hat 7.3 and 8.0, I'd like
> to stop there, and go straight for the LSF-based 1.4x, possibly
> making a "late" 1.3 based on RH-7.3.  Further, the cron job
> should log to a file and put that and the iso online, takers
> on the script mod?

That would be a really bad idea, it would generate a new ISO every day,
would be a support nightmare for the developers. Sometimes the code in the
CVS is broken - I recompile every couple of days, depending on what is
added - serveral times this month, I have had a version that didn't run, or
didn't install. It was usually fixed within a day, but if something like
that got out to the users, they would be pretty upset, which is why when the
code reaches a certain stability, that an ISO is realeased.

Now it looks like we may have a small wait as Mark has a new family member
to contend with - however, I have seen from the list that he has snuck a
couple of fixes into the CVS so we haven't totally lost him.

Darren

Correction=20
Le cot=E9 gauche  d'IPCOP (vers le modem ADSL)  correspond =E0 la zone =
RED.
C'est =E0 dire la zone de l'ext=E9rieur.
Le cot=E9 droit d'IPCOP (vers le switch) correspond  =E0 la zone GREEN =
que tu
souhaites prot=E9ger. L'interieur ou reseau personnel.

=20
 -----Original Message-----
From: Stephane [mailto:sfr...@ch...]
Sent: Tuesday, February 25, 2003 8:00 AM
To: Julien COTTET; ipc...@li...
Subject: Re: [IPCop-devel] (no subject)



Salut,

Si j'ai bien tout compris tu as :

Internet ---- modem ADSL ----- PC ----- Switch ---- IPCOP

C'est pas le mieux pour installer un firewall !!

Tu devrais avoir quelque chose comme ca :

Internet --- modem ADSL ------- IPCOP ---- SWITCH ----- PC

Le cot=E9 droit d'IPCOP (vers le switch) correspond =E0 la zone RED. =
C'est =E0
dire la zone que tu souhaites prot=E9ger de l'ext=E9rieur
Le cot=E9 gauche d'IPCOP (vers le modem) correspond ) =E0 la zone =
GREEN. C'est =E0
dire la zone que tu souhaites pouvoir joindre.

Cordialement

St=E9phane

Julien COTTET a =E9crit:


Bonjour,
=20
Un petit souci qui me prend la tete depuis hier soir: quel type de =
r=E9seau
d=E9clarer dans IP Cop ?
=20
Je pr=E9sente brievement mon installation : une carte Eden o=F9 est =
install=E9 IP
Cop, un switch et le PC que j'utilise actuellement pour prendre des
informations via mon modem ADSL (la raie manta verte alias Speed Touch =
USB).
=20
Je suis un peu perdu dans la diff=E9renciation Green et Green + Red.
=20
Merci pour le temps pris =E0 l'=E9coute de mon probl=E8me.
=20
Cordialement
=20
Julien COTTET


------------------------------------------------------- This SF.net =
email is
sponsored by: Scholarships for Techies! Can't afford IT training? All =
2003
ictp students receive scholarships. Get hands-on training in Microsoft,
Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp
_______________________________________________ IPCop-devel mailing =
list
IPC...@li...
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

On Wed, 26 Feb 2003 18:17:08 -0800, 
Darren Critchley <da...@kd...> wrote in message 
<000901c2de06$54cfcdb0$0a0a10ac@darrenc>:

> ----- Original Message -----
> From: "Arnt Karlsen" <ar...@c2...>
> To: <ipc...@li...>
> Sent: Wednesday, February 26, 2003 5:00 PM
> Subject: Re: [IPCop-devel] Bug: Port-forwarding
> 
> 
> > On Wed, 26 Feb 2003 15:22:46 -0800,
> > Darren Critchley <da...@kd...> wrote in message
> > <016501c2dded$f8dbb090$0a0a10ac@darrenc>:
> >
> > > There is a bug list at the ipcop sourceforge site - unfortunately
> > > it is difficult to find, and I haven't seen a link from the Ipcop
> > > main site to it.
> >
> > ..<snip>.
> >
> > > So hold tight for the next alpha release, and you can see how it
> > > stacks up for us.
> >
> > ..url's, to speed up testing?  ;-)
> Usual place you find a CVS.

..and Jason knows?  ;-)
 
> You will have to wait for Mark to release an ISO if you don't compile
> your own.

..sounds like a worthy cron job candidate.  I have a few boxes
available at a clients site, I need 802.11 and pcmcia support, 
at least "in progress", to warrant using one of my clients boxes 
for this.  His current mirror has Red Hat 7.3 and 8.0, I'd like 
to stop there, and go straight for the LSF-based 1.4x, possibly 
making a "late" 1.3 based on RH-7.3.  Further, the cron job 
should log to a file and put that and the iso online, takers 
on the script mod?

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

----- Original Message -----
From: "Arnt Karlsen" <ar...@c2...>
To: <ipc...@li...>
Sent: Wednesday, February 26, 2003 5:00 PM
Subject: Re: [IPCop-devel] Bug: Port-forwarding


> On Wed, 26 Feb 2003 15:22:46 -0800,
> Darren Critchley <da...@kd...> wrote in message
> <016501c2dded$f8dbb090$0a0a10ac@darrenc>:
>
> > There is a bug list at the ipcop sourceforge site - unfortunately it
> > is difficult to find, and I haven't seen a link from the Ipcop main
> > site to it.
>
> ..<snip>.
>
> > So hold tight for the next alpha release, and you can see how it
> > stacks up for us.
>
> ..url's, to speed up testing?  ;-)
Usual place you find a CVS.

You will have to wait for Mark to release an ISO if you don't compile your
own.

Darren

On Wed, 26 Feb 2003 15:22:46 -0800, 
Darren Critchley <da...@kd...> wrote in message 
<016501c2dded$f8dbb090$0a0a10ac@darrenc>:

> There is a bug list at the ipcop sourceforge site - unfortunately it
> is difficult to find, and I haven't seen a link from the Ipcop main
> site to it.

..<snip>.
 
> So hold tight for the next alpha release, and you can see how it
> stacks up for us.

..url's, to speed up testing?  ;-)

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

----- Original Message -----
From: "Jason Louie" <jas...@sh...>
To: "ipcop-devel" <ipc...@li...>
Sent: Wednesday, February 26, 2003 3:10 PM
Subject: [IPCop-devel] Bug: Port-forwarding


> I've installed various Routing software over the last year and have
> been using IPCop for the last month.  I like the interface and the
> simple installation onto my system.
>
> However, after saying this I have had problems with forwarding port
> 6112 so that my son can play Starcraft without excessive lags during the
> game.  I have had the same problem with Coyote Linux also which was the
> reason I have switched.  I have since installed SmoothWall 2.0-Mallard
> beta for curiosity sake and found that this problem was not there.  I
> would still like to continue using and supporting IPCop since SmoothWall
> will be moving to a non-GPL product, (to what I've heard, correct me if
> I'm wrong.)
>
> In closing I would like to add some a suggestion.  To help people
> understand what is being fixed or added to IPCop, a list might be
> available.  This prevents asking the same questions over and over again,
> (I'm not sure if my bug has been brought up before.)
>
There is a bug list at the ipcop sourceforge site - unfortunately it is
difficult to find, and I haven't seen a link from the Ipcop main site to it.

Now, comparing Ipcop 1.2 to Smoothwall 2.0 Mallard isn't entirely fair -
Ipcop is a 2.2 kernel using ipchains, while Smoothie 2.0 is a 2.4 kernel
using iptables.
Iptables is far superior to ipchains.

So that being said, the 2.4 kernel for Ipcop with Iptables is in Alpha
testing, with hopefully in the next week or two another alpha being
released. I have just completed the second phase of the Port Forwarding page
which was Port ranges, so gamers and other people that use MS products will
be happy to know that a whole range of ports can now be forwarded to a
machine behind Ipcop, instead of opening one port at at time or dropping to
the command line and doing it manually.

So hold tight for the next alpha release, and you can see how it stacks up
for us.

Darren

	I've installed various Routing software over the last year and have
been using IPCop for the last month.  I like the interface and the
simple installation onto my system.

	However, after saying this I have had problems with forwarding port
6112 so that my son can play Starcraft without excessive lags during the
game.  I have had the same problem with Coyote Linux also which was the
reason I have switched.  I have since installed SmoothWall 2.0-Mallard
beta for curiosity sake and found that this problem was not there.  I
would still like to continue using and supporting IPCop since SmoothWall
will be moving to a non-GPL product, (to what I've heard, correct me if
I'm wrong.)

	In closing I would like to add some a suggestion.  To help people
understand what is being fixed or added to IPCop, a list might be
available.  This prevents asking the same questions over and over again,
(I'm not sure if my bug has been brought up before.)

	Just adding my $0.02.

Jason

Congratulations.

Your best bit of coding yet !!!

All the best to the family.

Marco van Beek
Supporting Role Ltd.

Hi,

I'll be a bit busy the next couple of weeks, but I will find some time
to continue work on 1.3.

Why I'm so busy?  Just check out http://www.wormgoor.com/rosanne/.
She came 2,5 weeks early, so it was a bit unexpected.

Kind regards,

Mark Wormgoor
-- 
***************************************************************
* |\    /|      |  /|  /       Mark Wormgoor                  *
* | \  / |      | / | /        mailto:ma...@wo...       *
* |  \/  |ark   |/  |/ormgoor  http://www.wormgoor.com/mark/  *
***************************************************************

On Wednesday 26 February 2003 03:00, Darren Critchley wrote:
[snip]
> Again thanks to all the replies, Val and Steve were the closest, but it
> seems that *ctr = ":"; is illegal, you need to set it with the ascii value
> of the colon.
[snip]

as was previously pointed out before by steve, is that you needed to be using 
single quotes ( ' ) not double quotes ( " ). when the compiler reads a 
character inside these single quotes, it replaces the character with it's 
ascii code (in this case 58) and carries on. The lines you needed was:

<BEGIN CODE BLOCK>
char *ctr;

[insert your ipcop code here]

ctr = strchr(remport, '-');

if (ctr != NUll)
{
	*ctr = ':';
}
<END CODE BLOCK>

This does away with messy defines (I don't like defines unless you're using 
the value over and over again).

Right, that's the complete extent to my C knowledge :-p I just wanted to sound 
all knowledgable for once.

-- 
Regards,
	Daniel "Fremen" Llewellyn

> In the end, the following solution worked (for those that are interested)
> 
> #DEFINE COLON 58
> #DEFINE DASH 45
> 
> char *ctr
> 
> lots of ipcop code here
> 
>  ctr = strchr(remport, DASH);
> 
>  if (ctr != NULL)
> {
>     *ctr = COLON;
> }
> 
> That did it - the better part of my day was wasted on three lines of code, I
> hate days like that.  And I must say - string manipulation in C is very
> painful.
> 
> Well tomorrow the new port forwarding continues - now that the setportfw can
> port forward ranges, I need to make the gui allow people to enter ranges.
> 
> Again thanks to all the replies, Val and Steve were the closest, but it
> seems that *ctr = ":"; is illegal, you need to set it with the ascii value
> of the colon.

Sure. ":" is string in C syntax (like "IpCop"), because you use double
quotes, and it does not matter whether there is an only char in this
string or not. If one use *ctr = ':' (pay attention to single quotes),
everything sholud be ok (and it is the same as yours '*ctr = 58',
because chars in singe quots are just converted by a compiler into
their ascii values)

Regards,
Valentine