On Sun, Feb 18, 2007 at 02:44:50PM -0700, Archive wrote:
> As mentioned in an earlier email the DOMU or secondary Xen system(s) can
> not only talk to the DOM0 or Xen primary system but also to other other
> DOMU or secondary Xen system(s) and that most likely involves not only
> LAN interaction
As mentioned in an earlier email the DOMU or secondary Xen system(s) can
not only talk to the DOM0 or Xen primary system but also to other other
DOMU or secondary Xen system(s) and that most likely involves not only
LAN interaction but also Internet interaction.
Where internet interaction is
On Sun, Feb 18, 2007 at 02:44:50PM -0700, Archive wrote:
> It would be nice to have some examples of this route management code
> with an explanation of it's operation and theory for both simple and
> complex scenarios, especially some Xen scenarios.
>
> Any takers on this
Alvin Oga wrote:
hi ya
i donno what all the major features/advances of iptables is over
ipchains..but...
ipchains runs under 2.4.x kernels if you enable the "ipchains" modules
in the firewall config section of the kernel
- ipchains runs unmodified under 2.4...
if you are using a gener
hi ya
i donno what all the major features/advances of iptables is over
ipchains..but...
ipchains runs under 2.4.x kernels if you enable the "ipchains" modules
in the firewall config section of the kernel
- ipchains runs unmodified under 2.4...
if you are using a generic 2.4.x kernel wit
On Fri, 1 Feb 2002, David Gardi wrote:
> > I've just switched to 2.4.x on my laptop, and it was painless. I'm about
> > to do the same on a desktop that runs a firewall using my old original
> > ipfwadm rules, which are magically translated by debian (potato/2.2.x)
> > into (i think) ipchains.
>
Rick Macdonald wrote:
On Thu, 31 Jan 2002, Eric G. Miller wrote:
On Thu, 31 Jan 2002 09:08:45 -0500 (EST), Matt Kopishke <[EMAIL PROTECTED]>
wrote:
I have set up a firewall using ipchains and the bridge patch
(bridgein) under potato (2.2.19). The one snag I had was although the
firewall
On Thu, 31 Jan 2002, Eric G. Miller wrote:
> On Thu, 31 Jan 2002 09:08:45 -0500 (EST), Matt Kopishke <[EMAIL PROTECTED]>
> wrote:
>
> > I have set up a firewall using ipchains and the bridge patch
> > (bridgein) under potato (2.2.19). The one snag I had was although the
> > firewall works well
On Thu, 31 Jan 2002 09:08:45 -0500 (EST), Matt Kopishke <[EMAIL PROTECTED]>
wrote:
> I have set up a firewall using ipchains and the bridge patch
> (bridgein) under potato (2.2.19). The one snag I had was although the
> firewall works well only letting the world see certain ports (80 & 443),
> i
I have set up a firewall using ipchains and the bridge patch
(bridgein) under potato (2.2.19). The one snag I had was although the
firewall works well only letting the world see certain ports (80 & 443),
it doesn't let the servers behind the firewall get out. I set up a rule
that allows all traff
On Thu, Feb 01, 2001 at 03:49:22PM -0600, will trillich wrote:
...
> from what i've seen posted hither and yon, you
> can just add
>
> iface eth0 inet dhcp
>
> and you're off to the races.
>
> would that do?
No:) This only brings up your interface with ip etc setup via dhcp.
You'll have t
On Fri, Feb 02, 2001 at 12:18:34PM -0700, Yobb wrote:
>
> Hi folks. Can you help me out with this one?
>
> I want to fire up my ipchains set up when my machine boots. I am
> running IP Masq and I get my internet connection via DHCPCD. My second
> ethernet card in my MASQ machine is set up usin
Hi folks. Can you help me out with this one?
I want to fire up my ipchains set up when my machine boots. I am
running IP Masq and I get my internet connection via DHCPCD. My second
ethernet card in my MASQ machine is set up using the
/etc/network/interfaces as below
# Used by ifup(8)
ue.net.au/~pancreas
> > > > Work Email: [EMAIL PROTECTED]
> > > >
> > > > On Tue, 30 May 2000, Ron Rademaker wrote:
> > > >
> > > > > I'm not a telepath, I can't see from here if you got the right things
> > >
, Ron Rademaker wrote:
> > >
> > > > I'm not a telepath, I can't see from here if you got the right things in
> > > > your kernel ;) But you ipchains misses something, the masquerading, you
> > > > should do:
> > > >
> > > >
gt; >
> > > ipchains -A forward -j MASQ -s /24 -d 0/0
> > >
> > > I can tell you what you should have in your kernel: IP Masquerading, if
> > > you want to masquerade ping, you should also have ICMP Masqerading.
> > >
> > > Ron Radema
ICMP Masqerading.
> >
> > Ron Rademaker
> >
> > On Tue, 30 May 2000, Corey Popelier wrote:
> >
> > > Ok I now have my Debian and Windows boxes networked, and I tried to set up
> > > IP Chains as follows:
>
0/0
>
> I can tell you what you should have in your kernel: IP Masquerading, if
> you want to masquerade ping, you should also have ICMP Masqerading.
>
> Ron Rademaker
>
> On Tue, 30 May 2000, Corey Popelier wrote:
>
> > Ok I now have my Debian and Wi
masquerade ping, you should also have ICMP Masqerading.
Ron Rademaker
On Tue, 30 May 2000, Corey Popelier wrote:
> Ok I now have my Debian and Windows boxes networked, and I tried to set up
> IP Chains as follows:
>
> ipchains -P forward DENY
> ipchains -A forward -i ppp0 -j A
Ok I now have my Debian and Windows boxes networked, and I tried to set up
IP Chains as follows:
ipchains -P forward DENY
ipchains -A forward -i ppp0 -j ACCEPT
Now whenever I traceroute something from the Win box I get:
1 1ms<10ms<10ms (Linux b
Since there are some on the list that occasionally
send an email about IP Chains, I thought I would
drop the URL for a IP Chains GUI that I wrote. I realize
that most establish their IP Chains rules at boot.
But I created this GUI to change the rules on the fly.
If you have Perl/Tk installed, the
On 23 Feb, [EMAIL PROTECTED] wrote:
> *- On 23 Feb, Ian Keith Setford wrote about "IP-Chains help!?"
>>
>> Since I just picked up a new computer last week I no longer have to
>> dual-boot. I now have a need to share a 56k dial-up. I'll admit that I
>>
*- On 23 Feb, Ian Keith Setford wrote about "IP-Chains help!?"
>
> Since I just picked up a new computer last week I no longer have to
> dual-boot. I now have a need to share a 56k dial-up. I'll admit that I
> haven't used/needed ip-masquerading since mid 1996
check out
http://www.rustcorp.com/linux/ipchains/
Jian
>
>I'd appreciate any help. Also, I was wondering if anyone has a more
>in-depth place to get info about ipchains (other than the man page.)
>
>Thanks.
Since I just picked up a new computer last week I no longer have to
dual-boot. I now have a need to share a 56k dial-up. I'll admit that I
haven't used/needed ip-masquerading since mid 1996 so I'm very rusty with
ipfwadm. Now, if I'm correct, we have ipchains instead of ipfwadm and
such? I am
>doing some firewalling. I'm running 2.1.104 on my gateway, and I've played
>with ipfwcahins some.
ipchains :)
>2) Can someone share a recipe to allow incoming/outgoing ssh traffic. I
First, you have to allow traffic into the firewall:
# Any packets coming from your internal network is good
So, I want to "go to the next level" with my network at home, and start
doing some firewalling. I'm running 2.1.104 on my gateway, and I've played
with ipfwcahins some.
A couple of questions:
1) Is there a Debian way to set this stuff up - /etc/firewall or something?
2) Can someone share a rec
Greetings,
I've spent most of the day exploring the world of firewalling with Debian 2.0.
if I use ipfwadm-wrapper with the following commands, everything works
properly. Like so:
ipfwadm-wrapper -F -a accept -P tcp -S 0/0 1024:65535 -D 172.16.0.2 http
ipfwadm-wrapper -I -a accept -P tcp
28 matches
Mail list logo
