Hi all.
I have got to see a strange thing. Some of my iptables' rules are
disaprearing after several days!!!
I have many rules like:
# iptables -t mangle -A $MYCHAIN -s $SRC_IP -d $DST_IP -j MARK
--set-mark $MARK
for classifying traffic for shaping, total about 100 rules with
different 20
Hi Marco,
On 1/23/07, Marco Berizzi [EMAIL PROTECTED] wrote:
did you try to 'modprobe aes'?
Yeah and lsmod showes that aes is loaded into the kernel.
--
Gegroet,
Tim
___
LARTC mailing list
LARTC@mailman.ds9a.nl
Hello there, it does not matter what type of network you are trying to
reach, the Network unreachable error message suggests, that the router
does not know on which interface(physical) to forward the packets with
destination -net !
Before the lane you wrote, try this:
route add -net
Hi
We have applied the routing patches from
http://www.ssi.bg/%7Eja/#routes. To 2.6.15 this seems to have broken our
output natting. Has anyone else experienced this or any advice on how to
fix. Is this working on the newer kernel i.e. 2.6.19 ? Any help would be
appreciated.
--
Tim Haak
On 22/01/07 Michael P. Soulier did say:
This mention is in the howto
If you tunnel is not working, please check your routing. Your hosts need to
know that they should send the packets for the opposite network to you vpn
gateway. The easiest setup would be using your vpn gateway as default
Hi all,
Since the mail list receives a lot of repeated subjects (for example: i
have two adsl lines...), maybe these specific issues should be treated on
the LARTC Guide, or maybe if we had an wiki?
Is there a LARTC Wiki?
If not, what do you think about creating one?
Thanks
--
Marco
Yes, specially this subject (2 adsl lines...) ;)
It would be cool to have a wiki.. anyone motivated to create one?
On 1/23/07, Marco Aurelio [EMAIL PROTECTED] wrote:
Hi all,
Since the mail list receives a lot of repeated subjects (for example: i
have two adsl lines...), maybe these specific
I'm not aware of one, and I think it's an excellent idea.
There's some great software available for LARTC, and some of the
documentation is very good, but unfortunately it's all a bit disparate.
A wiki would be a great start.
I'd be happy to host one and transfer stuff into it unless someone
I also think that this would be a good idea. Having examples rulesets
and related firewall and QOS stuff.
On Tue, Jan 23, 2007 at 03:53:23PM GMT, Andrew Beverley [EMAIL PROTECTED] said
the following:
I'm not aware of one, and I think it's an excellent idea.
There's some great software
ESFQ's original hashing algorithm never worked particularly well for the
src or dst hash types: close IP addresses, such as 10.0.0.1 and 10.0.0.2
often hashed to the same number, even with many different perturbation
values. This prevented the src and dst hash types from working
adequately with
On Tue, Jan 23, 2007 at 03:53:23PM +, Andrew Beverley wrote:
I'm not aware of one, and I think it's an excellent idea.
There's some great software available for LARTC, and some of the
documentation is very good, but unfortunately it's all a bit disparate.
A wiki would be a great start.
I think that wiki is not the same thing, and...after all...is not the
LARTC official wiki...
Isn't the LARTC mailing list more popular? I think it is...and a wiki is
the way to go...imho
Alex Samad wrote:
On Tue, Jan 23, 2007 at 03:53:23PM +, Andrew Beverley wrote:
I'm not aware of
Hello,
On Tue, 23 Jan 2007, Tim Haak wrote:
We have applied the routing patches from
http://www.ssi.bg/%7Eja/#routes. To 2.6.15 this seems to have broken our
output natting. Has anyone else experienced this or any advice on how to
fix. Is this working on the newer kernel i.e.
Mark Krenz wrote:
I also think that this would be a good idea. Having examples rulesets
and related firewall and QOS stuff.
On Tue, Jan 23, 2007 at 03:53:23PM GMT, Andrew Beverley [EMAIL PROTECTED]
said the following:
I'm not aware of one, and I think it's an excellent idea.
14 matches
Mail list logo
