er. Make sure you have
rules and routes for both directions. Of course, there must be some
IP addresses because routes work only for devices with IPs. SNAT should
be able to assign non-local external IP address, not possible for
MASQUERADE, you have to use SNAT everywhere. T
s
- RNET sees valid lnet_IP when your gateway talks to RNET via
ipsec (allowing even masquerade for LNET boxes to be used when
talking with RNET).
Hope that helps!
> Cheers,
> Seba.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Hello,
On Mon, 25 Jun 2007, Seba Tiponut wrote:
> I use Julian Anastasov 'routes' (to be more specific: static_routes,
> alt_routes and nf_reroute) patches on a 2.4.32 kernel. On the same host I run
> IPSec. I have discovered after a few hours of networking problems
Hello,
On Fri, 23 Mar 2007, Frédéric Massot wrote:
> >>>> I regularly have errors (kernel: dst cache overflow) and crash of a
> >>>> firewall under Linux 2.6.17 and the route patch from Julian Anastasov.
> >
> > I assume IP_ROUTE
Hello,
On Thu, 22 Mar 2007, [ISO-8859-15] Frédéric Massot wrote:
> >> I regularly have errors (kernel: dst cache overflow) and crash of a
> >> firewall under Linux 2.6.17 and the route patch from Julian Anastasov.
I assume IP_ROUTE_MULTIPATH_CACHED is dis
to
our local IP:
+ if (lsrc && res.type != RTN_UNICAST && res.type != RTN_NAT)
+ goto e_inval;
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
a large list of ip's, but in running this setup I've never
> seen it use both gateway's.
Do you have script to ping/arping the gateways on eth device(s)?
The NOARP devices are always preferred if the GWs on ARP devices are
not marked reachable in ARP
R=m
> CONFIG_IP_ROUTE_MULTIPATH_RANDOM=m
> CONFIG_IP_ROUTE_MULTIPATH_WRANDOM=m
> CONFIG_IP_ROUTE_MULTIPATH_DRR=m
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
quot; for your all kindness. Tonight I will
> study deeper about your guideline and do more testing. Any progress, I'll
> update you via this mailing group.
Yes, it is not easy, there is no complete solution for such
setups as the details can be very different, you have to combine
lo
kernel 2.6.10, CONNMARK is included already, you don't have to
> patch anything.
I'm happy with that, i just don't see the problems you see
with "routes".
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LART
other high level dependencies can be solved with CONNMARK,
eg. web session persistence, may be with help from application
modules. The problem here is that "routes" works only at routing
level while CONNMARK work can be helped from other modules.
Regards
--
Julian Anastasov <[
nyway, it will be OK if use gcc 3.3.5 to compile. Can Julian check that?
> Thanks!
It should be fixed month ago but you need routes-2.6.10-12.diff.
Another option is to remove the fib_result_table "__inline__" from
include/net/ip_fib.h
> BR,
> Dominic Lu
Regards
--
Jul
gt; make[3]: *** [fib_frontend.o] Error 1
> make[3]: Leaving directory `/usr/src/linux/net/ipv4'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux/net/ipv4'
> make[1]: *** [_subdir_ipv4] Error 2
> make[1]: Le
howtos:
http://www.ssi.bg/~ja/#routes
> Tks A LOT for the response!
> Fernando Favero
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
gument".
> I don't know why it fails. I have a 2.4.20 kernel with Julian Anastasov's
> patches. iproute2 version ss010824.
Better use latest versions of iproute2.
> I really need the solution to this issue. Please help me :(
> Thanks in advance
Regards
--
Julian Anasta
>
> -Martin
>
> [0] http://www.ussg.iu.edu/hypermail/linux/kernel/0002.1/1522.html
> [1] http://open-source.arkoon.net/kernel/kernel_net.png
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
egative offset of -8 that should based on what I've read be the source
> mac address. I've been plating around with it, but no success yet.
>
> Any help would be much appreciated.
http://mailman.ds9a.nl/pipermail/lartc/2003q1/006663.html
> Thanks,
> Gerry
Rega
, device is
registered/unregisterd, etc.
> Regards,
> Reza
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
On Wed, 7 Jul 2004, Glen Mabey wrote:
> I'm sure that I had found (and printed out ...) a really good tutorial
> that explain how to use Julian Anastasov's routing patch, but I can't
> seem to find it now.
>
> Any pointers?
http://www.ssi.bg/~ja/
correct rules. For example:
- know which IP or subnet can use particular uplink. I do not see
specific 'from' ip rules for sources such as 24.201.150.222 and
24.201.150.250. May be each of them can use only its modem?
You must know which table will be used for each source address
and t
think 4 cable modems is too much, has it been tested ?
I do not remember how many nexthops allows the ip utility for
multipath routes but 16 should be possible.
> Help with this case would really be appreaciated, I am ready to give
> any details that w
d one in 2 links version. Now I'm using slightly extended
> version for 4 links with policy routing :)
Thank you, it is now linked. May be in the following days
I'll try to create advanced version.
> http://mailman.ds9a.nl/pipermail/lartc/2003q4/010372.html
R
oot]# ip route list table DEF
> default proto static
> nexthop via 172.16.0.1 dev eth0 weight 1
> nexthop via 192.168.0.1 dev eth1 weight 1
>
> with this configuration i still couldn connect to internet
From where? What shows tcpdump -ln ... ?
> regards
> reza
Regards
7; commands and
"2.4 Keeping them alive" from nano.txt. Make sure after upgrading
iproute2 that your nexthops are not dead. Also, list you rules
and routes and make sure they are valid, I see your commands but
I do not know which of them are accepted from the kernel
sult with early versions of linux kernel
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
P2, and then the SMTP server of ISP1 refuses
> to accept my message.
>
> So I would like to "tie" SMTP traffic to ISP1 line. What rules should
What about
/sbin/ip rule add prio 80 to $SMTP_IP table 201
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
--------
> Tushar Thakker
> Elitecore Technologies Ltd.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
On Thu, 8 Jan 2004, hare ram wrote:
> [EMAIL PROTECTED] patch -p1 <
> /root/update/update/routes-2.4.20-9.diff
What happens with routes-2.4.22-9.diff ?
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LAR
Hello,
On Fri, 12 Dec 2003, Antony Lesuisse wrote:
> So the problem is how to bypass the lookup in the table shown by:
> ip route show table local
http://www.ssi.bg/~ja/#loop
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
_
blem
> Thanks in advance.
>
> Marcelo.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
ems) you
want packets with saddr=DynIP to walk the external path and
to reach GOOD. Is it needed? Is there a problem with the above
solution in #1?
> Regards,
> Christian
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing
hen saddr=local_IP, the preferred
src IP must be local IP.
> I'm sorry if this question has been asked over and over again, but I
> have googled and looked into the archives but haven't found a solution
> that fits my needs.
>
> Best regards,
> Christian
Regards
--
Julian
n
this way: the NAT connection requests route with saddr=the external
IP address attached for this connection. As result, the multipath
route is avoided and the traffic for one connection is bound to
one ISP (usually): http://www.ssi.bg/~ja/#routes
> any insight of t
MAC in this way:
ip arp add table output to 1.2.3.4 lldst 00:11:22:33:44:55
> : Do de ip stack understand this "unicast" arp request?
Yes but at MAC level the ARP code cares only for
unicast/broadcast, no matter the actual dst MAC of the received
packet.
when using only "nexthop dev pppX"
This command should return error, missing "via" before GWIP:
> ip route add default table 222 proto static \
> nexthop via 217.5.98.12 dev ppp0 weight 1\
> nexthop 217.5.98.12 dev ppp
egards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
ase,
I created patch to upgrade to HTB 3.10
> Regards.
>
> Gordan
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Edge31-ca-u32 from the iproute2 examples, there are some ideas
about using policers. As for DS9, it tries to provide the same
interface to all qos objects as in 2.4, so it is possible to do
the same things as in 2.4, of course, there is one problem, nobody
wants to support new features in 2.2
he flush leads to
much more problems (CPU cycles for rerouting) compared to 2.4.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
keep each traffic through its ISP.
Read nano.txt from http://www.ssi.bg/~ja/#routes
It is for 2.4 but the concept and the routing rules are same.
> TIA.
>
> Gordan
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
://www.ssi.bg/~ja/
The old URL is still maintained but as mirror, not under
my control, may be it is now back as redirect
(http://www.linuxvirtualserver.org/~julian/) to the primary site.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
the interfaces and gateways you want:
http://www.ssi.bg/~ja/#iparp
ip arp add table output from 17.70.0.1 src 0
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
cept ARP from valid source IP from valid input device".
> Have I overlooked something in my setup or should I start poking in the
> kernel ARP code?
Take a look at arp_solicit()
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
s not enough.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
f
> rtmasq-2.4.20-2.diff
Use rtmasq-2.4.20-routes9-2.diff instead, I just uploaded it.
Apply it after routes-2.4.20-9.diff and let me know offline if it
compiles and works.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mail
> table ppp0 right?
> in such case the, nat, why may be nat not being applyed?
> cause it doesnt work at all..it goes to that interface but does not nat
> the src address of the package.
> any idea?
It is not supported but there is a patch:
http://www.ssi.bg/~ja/#rtmasq
R
raffic). "Invalid argument" is a good
indication for this :) This is one of the drawbacks I already
mentioned.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
gt; works.
May be there are some collisions. But if "equalize" works
for balancing your ISPs then you don't need the "routes" patches.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL
n is bound to its allowed path(s), no matter how many interfaces
are used. Selecting different nexthop should be allowed only if
it is alternative allowed from the routing rules.
> There shouldn't be problem what I read in this article.
Then why you see traffic to the wrong gateway?
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
nexthop and you can not notice it, this mistake is visible
on device output.
> So that I am confused on this packet traversing.. Could someone explain
> this behaviour ? Is it OK or I have missed something ?
You can read about such issues, use the above URL
> Regards,
> tw
> --
&g
spoofing check for all
interfaces". include/linux/inetdevice.h is a good source for
information about whether 0 or 1 as value for all/XXX changes
globally the feature for all interfaces. For rp_filter it is 0,
for send_redirects it is 1.
Regards
--
Julian
'ptr'
is adjusted by signed int offsets, so it can touch lower addresses.
> Thus we can at least say that negative offset in u32 are really "tricky"
> and really non clean and as seems to show experiment that they don't
> work (?)
This is a hac
ode at -2.
The filter's "protocol XXX" uses skb->protocol which is built
from the eth proto code for eth devices (returned from eth_type_trans).
So, "protocol ip" is ETH_P_IP, "protocol arp" is ETH_P_ARP and so on.
See the "llproto_names" array in iproute2 (li
at -2 match u32 0x22334455 0x at -12 match u16
0x0011 0x at -14
Ingress:
... match u16 0x0800 0x at -2 match u16 0x4455 0x at -4 match u32 0x00112233
0xFFFF at -8
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
to Ping or go out from My gateway IP
> i can only Ping my Gateway IP's
Check the settings again.
> thanks
> hare
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
/ip-routing/iproute2-2.4.7-now-ss020116-try.tar.gz
> is this Corect or i need to still upgrade
> if so, i did not find latest than this
You can always list the above directory for latest tarballs
> thanks
> hare
Regards
--
Ju
ht 256 dead onlink pervasive
> nexthop via 203.x.x.17 dev eth1 weight 1
This smells like one iproute utility bug, just upgrade to iproute2
from Year 2002 which fixes similar problem.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
the IP header:
Decimal Ofs Description
---
-14:DST MAC, 6 bytes
-8: SRC MAC, 6 bytes
-2: Eth PROTO, 2 bytes, eg. ETH_P_IP
0: Protocol header (IP Header)
> search through the various
> netfilter extensions - you
able main:
194.149.216.0/24 dev vlan2 scope link
> Luis Miguel Cruz Miranda.
> CCNA - Systems Administrator
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Y (table A)
from 0/0 to B => DEV X (table main)
You need to inspect the main table first.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
o the configured local IP:PORT but this
service can obtain the original DADDR:DPORT of the packet.
> Nickola
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
ses saddr=0.0.0.0 daddr=REMOTE_IP.
> > The routing then returns the best source IP to use for this connection
> > after creating a connected route in the routing cache.
> What do you mean by "unbound socket" ?
socket(), connect(), i.e. when there is no bind() to
te lookup (ignoring the fact that this
UDP packet has known saddr in iphdr). So, it depends both on
transport and on app to feed the routing with the right keys.
> Vincent.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
g to do when addresses to both ends are known is
to feed the routing with saddr and daddr. If callers use 0.0.0.0
as saddr when resolving routes, they will hit the multipath
route which is bad.
> Has anyone already experiencing such setup ?
Not exactly, but every
No, dead gateway detection currently works for routes with
same metric. But even then the detection is passive and needs help
from user space. Without such checks you can expect almost random
results. OTOH, you can run your own checks and to keep only the
alive routes.
n the route cache entries.
> Can somebody confirm (as the evidence suggests) that the routing cache is
> keyed on the above five elements?
Yes, this is my understanding reading the sources
> -Martin
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
The patches are designed to work with rp_filter enabled.
You can safely use it, it is changed to work only with the defined
paths.
> Thanks again.
> Vincent.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTEC
oesn't work when doing
> NAT.
May be you can hunt it with tcpdump. I assume your are
using the patches because the plain kernel has the same problem
for NAT.
> A big thanks to both of you. I've learned a lot today :)
>
> Thanks again.
> Regards,
> Vincent.
0x1C, inverted 0xE3
2.2 mask 0x1E, inverted 0xE1
So, for 2.2 may be:
ipchains -I input -d 0.0.0.0/0 22 -t 0xE3 0x00
What are the TOS values used during the SSH session?
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
as default (or to use alternative default gateways).
Another solution is your apps not to change the TOS, it can be
changed at the border gateways (if useful at all).
> Am I right ? I'm becomming a bit lost, here :-\
>
> Many Thanks for your time.
> Vincent.
Regards
--
Julian
mply can't do this if the ISPs have
source spoofing disabled. In such cases only the traffic that
is NAT-ed from your box has the right to use the multipath route.
This is a key requirement for the patches you are using. Once
the NAT connections are established they don&
Hello,
On Wed, 23 Oct 2002 [EMAIL PROTECTED] wrote:
Ops, is that correct?:
> ipchains -A fw -s 0.0.0.0 -d 0.0.0.0 -j ACCEPT
it should be
ipchains -A fw -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT
Regards
--
Julian Anastasov <[EMAIL PRO
e never observed deviations from
the 2.4 behavior. It would be good if you can compare the same
settings on 2.4.20pre.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
On Tue, 15 Oct 2002 [EMAIL PROTECTED] wrote:
> OUTPUT : " HTB: need tc/htb version 3 (minor is 6). you have 10.
My mistake, what about trying the 3.6 code:
http://luxik.cdi.cz/~devik/qos/htb/v3/htb3.6-020525.tgz
Regards
--
Julian Anastasov <[EMAI
2.2, use one of the above two
methods.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
ow can one achieve **owner** based policy routing in linux
> box ??
This is something that others should comment. NF is
supposed to do everything :)
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTEC
ere 50 is 0x32 (not 0x50). Is that the problem?
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
ent traceroute versions have this problem fixed.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> #echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter# 1
> #echo 0 > /proc/sys/net/ipv4/conf/eth2/rp_filter# 1
> The gc_timeout seems to be a timeout between gc's?
this is gc_interval
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
__
rotocol.
I see it in this way: when such packet is received, we
decapsulate it and place it on the expected interface. As
result, the upper layers will see the packet on the right
input interface even if it is received on another input
interface (for example, if it is the o
n play with br0 if ipmode is off.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
usr/src/linux patched with
bridge-ipmode-2.4.19-2.diff, the user-space stuff is not enough.
> Any Clue?
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
On Tue, 10 Sep 2002, Thad Marsh wrote:
> Can some one point me to a reference for how to route two wan nics and
> two internal nics on the same box.
Here you can find some documents and patches on this issue:
http://www.ssi.bg/~ja/#routes
Regards
--
Julian Anastasov &
u have to upgrade to iproute2 package released this year.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
; May I post the script I used to try this out?
Or if possible to provide reference to it after the 5th
reading of all docs :)
> Thanks, folks!
>
> Calvin Dodge
> Certified Linux Bigot (tm)
> http://www.caldodge.fpcc.net
Regard
is not used only as "default" rule. So,
playing tricks with different gateways is not possible. The
setup is ambiguous if NAT is involved.
> A.H
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
(even the good ones :)).
Any bugfixes and comments can be posted directly to me or
to the LARTC and/or DiffServ mailing lists.
Have fun!
DS-9 - QoS Backport from 2.4.19 to 2.2.21:
http://www.ssi.bg/~ja/ds9/
Changes between DS-8 and DS-9:
http://www.ssi.bg/~ja/ds9/Changelog.ds9
Regards
ide my "DS-9" tree to anyone interested in
testing and hosting the files.
> Regards,
> Amit
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
at are reachable from this
link.
> what other things i have to consider ?..
As for applying the patches you need to download them
correctly. More likely you have white space problem (try with
patch -l).
> Awaiting a reply very very anxiously..
> A.H
Regard
ly the routes administratively
marked as such. This is the current way.
> Thanks,
>
> --
> Laurens van Alphen
> Keen on dots
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
On 31 Jul 2002, William L. Thomson Jr. wrote:
> two things. The first is patches made by Julian Anastasov,
> I had a link but it does not seem to work. Julian subscribes to this
> list so maybe he will post an updated link to where they can be found.
The box t
have to recreate
the route because when one ppp devices is registered again its
nexthop status does not change, it remains dead.
> Thanks
>
> Tobias
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
erent tables, cause this seems not
> to do failover
Yes, similar behavior appeared in latest 2.4.19pre kernels,
it looks like a recommendation the users to recreate their routes
because a device in nexthop was unregistsred. Is this true for
your setup?
Regards
--
Julian Anastasov &l
o add ipchains support for tc
in addition to the iptables' one. My wish was to have only the
needed bugfixes :)
> cheers,
> jamal
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
rtualserver.org/~julian/01_ingress-breaks-fw-1.diff
At least, FW_REDIRECT, not sure for any others
> cheers,
> jamal
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
know of any place where these differences are
> explained clearly.
Huh. I don't want to start new howto :)
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
able to build correct routing rules for your
setup.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
if you somewhere use fwmark in ip rules, the fwmark
there is again in hex. Make sure all values match according
to their representation, i.e. 20 in dec is different from
20 in hex.
> If anyone has any suggestions, they are most welcome.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]&
e detected as dead.
This bug is fixed in iproute2 package from this year.
Fetch the latest archive.
Regards
--
Julian Anastasov <[EMAIL PROTECTED]>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
ltipath route because if we register the same device name,
the nexthop will not switch from dead to alive. So, for 2.4 (I'm
not sure how the behaviour will change in 2.5 later) the
kernel removes the multipaths but note that we (the users)
always have to recreate the multipa
1 - 100 of 121 matches
Mail list logo
