All of lore.kernel.org
 help / color / mirror / Atom feed
From: wyonker@dcsnow.com wyonker@dcsnow.com
To: lartc@vger.kernel.org
Subject: [LARTC] Masquerading under 2.4
Date: Fri, 12 Jan 2001 01:51:54 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416862@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416855@msgid-missing>

<PRE>Here is the final piece to my puzzle.  I'll buy someone a beer if they 
can help me with this.

I have two connections to the internet.  I would like all traffic on port
27015 to go out on the 2nd connection (which is eth1 on the router) 
and
all traffic from one client also.  Oh and I would like to force all
traffice going to specific hosts (myisp.com and myisp2.com) to go 
over
their respective interfaces because they block traffic from anywhere 
else.

Now, to do the part with the client I can just do the following right?

echo 200 John &gt;&gt; /etc/iproute2/rt_tables
ip rule add from 10.0.0.10 table John
ip route add default via 195.96.98.253 dev ppp2 table John
ip route flush cache

I copied that from the advanced routing Howto.

So can I just add the port to the 'ip rule add' line? Like this?

ip rule add from 10.1.1.10:27015 table John

As always, any help would be appreciated.

On 11 Jan 2001, at 10:12, Willis Yonker wrote:

&gt;<i> Hello all,
</I>&gt;<i> 
</I>&gt;<i> I just got the 2.4.0 kernel and built in masquerading into the kernel
</I>&gt;<i> (not as a module).  When you do that, it takes away the option to act
</I>&gt;<i> as ipchains did in 2.2.
</I>&gt;<i> 
</I>&gt;<i> Okay, that's fine with me.  I just have no idea how to setup
</I>&gt;<i> masquerading (or for that matter port forwarding either) using the 2.4
</I>&gt;<i> way.  Can someone point me to some documentation I can use to
</I>&gt;<i> acomplish this?
</I>&gt;<i> 
</I>&gt;<i> Thank you for your help.
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> _______________________________________________
</I>&gt;<i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>&gt;<i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO:
</I>&gt;<i> <A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</I>



</PRE>

  parent reply	other threads:[~2001-01-12  1:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 14:45 [LARTC] Masquerading under 2.4 Arthur
2001-01-11 15:12 ` Willis
2001-01-11 20:12 ` wyonker
2001-01-11 21:30 ` Arthur
2001-01-11 22:47 ` wyonker
2001-01-12  1:51 ` wyonker [this message]
2001-01-12  9:51 ` Arthur
2001-01-13  0:37 ` wyonker

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-98373940416862@msgid-missing \
    --to=wyonker@dcsnow.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.