From: Stephen Hemminger <stephen@networkplumber.org>
To: Asi Lichtenstein <asili22@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: How to add IPv6 multiple routing tables support to 2.6.16.26 kernel
Date: Sat, 4 Jan 2014 13:34:17 -0800 [thread overview]
Message-ID: <20140104133417.5d67c179@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAMBtn_2fjONQk0aO6MBy3j9X__78CTon_aYzJWCjouKnZDXEMw@mail.gmail.com>
On Thu, 2 Jan 2014 15:24:34 +0200
Asi Lichtenstein <asili22@gmail.com> wrote:
> Hi there,
>
> I need to add such support.
> How would you recommend me adding such support?
>
> Is there a patch I could use?
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
First, 2.6.16 is 8 years old.
Second, by now there are 100's of known vulnerabilities; such a system
would be a sitting duck for remote exploitation.
Third, multiple route tables in Linux was implemented much earlier
than that, back in the 2.4 development. It is probably in the 2.6.16
kernel. Most likely the vendor config or tools you have are broken
and don't allow access to it.
next prev parent reply other threads:[~2014-01-04 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 13:24 How to add IPv6 multiple routing tables support to 2.6.16.26 kernel Asi Lichtenstein
2014-01-02 13:26 ` Fwd: " Asi Lichtenstein
2014-01-02 18:27 ` Ben Hutchings
[not found] ` <CAMBtn_3OnZWZdSWHN3sg0jwG74mUWprNO+H9gE9tDgRO-j2f3g@mail.gmail.com>
2014-01-02 20:06 ` Asi Lichtenstein
2014-01-02 22:25 ` David Miller
2014-01-04 21:34 ` Stephen Hemminger [this message]
[not found] ` <CAMBtn_3gFon_Qdrnwfxpo8mXtK502hLDBQc9hf8_RFYLpfcSuA@mail.gmail.com>
[not found] ` <CAMBtn_0TGndWf4zv783qEBe8YHWK6g0a_=QM_JoneavX7f3RTQ@mail.gmail.com>
2014-01-05 11:33 ` Asi Lichtenstein
2014-01-05 13:25 ` François-Xavier Le Bail
2014-01-05 13:49 ` Asi Lichtenstein
2014-01-05 13:56 ` François-Xavier Le Bail
2014-01-05 14:09 ` Asi Lichtenstein
2014-01-06 8:56 ` Asi Lichtenstein
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=20140104133417.5d67c179@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=asili22@gmail.com \
--cc=netdev@vger.kernel.org \
/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