Bluehost.com Web Hosting $6.95

NAT question

This is a discussion on NAT question within the Linux Networking forums, part of the Linux Forums category; I am trying to set up my NAT box to permit CORBA traffic. I am running the demo programs provided ...


Go Back   Usenet Forums > Linux Forums > Linux Networking

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 07-19-2003
ray
 
Posts: n/a
Default NAT question

I am trying to set up my NAT box to permit CORBA traffic. I am
running the demo programs provided by jacorb 1.4.1 If I have the
server on the unprotected network and the client inside, the programs
works fine. When I swap roles, I can't get the outside client to
connect to the server on the protected network.

The inside address 192.168.10.X is translated to an unused address on
the external network. We are using the jacorb property "proxy host"
to inform the external client to use the translated IP (1.1.1.1) to
contact the server. When the internal server tries to contact itself
it uses the translated address (1.1.1.1) not the internal address and
is not successful.

I can't seem to configure the NAT box to redirect the traffic from the
inside IP that is destined for the translated address back to itself.
Is there a kernel option that is preventing this from happening? i
think my rules are configured correctly.

thanks

ray
Reply With Quote
  #2 (permalink)  
Old 07-19-2003
Timo Voipio
 
Posts: n/a
Default Re: NAT question

ray wrote:

> The inside address 192.168.10.X is translated to an unused address on
> the external network. We are using the jacorb property "proxy host"
> to inform the external client to use the translated IP (1.1.1.1) to
> contact the server. When the internal server tries to contact itself
> it uses the translated address (1.1.1.1) not the internal address and
> is not successful.


Ho-humm.

How about creating an aliased IP interface on the jacorb box? So if the
"real" interface it uses to connect to the NAT router is eth0 and has an IP
address 192.168.10.X, then the aliased interface would be eth0:0 with
address 1.1.1.1. Alias interfaces are setup up just like normal interfaces.
So if you'd like to use the setup mentioned above, then setting up an
aliased interface eth0:0 would be as simple as this:

ifconfig eth0:0 1.1.1.1 broadcast 1.1.1.1 pointopoint

I'm not too sure about those options. They worked on my quick test, but I
don't make any claims.

You'll probably want to read IP aliasing mini-HOWTO:
http://www.tldp.org/HOWTO/mini/IP-Alias/

Follow-ups only to c.o.l.networking.

-Timo

--
Timo Voipio | Helsinki, Finland | ICBM at: 60 11.800 N 024 52.760 E
GeekCode ver 3: GU>CC d s-: a--- C++ UL(+)$>+++$ P+>+++ L++(+) E- W++ N++
o? K? w O M- V- PS PE Y+ PGP+ t 5++ X R tv- b++(++++) DI+ D G e- h! r !y

Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 08:47 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0