All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Need some advice
Date: Tue, 25 Mar 2003 17:25:24 +0000	[thread overview]
Message-ID: <marc-lartc-104861333321516@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98414767107466@msgid-missing>


Jesper....

(Sorry for brief reply...work, work, work...)

Try something like this

# echo 5 icecast >> /etc/iproute2/rt_tables
# ip rule add from $ETH1_IP table icecast
# ip route add default via $ETH1_GW table icecast

Does that make sense?

Read up on it here:

  http://linux-ip.net/html/routing-tables.html
  http://linux-ip.net/html/routing-selection.html

Good luck,

-Martin

 : Greetings!
 :
 : I've been struggling for a few days now with something that gives me a
 : headache 'cause I'm not really an iproute expert, nor even an advanced
 : user. I've browsed through the archives, HOWTO's and such but didn't pick
 : up anything particularily useful to help me with my little problem.
 :
 : I have two network cards installed on a single RedHat8 Linux (2.4.18-14)
 : box, each interface has it's own dedicated IP address, both have the same
 : mask and gateway. Now, what I'm trying to do is dedicate eth1 to icecast (a
 : stream server) only, so that any other outgoing/incoming traffic (HTTP,
 : FTP, SSH, ICMP etc) would use eth0.
 :
 : I managed to set up my firewall (with fwbuilder, iptables) so that only
 : icecast answers on eth1 and the rest of the allowed services on eth0. But
 : clearly whether you connect to http on eth0 or icecast on eth1, there is
 : traffic only on eth1 (at least when you look at "netstat -i" or Tx_Bytes &
 : Rx_Bytes in /proc/net/PRO_LAN_Adapters/eth*.info). That's probably because
 : "ip route ls" shows that Red Hat has set eth1 as my default gw.
 :
 : So.. I guess what I'm asking is what would the right "ip" commands be
 : that'd allow me to set up my routes in such a way that would make all this
 : possible? .. and moreover, how do I get Red Hat scripts not to mess with
 : those settings.. ;-)
 :
 : Thanks in advance! Excuse me if my explanation is not very clear, too much
 : monitor tan for today.
 :
 :
 : _______________________________________________
 : LARTC mailing list / LARTC@mailman.ds9a.nl
 : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
 :

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

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

      parent reply	other threads:[~2003-03-25 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 14:15 [LARTC] Need some advice Krepper Guillermo Billy
2001-03-09 14:54 ` Arthur van Leeuwen
2003-03-25 17:11 ` Jesper Johnson
2003-03-25 17:25 ` Martin A. Brown [this message]

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-104861333321516@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --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.