RE: funny ECMP

Dear Li,

nice to hear from you.

1st: i have send in a bugfix:
http://www.freebsd.org/cgi/query-pr.cgi?pr=149917


I have changed the route selection code of ecmp to
balance only between routes of the same weight.
(see attached file)

As Qing Li mentioned months ago, there are problems with static routes
and interfaces.


Do you have the exact link to the email thread?
There were no pending ECMP related issues since my last round of
commits
as far as I can remember.

http://lists.freebsd.org/pipermail/freebsd-net/2010-January/024420.html
http://lists.freebsd.org/pipermail/freebsd-net/2010-February/024539.html

Example 1:
ifconfig em1 alias 10.13.13.90/24
ping 10.13.13.95 ok
route add 10.13.13.0/24 10.11.11.1 -weight 2
ping 10.13.13.95 broken (arpresolve: can't allocate llinfo for
10.13.13.95)


Could you please explain a bit on exactly what you try to
accomplish here with this configuration?

rebuilding my core-routers.
it's a very special setup:

2 redundat core routers, connected via ospf (quagga),
vrrp to server-side.
currently I use a very modfied ucarp version because freebsd 6 only allows on route.
problem is with standard freebsd and carp, that there is at the failover router a via ospf received route to the server-side interface. when now carp tries to add the route during failover, it fails. and seconds later the ospf route times out.

so, i hoped to use carp, quagga and freebsd ecmp to be able to avoid this problems now.
so I need route-merics (weights?) to prefer direct interface routes (connected) before static ones.
perhaps I also need to change quagga to send also the merics to the kernel, as in differnce to, for example, cisco router, connected and static routes have the same weight.

deleting the last static multipath routes seems to affect?, destroy?
the interface route.
system crashes in:
/usr/src/sys/net/route.c:370
rn = rnh->rnh_matchaddr(dst, rnh);
if (rn && ((rn->rn_flags & RNF_ROOT) == 0)) {
newrt = rt = RNTORT(rn);
here -> RT_LOCK(newrt);
RT_ADDREF(newrt);
if (needlock)


I will take a look.

thanks.

Kind regards,
Ingo Flaschberger

_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Cant send packets via WiFi (possibly route issue)
    ... I think that this WiFi device should route all ... it should *all* be routed to the eth1 interface. ... Wireless is much like a point-to-point link using ... The connection between the two networks is the "Wifi AP". ...
    (comp.os.linux.networking)
  • RE: Running public IPs inside an RFC 1597 network
    ... > I'm running a typical Class C RFC 1597 network in my lab. ... know or care if we humans designate a subnet as public or private. ... is the absolute most general route there is for a machine. ... In a correctly configured system when you define an interface, ...
    (freebsd-questions)
  • Equal cost paths from separate OSPF Processes
    ... the network statements are valid in all OSPF processes. ... interface Serial0.300 point-to-point ... router#sh ip route ospf ... connected, includes subnets in redistribution ...
    (comp.dcom.sys.cisco)
  • Re: [patch] Problem with two NIC on same NET (in_scrubprefix: err=17, new prefix add failed)
    ... route) is going down, then the network route is replaced by network ... route of the other interface and everything is OK. ... So, at least, a loopback route is installed ...     I need to run some tests on your patch, but keep in mind the LLE_STATIC is sort overloaded ...
    (freebsd-current)
  • Re: panic in rt_check_fib()
    ... It dropped a the lock on one route while it went off an did something ... then brings up the wired interface of my laptop. ... echo '## Bringing up network interface.' ... With your version of rt_check_fibI have no panics so far. ...
    (freebsd-current)