All of lore.kernel.org
 help / color / mirror / Atom feed
From: carlosh@echos.co.nz
To: lartc@vger.kernel.org
Subject: [LARTC] Official RH kernel documents, and load balancing
Date: Mon, 22 Sep 2003 21:09:51 +0000	[thread overview]
Message-ID: <marc-lartc-106426463629736@msgid-missing> (raw)

Hi:


I have an 'advanced-networking' problem. I want to have two interfaces to
the internet, apart from the internal one to the LAN.

I came across this page:
http://www.redhat.com/mirrors/LDP/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.multipl
e-links.html


and Julian's patches for the kernel published here:
http://www.ssi.bg/~ja/
and the How-to: http://www.ssi.bg/~ja/nano.txt


So, I downloaded the patch:

routes-2.4.22-9.diff (December 14, 2001), and applied it to my 2.4 kernel...


The kernel re-compile part was fine, following the instructions in :

http://tldp.org/HOWTO/Kernel-HOWTO/


The issue is when I have to create a new initrd file.. it appears to create
a vmlinuz, not a bzImage as the kernel-howto document says.


So the new kernel does not boot...


Questions:

Have anyone done this?

I mean, having two connections to the Internet, using RH8.0 or RH 9.0, and
having them selecting (balancing) which interface to use to send packets
out, and receiving in either seamlessly and with NAT ?

I think this functionality should be built in and available, instead of
having to patch the kernel?

What would you guys recommend?


As for the initrd part, any suggestions? Is there an official RedHat
"re-build kernel" document?



Thanks before-hand,

Carlos
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-09-22 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 21:09 carlosh [this message]
2003-09-23  0:36 ` [LARTC] Official RH kernel documents, and load balancing Alex
2003-09-23  1:00 ` Daniel Chemko

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=marc-lartc-106426463629736@msgid-missing \
    --to=carlosh@echos.co.nz \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.