From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Routing Multiple Inbound IP Addresses -- How?
Date: Tue, 29 Nov 2005 12:03:10 -0500 [thread overview]
Message-ID: <002101c5f506$c73d0100$6901a8c0@QUARK> (raw)
In-Reply-To: <20051129132437.GJ23546@rednote.net>
Aha, I got you.
Ok, I need to look at iptables rules, since I'm not up on them, but yes ...
This is possible.
Basically, what you want to do is have a gateway to more than one IP. This
is the inverse of a multicast IP which sends information that it receives to
multiple IP's, you sore of want it the other way ... Multiple IP's get
information but they go to a central location; however, you want to retain
the information of which IP it was sent to.
Now, I do have one question still. You do want to use NAT, correct? So at no
point in time do you want these computers to have public IP's? except of
course for your gateway ... Is that correct?
The reason I ask this is because it's the difference between talking about
pass throughs, and talking about redirection.
Take care,
Sina
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Janina Sajka
Sent: Tuesday, November 29, 2005 8:25 AM
To: Speakup is a screen review system for Linux.
Subject: Re: Routing Multiple Inbound IP Addresses -- How?
Hi, Sina:
Didn't remember the term multihoming. I'll check that out.
So, here's my situation. My ISP provides me multiple ip addresses, if I want
them. I want to take advantage of that in a way I think is appropriate. It
would be easy if I just used the external, routable ip addresses
directly--one for each machine perhaps.
But, I want to keep my internal, nonroutable scheme intact. For one thing, I
have more machines than routable addresses. For another thing, I'd like the
freedom to use the routables by function, rather than specific machine,
meaning that I might migrate internally from one machine to another at some
point, without changing the externals.
So, how do I do that NAT? Let's say I have four IP addresses. They're
discontinguous. Internally, I have seven or eight machines (depending on the
day).
Here's what I know I can do. I can route traffic arriving on address A port
80 to machine A-Prime port 80, and route traffic arriving on address B port
80 to machine B-Prime.
But, can I route traffic arriving on address C, whatever port, to machine
C-Prime? Without specifying all the particular ports one at a time? Or as
some kind of gargantuan range like 1-32767?
Sina Bahram writes:
> Hi Janina,
>
> Can you provide a little more information.
>
> When you say over your dsl, do you mean that your dsl modem is going
> to be assigning more than one IP address to you? If so, then you're
> wanting something like multihoming, although if you want to pass those
> IP's along, as you said, they are routable ... Then that's a different
situation.
>
> Could you explain the specifics in greater detail please?
>
> Take care,
> Sina
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca
> [mailto:speakup-bounces@braille.uwo.ca]
> On Behalf Of Janina Sajka
> Sent: Monday, November 28, 2005 10:12 PM
> To: speakup@braille.uwo.ca; ma-linux@tux.org;
> blinux-list-bounces@redhat.com
> Subject: Routing Multiple Inbound IP Addresses -- How?
>
> This is fairly basic, I'm sure. But, for the life of me, I can't find
> documentation on it.
>
> So, here's the situation ...
>
> I have several routable IP addresses. All of them need to come through
> the same interface, over my DSL to be specific. So, how can I route
> based on IP alone? I know how to route by port, but how do I do it by IP
address?
>
> All examples/help much appreciated.
>
>
> --
>
> Janina Sajka Phone: +1.240.715.1272
> Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
>
> Marketing the Owasys 22C talking screenless cell phone in the U.S. and
> Canada--Go to http://www.ScreenlessPhone.Com to learn more.
>
> Chair, Accessibility Workgroup Free Standards Group (FSG)
> janina@freestandards.org http://a11y.org
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
Janina Sajka Phone: +1.240.715.1272
Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
Marketing the Owasys 22C talking screenless cell phone in the U.S. and
Canada--Go to http://www.ScreenlessPhone.Com to learn more.
Chair, Accessibility Workgroup Free Standards Group (FSG)
janina@freestandards.org http://a11y.org
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Sina Bahram
` Travis Siegel
` Janina Sajka
` Sina Bahram [this message]
` Gregory Nowak
` Janina Sajka
` Janina Sajka
` Gregory Nowak
Dawes, Stephen
` Janina Sajka
Dawes, Stephen
` Ralph W. Reid
` Janina Sajka
` Jim Kutsch
` Janina Sajka
` Gregory Nowak
` Janina Sajka
Dawes, Stephen
` Janina Sajka
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='002101c5f506$c73d0100$6901a8c0@QUARK' \
--to=sbahram@nc.rr.com \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).