Subject: Re: ipcop and serial ports
From: Jim Gribbin (jewelrysupplier@gci.net)
Date: Mon Apr 28 2003 - 18:17:30 AKDT
I was using smoothwall at one time at work. But then my available
Internet connection changed to GCI's DSL and it came with a Linksys
router. Nobody bothered to ask me if I had another solution, it was just
'Here it is'. This was about 6 months or so ago. So I no longer have
Smoothwall here. I stripped that box out a few weeks later. I have
considered setting up smoothwall or ipcop in the DMZ behind the router,
but haven't gotten around to it.
At home I was using a MultiTech Proxy solution that I had from before I
discovered Linux. I used it until a couple of weeks ago. I was
effectively starting fresh and made the decision to try ipcop this time
around.
Jim Gribbin
On Mon, 2003-04-28 at 14:49, enderak@gci.net wrote:
> I, for one, have not switched to ipcop. I installed it from smoothwall 0.9.9, but kept having problems with it (mostly related to overzealous logging filling up my hard drive and using all my cpu cycles to process) so I installed smoothwall 1.0 GPL, and its been running happy ever since.
>
> I don't know, maybe it's my particular setup, but after all the good things I have heard about it, I was rather disappointed with all the problems.
>
> Justin
>
>
> ----- Original Message -----
> From: Adam Elkins <i-robot@gci.net>
> Date: Monday, April 28, 2003 3:22 pm
> Subject: Re: ipcop and serial ports
>
> >
> > I'm just courious, why has everyone switch to ipcop? Is it really
> > better than Smoothwall?
> > What are the pros/cons?
> >
> > Adam (still rockin an authentic AKLUG smoothie)
> >
> >
> > On Mon, 28 Apr 2003 13:57:19 -0800
> > Jim Gribbin <jewelrysupplier@gci.net> wrote:
> >
> > >
> > > Nice try, but ipcop doesn't have a serial.conf. At least not in
> > /etc.> I'm still looking to see if I can find it somewhere else as
> > ipcop seems
> > > to have moved or hidden some of scripts for security reasons.
> > >
> > > I may take a shot at just creating one and see if it uses it.
> > >
> > > Jim Gribbin
> > >
> > > On Mon, 2003-04-28 at 11:14, Fielder George Dowding wrote:
> > > > Greetings Jim and all,
> > > >
> > > > Under the 2.4 kernel, serial port setup is handled in a new and
> > > > better way, really :)
> > > >
> > > > Look in the file /etc/serial.conf
> > > >
> > > > Read the man page for setserial
> > > >
> > > > You will probably have to edit serial.conf to reflect the desired
> > > > ttyS<n>, IRQ, and I/O address. The card you are talking about
> > may be
> > > > listed in serial.conf. In any case, look for the stanzas that set
> > > > the ports to the ones you are getting and edit them to the
> > ones you
> > > > want.
> > > >
> > > > fgd.
> > > >
> > > > On 27 Apr 2003 22:26:57 -0800
> > > > Jim Gribbin <jgribbin@alaska.net> wrote:
> > > >
> > > > >
> > > > > I don't think I'm doing a good job at describing my serial port
> > > > > problem, so I'll try a little different tact.
> > > > >
> > > > > I have a pci high speed port card with 2-serial & 1-parallel
> > > > > ports.
> > > > >
> > > > > Under the 2.2 kernel, /proc/pci showed an unknown card mfg'd by
> > > > > Timedia in a particular slot with 3-ports and an irq. Apparently
> > > > > because the card was unknown, Linux did nothing with the
> > ports and
> > > > > I could assign the ports using setserial's port option to
> > whatever> > > available /dev/ttySx were available.
> > > > >
> > > > > Under the 2.4 kernel, Linux seems to know what the card is.
> > > > > /proc/pci now shows a multi-port card mfg'd by Timedia (I don't
> > > > > recall the exact wording, but the card is now known) with 2-
> > serial> > > ports and a parallel port. Because Linux now knows the
> > card, it is
> > > > > assigning the ports for me. But I want them assigned
> > elsewhere and
> > > > > Linux won't let me do it has them already assigned.
> > > > >
> > > > > Clear as mud now? :-)
> > > > >
> > > > > Jim Gribbin
> > > > >
> > > > >
> > > > >
> > > > > ---------
> > > > > To unsubscribe, send email to <aklug-request@aklug.org>
> > > > > with 'unsubscribe' in the message body.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > ---------
> > > To unsubscribe, send email to <aklug-request@aklug.org>
> > > with 'unsubscribe' in the message body.
> > >
> >
> > ---------
> > To unsubscribe, send email to <aklug-request@aklug.org>
> > with 'unsubscribe' in the message body.
> >
> >
>
>
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
This archive was generated by hypermail 2a23 : Mon Apr 28 2003 - 18:09:23 AKDT