Previously Koala wrote:
> I was wondering if someone could point to a vast area about ipchains.
Heh, I know there is rusty's unreliable guide to netfilter which is
a pretty good document imho, but it only works for netfilter which is
in the 2.4 kernels.
Anyway, can you confirm that what you want
Previously Koala wrote:
> I was wondering if someone could point to a vast area about ipchains.
Heh, I know there is rusty's unreliable guide to netfilter which is
a pretty good document imho, but it only works for netfilter which is
in the 2.4 kernels.
Anyway, can you confirm that what you want
Marco,
No. What I gather here is that Koala has his own LAN, as well as a
corporate intranet, which is then connected to the Internet by
masquerading. He wants a router between his own LAN and the corporate
intranet. That router must forward Internet-bound datagrams from his LAN
to the corporate r
Marco,
No. What I gather here is that Koala has his own LAN, as well as a
corporate intranet, which is then connected to the Internet by
masquerading. He wants a router between his own LAN and the corporate
intranet. That router must forward Internet-bound datagrams from his LAN
to the corporate
Koala wrote:
> on a HUB. Their IP Addresses are 1.1.1.1/24 . My idea, was, to have Network C
> going
> through a default gateway of 1.1.1.1 (Debian with ipchains) where the second
> interface card goes to the normal network B (10.10.10.1) Therefore, Netwrok C
> can
> see Network B, but Network B
I'd check out http://www.linux-firewall-tools.com/
It has a good guide on setting up a LAN, firewalling, and various
basic network security issues. It also has an automatic firewall
generation tool, but it's better to use the firewall it generates
as a guide to writing your own rather than just p
Koala wrote:
> on a HUB. Their IP Addresses are 1.1.1.1/24 . My idea, was, to have Network C going
> through a default gateway of 1.1.1.1 (Debian with ipchains) where the second
> interface card goes to the normal network B (10.10.10.1) Therefore, Netwrok C can
> see Network B, but Network B can´
I'd check out http://www.linux-firewall-tools.com/
It has a good guide on setting up a LAN, firewalling, and various
basic network security issues. It also has an automatic firewall
generation tool, but it's better to use the firewall it generates
as a guide to writing your own rather than just
No, not really
Network A (Internet)
Network B (10.10.10.1/24)
Network C (1.1.1.1/24)
Currently, the normal internal (Network B) work stations use one default
gateway.
Lets say it is 10.10.10.1, and the IP Addresses of the work stations would be in
the class 10.10.10.1/24. Network C is a smal
On Fri, Jul 07, 2000 at 12:03:16PM +0200, Mr.Koala wrote:
> Hi List,
>
> I was wondering if someone could point to a vast area about ipchains. I
> am trying to mount a debian box with ipchains and two network cards. The
> two network cards part is going fine I think, as I am also getting help
> to
Hi List,
I was wondering if someone could point to a vast area about ipchains. I
am trying to mount a debian box with ipchains and two network cards. The
two network cards part is going fine I think, as I am also getting help
to install an NE2000 as eth1. Anyway, staying on the point, the basis is
No, not really
Network A (Internet)
Network B (10.10.10.1/24)
Network C (1.1.1.1/24)
Currently, the normal internal (Network B) work stations use one default gateway.
Lets say it is 10.10.10.1, and the IP Addresses of the work stations would be in
the class 10.10.10.1/24. Network C is a smal
On Fri, Jul 07, 2000 at 12:03:16PM +0200, Mr.Koala wrote:
> Hi List,
>
> I was wondering if someone could point to a vast area about ipchains. I
> am trying to mount a debian box with ipchains and two network cards. The
> two network cards part is going fine I think, as I am also getting help
> t
Hi List,
I was wondering if someone could point to a vast area about ipchains. I
am trying to mount a debian box with ipchains and two network cards. The
two network cards part is going fine I think, as I am also getting help
to install an NE2000 as eth1. Anyway, staying on the point, the basis i
14 matches
Mail list logo
