On Tue, Nov 30, 2004 at 11:59:38AM -0800, Paul Johnson wrote:
> On Tuesday 30 November 2004 11:56 am, Mike M wrote:
>
> > If risk is manageable then I choose a). If not, then b) or c) father
> > buys router/firewall appliance.
>
> Finagle's Law dictates that A will inevitably lead to B. That's a
Ray you sent this to me privately...
Fwd this one back to the list...
CW Harris wrote on 2004-11-30 02:33:
> You might google, or ask, over on debian-firewall... I seem to recall
> someone mentioning a package or setup they used that allowed one to
> restore the old ruleset after a defined time
On Tuesday 30 November 2004 11:56 am, Mike M wrote:
> Yep. Now, how to get it in.
>
> a) ssh over Internet to unprotected box and recompile kernel and play
>with config
> b) drive 6h to get box; install behind my f/w; fix it; drive 6h to put
>box back
>
> If risk is manageable then I
On Tue, Nov 30, 2004 at 11:19:04AM -0800, Paul Johnson wrote:
> On Tuesday 30 November 2004 10:59 am, Mike M wrote:
> > On Mon, Nov 29, 2004 at 02:01:17PM -0800, Paul Johnson wrote:
> > > On Monday 29 November 2004 1:04 pm, Mike M wrote:
> > >
> > > > 1) connect Deb box to cable modem
> > > > 2) s
On Tuesday 30 November 2004 10:59 am, Mike M wrote:
> On Mon, Nov 29, 2004 at 02:01:17PM -0800, Paul Johnson wrote:
> > On Monday 29 November 2004 1:04 pm, Mike M wrote:
> >
> > > 1) connect Deb box to cable modem
> > > 2) ssh to Deb box to test access
> > > 3) have father install 2nd NIC on Deb b
On Mon, Nov 29, 2004 at 02:01:17PM -0800, Paul Johnson wrote:
> On Monday 29 November 2004 1:04 pm, Mike M wrote:
>
> > 1) connect Deb box to cable modem
> > 2) ssh to Deb box to test access
> > 3) have father install 2nd NIC on Deb box
> > 4) using ssh, install iptables and configure iptables on
On Mon, Nov 29, 2004 at 05:04:20PM -0500, David Mandelberg wrote:
> Mike M wrote:
> >>Also, there should be a firewall on the box before it's
> >>ever connected to the net.
> >
> >
> > Chicken/egg dilemma here? Any suggestions?
> This isn't a chicken/egg dilemma (almost nothing is), all you need
Mike M wrote:
>>Also, there should be a firewall on the box before it's
>>ever connected to the net.
>
>
> Chicken/egg dilemma here? Any suggestions?
This isn't a chicken/egg dilemma (almost nothing is), all you need to do
is install it from a cd or something, if you can't do that then just
inst
On Monday 29 November 2004 1:04 pm, Mike M wrote:
> 1) connect Deb box to cable modem
> 2) ssh to Deb box to test access
> 3) have father install 2nd NIC on Deb box
> 4) using ssh, install iptables and configure iptables on Deb box
That'll work, but you might want to install ipmasq and get your D
On Mon, Nov 29, 2004 at 03:29:34PM -0500, David Mandelberg wrote:
> Mike M wrote:
> > 1) connect Deb box to cable modem
> > 2) ssh to Deb box to test access
> > 3) have father install 2nd NIC on Deb box
> > 4) using ssh, install iptables and configure iptables on Deb box
> That would work, but one
Mike M wrote:
> 1) connect Deb box to cable modem
> 2) ssh to Deb box to test access
> 3) have father install 2nd NIC on Deb box
> 4) using ssh, install iptables and configure iptables on Deb box
That would work, but one problem is that when testing firewall rulesets
(especially if you've never don
Hi,
Yesterday I built a Debian stable file server for my father assuming he
had a router/switch with a DHCP server on it. Today I learned that he
does not have a router - only a switch.
I want to try making the Debian box into a router remotely. Would this work?
1) connect Deb box to cable mode
12 matches
Mail list logo
