ipcop-devel Mailing List for IPCop Firewall

I've installed IPCop version 1.3Alpha ona test machine (p200 64mb RAM =
800mb HDD) with a USB2.0 card. On configuration I have to manually =
select EHCI on the IPCop setup screen, after that nothing happens on the =
speedtouch modem connected to it. No power or anything (IE no =
green/orange light up and flash). I have verified that the USB2.0 card =
is not faulty by putting it in my win2k box and installing the drivers =
for it; the modem is connected to that, and everything proceeds to be =
detected and installed with the green/orange lights flashing etc. I'm =
not sure if it could be the power supply unit up to scratch as i beleive =
in the p200 box its a 150Watt PSU.

Does anyone else have a USB2.0 card with IPCop 1.3Alpha installed and =
working with a speedtouch modem?

Many thanks,

James Read

Hi,

> > > I was just wondering, there seems to be no external access page on this
> > > revision, is it being worked on, or has it been dropped?
> > For now, it was dropped.  External access as it existed in the 2.2 kernel
> > no longer exists.  You can either allow access on a connection to the
> > firewall (INPUT chain) or on a forwarded connection (FORWARD chain).  For
> > the forward chain, you need to know the final destination.
> >
> > I solved this by allowing access from the entire internet to the forwarded
> > port.  I think only a few users used the options for limiting forwarded
> > ports based on ip addresses.
> 
> Unfortunately I was one of them. Is this because of the iptables instead of
> ipchains, or can we still restrict by ip address using iptables.

We can still restrict by ip address.  However, the location needs to move 
from the external access page to the port forwarding page to make clear 
what it does.  What I'm not sure about:
- how do we handle the conversion?
- do we need an external access page for incoming connections ?
- who wants to take a look at integrating externall access into the port 
  forwarding page ?

> > > Also, is the h323 patch compiled into the kernel? I have an ip phone
> > > that uses that protocol, which works ok for the most part behind ipcop
> > > pre4f (I have to reboot sometimes as it stops working), but with 1.3, I
> > > can dial out to my office, but the signal is dropped when the other end
> > > answers.
> > The patch is not compiled in.  I am having problems with the kernel patch.
> >  However, 2.4.20 just came out today, so I'm going to give that a try
> > instead.  Will try for an alpha2 release based on 2.4.20 this weekend.
> 
> Looking forward to testing it.

Just played around with 2.4.20.  I have succesfully compiled in the h323 
masquerading now.  Turned out it was a little disagreement between me and 
the netfilter kernel patch-o-matic.

Kind regards,

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

On Fri, 29 Nov 2002, Mark Wormgoor wrote:

> For now, it was dropped.  External access as it existed in the 2.2 kernel
> no longer exists.  You can either allow access on a connection to the
> firewall (INPUT chain) or on a forwarded connection (FORWARD chain).  For
> the forward chain, you need to know the final destination.
> 
> I solved this by allowing access from the entire internet to the forwarded
> port.  I think only a few users used the options for limiting forwarded
> ports based on ip addresses.

FWIW, It seems to me that the ability to restrict access on inbound
connections to the protected networks is a pretty fundamental capability
for a firewall. Its certainly something that I use on my IPcop at home 
(and the commercial firewalls at work for that matter).


Joe Matuscak
Rohrer Corporation
717 Seville Road
Wadsworth, Ohio 44281
(330)335-1541
mat...@ro...

----- Original Message -----
From: "Mark Wormgoor" <ma...@wo...>
To: <ipc...@li...>
Sent: Friday, November 29, 2002 2:28 AM
Subject: Re: [IPCop-devel] 1.3 Alpha


> Hi,
>
> > I was just wondering, there seems to be no external access page on this
> > revision, is it being worked on, or has it been dropped?
> For now, it was dropped.  External access as it existed in the 2.2 kernel
> no longer exists.  You can either allow access on a connection to the
> firewall (INPUT chain) or on a forwarded connection (FORWARD chain).  For
> the forward chain, you need to know the final destination.
>
> I solved this by allowing access from the entire internet to the forwarded
> port.  I think only a few users used the options for limiting forwarded
> ports based on ip addresses.

Unfortunately I was one of them. Is this because of the iptables instead of
ipchains, or can we still restrict by ip address using iptables.

>
> Second, I allowed access to 113 (ident), but there's nothing listening on
> that port.  The reason is that a lot of servers (ftp/irc) check ident
> before allowing access.  A closed port gives a quicker denial than a
> denied port.
>

Ok.

> > Also, is the h323 patch compiled into the kernel? I have an ip phone
> > that uses that protocol, which works ok for the most part behind ipcop
> > pre4f (I have to reboot sometimes as it stops working), but with 1.3, I
> > can dial out to my office, but the signal is dropped when the other end
> > answers.
> The patch is not compiled in.  I am having problems with the kernel patch.
>  However, 2.4.20 just came out today, so I'm going to give that a try
> instead.  Will try for an alpha2 release based on 2.4.20 this weekend.

Looking forward to testing it.

>
> Kind regards,
>
> Mark Wormgoor
> --
> ***************************************************************
> * |\    /|      |  /|  /       Mark Wormgoor                  *
> * | \  / |      | / | /        mailto:ma...@wo...       *
> * |  \/  |ark   |/  |/ormgoor  http://www.wormgoor.com/mark/  *
> ***************************************************************
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>
>

Hi,

> I was just wondering, there seems to be no external access page on this
> revision, is it being worked on, or has it been dropped?
For now, it was dropped.  External access as it existed in the 2.2 kernel
no longer exists.  You can either allow access on a connection to the
firewall (INPUT chain) or on a forwarded connection (FORWARD chain).  For
the forward chain, you need to know the final destination.

I solved this by allowing access from the entire internet to the forwarded
port.  I think only a few users used the options for limiting forwarded
ports based on ip addresses.

Second, I allowed access to 113 (ident), but there's nothing listening on
that port.  The reason is that a lot of servers (ftp/irc) check ident
before allowing access.  A closed port gives a quicker denial than a
denied port.

> Also, is the h323 patch compiled into the kernel? I have an ip phone
> that uses that protocol, which works ok for the most part behind ipcop
> pre4f (I have to reboot sometimes as it stops working), but with 1.3, I
> can dial out to my office, but the signal is dropped when the other end
> answers.
The patch is not compiled in.  I am having problems with the kernel patch.
 However, 2.4.20 just came out today, so I'm going to give that a try
instead.  Will try for an alpha2 release based on 2.4.20 this weekend.

Kind regards,

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

On 29.11.2002 02:19 jer wrote:
> hello....
> 
> have a little proposal for you all....i run an irc server, i am goin
> to make
> a channel called #ipcop. I will make a link from it on the download
> page for
> the alpha, and for the beta versions of ipcop that i presently mirror.
> Shall
> i send this to the users list as well? That way we can offer help via
> live
> chat, rather than email for those in need of a quick answer?
> 
> If you have an irc client you may connect via
> securityfreak.foxchat.net
> 
> If you do not, i am just finishing up the webclient connect that is
> accessable from www.securityfreak.net by clicking the live chat link
> 
> Your thoughts??
> Jeremy
> 

Not to diminsh your work in anyway, but what is wrong with the #ipcop 
channel on sourceforge?

  --
'ooroo

stinga...(:)-)
---------------------------------------------------
Email: st...@wo...      o
You need only two tools.        o /////
A hammer and duct tape. If it    /@   `\  /) ~
doesn't move and it should,     >  (O)  X<  ~  Fish!!
use the hammer. If it moves and  `\___/'  \) ~
shouldn't, use the tape.           \\\
---------------------------------------------------

Hi all,

For anyone interested I have released a new PCI ADSL driver (v3.2.1) for 
IPCop 0.1.2

You can download it from

http://www.traverse.com.au/downloads/drivers/default.asp?r=92

For details of this release see

http://www.traverse.com.au/downloads/drivers/default.asp?r=91

Also for anyone playing around with 2.4, I have built a driver engine that 
will compile a PCI ADSL driver for any 2.4 kernel....

http://adsl4linux.no-ip.org

Cheers,

  - Guy.

------------------------------------------------------------------
Guy Ellis
gu...@tr...

Traverse Technologies
ABN 98 078 657 324
652 Smith St.,
Clifton Hill, Victoria, 3068
AUSTRALIA
http://www.traverse.com.au
Tel (+613) 9486 7775
Fax (+613) 9482 7754
Mobile 0419 398 234
------------------------------------------------------------------

I was just wondering, there seems to be no external access page on this
revision, is it being worked on, or has it been dropped?

Also, is the h323 patch compiled into the kernel? I have an ip phone that
uses that protocol, which works ok for the most part behind ipcop pre4f (I
have to reboot sometimes as it stops working), but with 1.3, I can dial out
to my office, but the signal is dropped when the other end answers.

Just wondering.

Darren.

I installed and had a quick look at 1.3 alpha.

It installed ok, detected my cards - 3Com Corkscrew, installed ok.

I was able to bring up a vpn tunnel with another ipcop box, etc.

I then went to grc for a quick peek at the ports, port 5000 has been
plugged, great!
But I found that port 113 ident was showing as closed, and it is not even
configured in the external access page.
Was this done on purpose or was it an oversight?

The only other thing I noticed was in the gui that the pages were of varying
sizes in width, some grew with the web browser, some were larger than the
web browser. And connections showed a whole bunch of stuff that I don't
think was there in the last release.

Darren.

hello....

have a little proposal for you all....i run an irc server, i am goin to make
a channel called #ipcop. I will make a link from it on the download page for
the alpha, and for the beta versions of ipcop that i presently mirror. Shall
i send this to the users list as well? That way we can offer help via live
chat, rather than email for those in need of a quick answer?

If you have an irc client you may connect via   securityfreak.foxchat.net

If you do not, i am just finishing up the webclient connect that is
accessable from www.securityfreak.net by clicking the live chat link

Your thoughts??
Jeremy

I am in the process of testing out the alpha version of IPCOP 1.3.

Install went without a hitch, although some menus could do with a =
re-work around. Apart from a mis auto detect of my Netgear FA311 as a =
USB Cat? network card that was the only manual thing I had to change. =
Nothing really _major_ went worng.

I'm glad to see there is PCI ADSL support built in, but as I have not =
got one of these cards I carn't test this out.

USB2 EHCI - The kernel detected my 4 port card with ease. On install =
inspection it could not load up the modules for the card, but on the =
reboot that is needed after the install; everything proceeded to =
work/detect as per normal. I don't think this is a major error, but I =
just noticed it none the less.
All is needed now is to plug the modem in, as I have already uploaded =
the firmware mgmt.o without no problems at all.



The web gui has deffitnely had a change for the good, even if it is  My only little nag which is really personal in my opinion is the =
menu list on the left hand side; the font is a little bit too small. =
Then again thats only 'looks' , somthing to consider ?

Must admit I do like the proxy graphs tab on the Information page.

Only other option would be in the port forwarding section to not  the option to port fortward TCP and UDP but also a few other =
popular protocals such as pptp's GRE etc.
Again this is just my view on what could be improved and added. Granted =
this is only an alpha, IPCOP is comming along nicely and in my opinion =
this alpha sould be a beta becuase of its quality.=20

Bugs relating to pure kernel configs/firewall rules have yet to be =
found, but I am not an expert on IPTABLES/Netfilter so mabie a few other =
people could inspect the rules to make sure there squeaky tight. Im not =
saying the rules are bent/broke/whatever but if they can be tighter; =
then do it already :-)

One other thing I have rememberd is that somtimes when I do a $'reboot' =
on the shell it shuts down the system instead of doing a shutdown -r =
now. This could be me but im reporting it just to make sure. If im worng =
just say, at the end of the day it is probably down to user error =
anyway.

On the whole a big thumbs up as to what is an alpha release! I am =
impressed!

James Read.

Hi,

> G'day Christopher,
>        You are right, 120M HDD is not enough.   Here are the relevant bits 
> from my current "1.3 alpha 1" install....
> 
> Memory:
>            total       used       free     shared    buffers     cached
> Mem:      30460      27656       2804          0       8208      11144
> -/+ buffers/cache:    8304      22156
> Swap:     17132        176      16956

Look at that second line.  It is only using about 8,5MB of RAM.  The rest 
is just buffers and cache.  Not too bad...
From my installation, I can see that Squid will cause problems.  My Squid 
process is consuming almost 8MB RAM.  Runner up is Apache with 2.5MB.

But 16MB should be enough for the installation.  I did change the 
installrootimage from 4MB to 6MB, so I don't know if 12MB is still 
workable.

> Disk usage:
> Filesystem         Size  Used Avail Use% Mounted on
> /dev/harddisk4     622M   89M  502M  15% /
> /dev/harddisk1     5.7M  2.3M  3.1M  42% /boot
> /dev/harddisk3     154M  4.4M  142M   3% /var/log
> 
> Hope that is readable.
> 
>     Anyway, with 32M of RAM, swap is hardly being used at all.  However, if 
> you add up the HDD usage,  swap + "/" + "/boot" + "/var/log" + some install 
> work-space to expand ipcop.tgz,  it looks like about 270M would be an 
> absolute minimum.

Major oops.  Need to check the installer to cope with the new disk 
requirements (add to todo list).  The only reason for this new disk size 
is the addition of Python.  By itsself, that will add up to the 25MB that 
was added.  You can manually hack your cd and remove Python from the 
ipcop.tgz file (remove /usr/bin/python and /usr/lib/python2.2/).  You 
should also remove /usr/lib/gcc-lib and /usr/lib/gconv.  Those are there 
by accident and will be removed in the next iso.

However, I do have some good news.  When we switch to LFS, I will be able 
to fit almost the exact same installation into under 35MBs of diskspace.  
It should also help for memory usage, since most binaries won't have so 
many features compiled in, including glibc.

Kind regards,

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

At 09:19 PM Thursday 28/11/2002, Christopher Sawtell wrote:

> > Downloaded Mark's 1.3 alpha 1 this evening.
>So did I, but before I go much further please could I ask what the minimum
>disk and memory requirements are? I'm currently stuck on the Voldemort system
>because I could not get IPCop-0.1.1 to instsall onto this dear little old
>'486 with 16Megs RAM and 120Megs disk
><snip>

G'day Christopher,
       You are right, 120M HDD is not enough.   Here are the relevant bits 
from my current "1.3 alpha 1" install....

Memory:
           total       used       free     shared    buffers     cached
Mem:      30460      27656       2804          0       8208      11144
-/+ buffers/cache:    8304      22156
Swap:     17132        176      16956

Disk usage:
Filesystem         Size  Used Avail Use% Mounted on
/dev/harddisk4     622M   89M  502M  15% /
/dev/harddisk1     5.7M  2.3M  3.1M  42% /boot
/dev/harddisk3     154M  4.4M  142M   3% /var/log


Hope that is readable.

    Anyway, with 32M of RAM, swap is hardly being used at all.  However, if 
you add up the HDD usage,  swap + "/" + "/boot" + "/var/log" + some install 
work-space to expand ipcop.tgz,  it looks like about 270M would be an 
absolute minimum.

Cheers
Glen
--
      "The Irish were next, being the only people who could credibly be
          accused of lowering the tone of a society of convicts."
                 - Guy Rundle, on early NSW settlement.
--
    

Hiya.

I too have downloaded 1.3alpha1. I must say that you've done a great job on
it. It's very 'familiar'!

I had some problems with it as well, nothing too major. It detected the
3c509, but neither of the 8139's. insmod 8139too fixed that, and then I
could su - setup and select the cards correctly.

I suspect that the newer kernel might be addressing interfaces to cards
slightly differently - I had to dive into /var/ipcop/ethernet/settings to
make the right card appear on the right interface (eth0 vs. eth1 etc.). Once
I got this correct (with what was plugged in, and what ipcop0.1.2pre4h used
successfully) the green interface wasn't eth0 anymore, so that broke dhcp.
This has been mentioned before, and I could probably (eventually) get around
it.

I didn't try importing the configuration from 0.1.2pre4h, that would be
interesting.

Other than that, it seemed to work very well on my P133, 32Mb RAM, 2.2Gb HD,
1 x 3c509 and 2 x RT 8139(c?). The http interface makes better use of screen
real-estate, can fit more text on a single line.

I'd like to throw some fwbuilder iptables configurations at it... hmmm,
interesting.

Mark, I've sent a diff into Eric to address some PPTP/mtu/mru issues, do you
want it as well, or are you going to base your future scripts of whatever he
releases in the 0.1.2 code base so you'll pick them up anyway?

Cheers -

On Thu, 28 Nov 2002 11:16, Harry Moyes wrote:
> Hi all
>
> Downloaded Mark's 1.3 alpha 1 this evening.=20
So did I, but before I go much further please could I ask what the minimu=
m=20
disk and memory requirements are? I'm currently stuck on the Voldemort sy=
stem=20
because I could not get IPCop-0.1.1 to instsall onto this dear little old=
=20
'486 with 16Megs RAM and 120Megs disk

TIA a 10^6

--=20
Sincerely etc.,
Christopher Sawtell

Hi,

> If possible in the next release/version would it be posible to include
> support for USB2 cards, with various chipsets such as via/eci. I brought
> a USB2 (jetway) card as it said it had two uchi chips on it and a echi?
> chip for USB2 .Thinking I could use this on ipcop, i install it but
> didnt detect the speedtouch modem on the end, nor did any of the lights
> light up on the modem.

You could give the 1.3 ALPHA (*HINT*) release a try.  I added in support
for the ehci/usb2.0 adapter.

Kind regards,

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

If possible in the next release/version would it be posible to include =
support for USB2 cards, with various chipsets such as via/eci. I brought =
a USB2 (jetway) card as it said it had two uchi chips on it and a echi? =
chip for USB2 .Thinking I could use this on ipcop, i install it but =
didnt detect the speedtouch modem on the end, nor did any of the lights =
light up on the modem.=20

Thanks

James.

Hi all

Downloaded Mark's 1.3 alpha 1 this evening.  Burnt ISO, wrote floppies from
the ISO, installed on 50Mhz 486 with 64Mb memory.  Install ran OK, some of
the install menus corrupted by the long release string.  Have it on my
private test network, will try it with the usual tests tomorrow.

Boots OK, web server's OK, and looks like the patch I sent in ages ago to
display the system name on the blue bar is in as well - I'm stunned!

Thanks Mark, looks like a good start.

Harry Moyes

Hi,

> I'm about to hack my way in enabling ipcop 1.3alpha to support the USB
> eci (globespan chipset) modems. I have it working here.
> 
> However, I would like to ask what is the best way to submit
> patches/updates (I'll need extra stuff in the config program/cgi and
> binaries to make it work). On the other hand, it will support pppoe,
> pppoa, fixed ip and a whole set of encapsulations.
> 
> Also, I'll need a few extra functionalities in the kernel (I will need
> to submit an update to the kernel .config).
> 
> Shall I get CVS access or you prefer to merge changes "by hand"?

For now, I prefer merging changes by hand, especially changes this
size.  So, if you could send me a diff against CVS, I'll be happy to
merge it.

Kind regards,

Mark

Mark, I got the ISO today too.

I'm about to hack my way in enabling ipcop 1.3alpha to support the USB
eci (globespan chipset) modems. I have it working here.

However, I would like to ask what is the best way to submit
patches/updates (I'll need extra stuff in the config program/cgi and
binaries to make it work). On the other hand, it will support pppoe,
pppoa, fixed ip and a whole set of encapsulations.

Also, I'll need a few extra functionalities in the kernel (I will need
to submit an update to the kernel .config).

Shall I get CVS access or you prefer to merge changes "by hand"?

Dave.

Hi,

>     Dutifully downloaded  IPCop v1.3 alpha1 and did an HTTP install on
> an
> old IBM PC330.   P-100, 32M, 850M HDD, 2xRTL8139D (green, orange, red is
> modem) no CDROM  - fairly minimal but overkill for my dial-up
> connection.
>
>     Boot from floppy, select HTTP install, insert driver disk.
>     Selected "probe" to find the NIC,  reported USB NIC - install fails,
>
> sorry can't cat /proc/bus/usb/devices.

Well, I've got this one sorted out.  It seems that the USB network drivers
will load succesfully, no matter what.  Even if you don't have USB, you
can still load these modules.  My only choice is to remove them from the
autodetect.

>      No prob, reboot - look through the driver list - no 8139too in the
> list, bugger!
Well, there's two 8139 based drivers in the list:
RealTek RTL-8139 Fast Ethernet                = 8139too
RealTek RTL-8139C+ series 10/100 PCI Ethernet = 8139cp

>      Select "MANUAL" and enter 8139too   without any parameters, OK,
> driver
> installs and rest of HTTP installation seems normal.
>      Remote admin on port 81 seems OK -  using it now for this dial-up
> session, but came a guttsa when I tried to do a SSH login as setup (to
> configure orange) - no remote shell??
Did you re-enable sshd in the admin pages?

> BTW. The revised cgi-bin layout seems even more awkward than the old one.
I haven't changed anything.  Only the external access page is now gone.

Kind regards,

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

G'day Mark,
    Dutifully downloaded  IPCop v1.3 alpha1 and did an HTTP install on an 
old IBM PC330.   P-100, 32M, 850M HDD, 2xRTL8139D (green, orange, red is modem)
no CDROM  - fairly minimal but overkill for my dial-up connection.

    Boot from floppy, select HTTP install, insert driver disk.
    Selected "probe" to find the NIC,  reported USB NIC - install fails, 
sorry can't cat /proc/bus/usb/devices.
     No prob, reboot - look through the driver list - no 8139too in the 
list, bugger!
     Select "MANUAL" and enter 8139too   without any parameters, OK, driver 
installs and rest of HTTP installation seems normal.
     Remote admin on port 81 seems OK -  using it now for this dial-up 
session, but came a guttsa when I tried to do a SSH login as setup (to 
configure orange) - no remote shell??   BTW. The revised cgi-bin layout 
seems even more awkward than the old one.

HTH.  Anything else?  Just ask.

Cheers
Glen

--
    "Does Linux run on Red Hat?" - Joe Barr
--
     

Hello
I want to develop a Web-Gui to manage QoS, and just want to know if
something similar for ipcop exists ??
If not, i will start that project.
Any suggestions are welcome.
Ufuk Altinkaynak

Hi,

The v1.3 alpha is online right now.
http://www.securityfreak.net/ipcop/alpha/

Things you need to be aware of:
1. Some of the network drivers were renamed.  If you do a restore of
your settings, you may need to edit /var/ipcop/ethernet/settings by
hand.  For example, rtl8139 is now 8139too.

2. The external access page is gone.  Due to the nature of 2.4
firewalling, the original meaning of this page no longer exists.  There
are two different sets of rules:
- INPUT, meant for traffic destined for the firewall
- FORWARD, meant for traffic destined for a host behind the firewall.
For now, I have solved this by allowing the entire internet access to a
port that you forward to a host behind the ipcop firewall.  Also, it is
not possible to grant access to a port on the ipcop firewall, besides
manually editing /etc/rc.d/rc.firewall.up.

3. The following modules are gone: ip_masq_ipsec, ip_masq_icq and
ip_masq_h323.  You should be able to use icq.  You can only use one
ipsec connection behind a 2.4 kernel right now.  And there is a h323
masquerading module, but I'm having trouble with the kernel patch.

4. The firewalllog.dat file has a very ugly regexp at the bottom. ;-)

5. I have had at least one report of the install auto-detecting an USB NIC 
when no USB NIC was installed.  If you get this error, could you please 
send me the output of:   cat /proc/bus/usb/devices

Kind regards,

Mark Wormgoor

Does anyone have the src of ipcop-0.1.2pre4 'f' or 'h' ?

If so, could you please provide a link.

Thank you.