netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andre Tomt" <andre@tomt.net>
To: <netdev@oss.sgi.com>
Subject: unable to add ipv6 default route in 2.4.21-rc1 + latest bkbits.net pieces
Date: Fri, 2 May 2003 20:25:11 +0200	[thread overview]
Message-ID: <002001c310d8$2bb57b00$0a01ff0a@slurv> (raw)

Hi,

I noticed a problem on one of our semi-production systems today, it
suddenly lacked a working ipv6 default route. After further
investigation, even the raw iproute commands failed (I had it all set up
in /etc/network/interfaces, a debian network configuration file).

It seems to me something changed in 2.4.21? It certainly broke my
iproute. 2.4.20 works fine (well, with many fixes not related to ipv6).
iproute is debian version 20010824-9 (from unstable/sid).

kvass:~# ip -6 route add default via 2003:730:f:3:: dev eth0
RTNETLINK answers: Invalid argument

and for good measure:
kvass:~# ip -6 route add 2000::/3 via 2003:730:f:3:: dev eth0
RTNETLINK answers: Invalid argument

2001:730:f:3::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss
1440
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440
ff00::/8 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440
unreachable default dev lo  proto none  metric -1  error -101

kvass:~# ip -6 route
2001:730:f:3::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss
1440
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440
ff00::/8 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440
default dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440
unreachable default dev lo  proto none  metric -1  error -101

Theres a defaultroute there pointing to eth0 with noe gw set, that seems
to be some kind of, err, default. Removing it and (trying, in this case)
adding a proper default route has no effect. I even tried to recompile
iproute, but that gave the same symptoms. Not sure if dpkg-buildpackage
actually buildt it against /usr/include/linux or
/usr/src/linux/include/linux though.

Any ideas? I know there have been some deal of ipv6 fixes and additions
going into 2.4.21, did this break something?

-- 
Cheers,
André Tomt
andre@tomt.net

             reply	other threads:[~2003-05-02 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 18:25 Andre Tomt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-02 21:38 unable to add ipv6 default route in 2.4.21-rc1 + latest bkbits.net pieces Andre Tomt
2003-05-04  9:21 Andre Tomt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002001c310d8$2bb57b00$0a01ff0a@slurv' \
    --to=andre@tomt.net \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).