On Thu, 2003-10-30 at 08:53, Norbert Preining wrote:
> Our bridged/fw was running 160 day with code from there. Now I have
> installed a new kernel (2.4.22) with the current ebtables code
> (ebtables.sf.net) which can do even more, although I don't need it. But
> ebtables is the code in 2.6 and ac
On Thu, 2003-10-30 at 08:53, Norbert Preining wrote:
> Our bridged/fw was running 160 day with code from there. Now I have
> installed a new kernel (2.4.22) with the current ebtables code
> (ebtables.sf.net) which can do even more, although I don't need it. But
> ebtables is the code in 2.6 and ac
On Mit, 29 Okt 2003, Benjamin Goedeke wrote:
> http://bridge.sf.net to replace the firewall once the transition to
Our bridged/fw was running 160 day with code from there. Now I have
installed a new kernel (2.4.22) with the current ebtables code
(ebtables.sf.net) which can do even more, although I
On Mit, 29 Okt 2003, Benjamin Goedeke wrote:
> http://bridge.sf.net to replace the firewall once the transition to
Our bridged/fw was running 160 day with code from there. Now I have
installed a new kernel (2.4.22) with the current ebtables code
(ebtables.sf.net) which can do even more, although I
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>I administer a LAN that will soon be moved from private to public IP
>space. The LAN is inside a university network and as such in a rather
>hostile environment.
Another alternative is a proxy-arp firewall. See
http://www.blars.org/sapaf.
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>I administer a LAN that will soon be moved from private to public IP
>space. The LAN is inside a university network and as such in a rather
>hostile environment.
Another alternative is a proxy-arp firewall. See
http://www.blars.org/sapaf.
> as opposed to a setup with a firewall+router.
With Linux there are few problems with transparent firewalling setup - ie,
normal iptables don't work with such setup to well, you need to use special
bridge-iptables, ebtables IIRC. One drawback to that is that you can't do
everything your'e used to
Hello everyone,
I administer a LAN that will soon be moved from private to public IP
space. The LAN is inside a university network and as such in a rather
hostile environment.
At the moment there is a firewall with a public IP doing all the
filtering and a NAT/router box behind this. Now I'm thin
> as opposed to a setup with a firewall+router.
With Linux there are few problems with transparent firewalling setup - ie,
normal iptables don't work with such setup to well, you need to use special
bridge-iptables, ebtables IIRC. One drawback to that is that you can't do
everything your'e used to
Hello everyone,
I administer a LAN that will soon be moved from private to public IP
space. The LAN is inside a university network and as such in a rather
hostile environment.
At the moment there is a firewall with a public IP doing all the
filtering and a NAT/router box behind this. Now I'm thin
10 matches
Mail list logo
