network routing

"William Tasso" <SpamBlocked RemoveThis @tbdata.com> wrote in message
news:op.srmeutvtm9g4qz-wnt@tbdata.com...
 > Greetings one and all.
 >
 > I've been staring at this too long and it's now a blackhole for all
 > creative thought.
 >
 > Consider this schema ....
 >
 > Internet - Router - Network(A) - Firewall - Network(B,C)
 >
 > Notes:
 > o Internet feed provides 128 public IP-Addresses.
 > o Router is a linux box.
 > o Networks (B) and (C) can use a subset(s) of available IP-Addresses.
 >
 > Q: How to configure the router so that it knows how to route traffic to
 > hosts on Network(B)&(C)
 >

Well I'm not a network guru and I may be looking at this too simply but it
sounds like you may be looking for NAT (Network Address Translation)
<a style='text-decoration: underline;' href="http://www.vicomsoft.com/knowledge/reference/nat.html" target="_blank">http://www.vicomsoft.com/knowledge/reference/nat.html</a>

Just thought it might be worth mentioning.

Neil<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: network routing 

From the relative comfort of the boardroom, <neilr DeleteThis @NOSPAMpages-uk.com>
patched in a new connection to news:alt.www.webmaster and said:

 > ...
 > sounds like you may be looking for NAT (Network Address Translation)
<font color=purple> > <a style='text-decoration: underline;' href="http://www.vicomsoft.com/knowledge/reference/nat.html</font" target="_blank">http://www.vicomsoft.com/knowledge/reference/nat.html</font</a>>
 >
 > Just thought it might be worth mentioning.

Thanks, it's a possiblity I hadn't considered - it's planned that all the
hosts will use public IPs.

--
Whatever you do - do something.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: network routing 

"William Tasso" <SpamBlocked.RemoveThis@tbdata.com> wrote in message
news:op.srmrrkabm9g4qz-wnt@tbdata.com...
 > From the relative comfort of the boardroom, <neilr.RemoveThis@NOSPAMpages-uk.com>
 > patched in a new connection to news:alt.www.webmaster and said:
 >
  >> ...
  >> sounds like you may be looking for NAT (Network Address Translation)
<font color=green>  >> <a style='text-decoration: underline;' href="http://www.vicomsoft.com/knowledge/reference/nat.html</font" target="_blank">http://www.vicomsoft.com/knowledge/reference/nat.html</font</a>>
  >>
  >> Just thought it might be worth mentioning.
 >
 > Thanks, it's a possiblity I hadn't considered - it's planned that all the
 > hosts will use public IPs.

Wow - I was surprised to see you asking this question, given how much help
you were with this stuff when I needed it a few months ago.

It seems to me that NAT should work whether the IPs were public or private,
as long as the router can see the machine it's routing to.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: network routing 

Tony wrote:

 > It seems to me that NAT should work whether the IPs were public or private,
 > as long as the router can see the machine it's routing to.

Yep. NAT can work with either public or private IP addresses -- or even a
combo of them.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me ~ <a style='text-decoration: underline;' href="http://tobyinkster.co.uk/contact" target="_blank">http://tobyinkster.co.uk/contact</a><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: network routing 

Toby Inkster wrote:
 > Tony wrote:
 >
 >
  >>It seems to me that NAT should work whether the IPs were public or private,
  >>as long as the router can see the machine it's routing to.
 >
 >
 > Yep. NAT can work with either public or private IP addresses -- or even a
 > combo of them.
 >
NAT works great on outgoing traffic. But it doesn't work well on
incoming. He could use NAT on network A, but not B and C (since he
wants to route TO these networks).

The correct solution is to set up IP forwarding on the firewall with
subnet masks pointing to B and C (assuming they are on different NICs).
Or, if they're on the same NIC, just IP forwarding will do.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex.DeleteThis@attglobal.net
==================<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: network routing 

From the relative comfort of the Chaos boardroom, <SpamBlocked.DeleteThis@tbdata.com>
patched in a new connection to news:alt.www.webmaster and said:

 > ...
 > Internet - Router - Network(A) - Firewall - Network(B,C)

Gentlemen, I thank you all for contributing.

The solution is fairly trivial (I did mention the black hole draining all
creative thought) - a real 'Networking 101' moment.

Firewall is now configured in bridging mode and the world is once again
full of happy smiley servers.

--
Whatever you do - do something.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: network routing