Re: Legacy OpenTransport problem
Re: Legacy OpenTransport problem
- Subject: Re: Legacy OpenTransport problem
- From: Zachary and Meagan <email@hidden>
- Date: Tue, 18 Jul 2006 11:51:54 -0700
First off, yes I am definitely using "unusual" terminology as I am
not an expert in this area =)
Client: DSLRouter -> AirportBase -> Linksys -> Computer
Server: DSLRouter -> Computer
This is just for testing of course. The client's IP seems to be the
IP of the Airport. I've tested other applications that seem to work
ok in this environment, so I am assuming it's my code that has
issues. Anyway, I would like my app to work in as many configs as
possible.
On Jul 18, 2006, at 11:33 AM, Justin C. Walker wrote:
CC: me on replies, since I am not at home right now, so won't see
most list traffic.
On Jul 18, 2006, at 11:24 AM, Zachary and Meagan wrote:
In a nut shell I am using UPD
UDP, right?
(connectionless) for both WinSock and OT. The issue I am running
into is that the server app is running using a static IP. The
clients I am testing with are behind two layers of routers. When
the server gets the client's request to join, the server simply
uses the IP address as is to sent a receipt to the sender. The
problem is that the IP address seems to the address of the first
router (which is a local address). So of course the client's
message never makes it to the server.
This doesn't make any sense. Unless you are using "unusual"
terminology, routers do not use their own IP addresses for packets
they forward. They just point packets in the right direction, and
send them on their way, (more or less) unmolested.
Could it be that these routers are actually NAT boxes?
I am assuming if I had used a connection based approach this
problem would be taken care of behind the scene?
You should be able to quickly verify this statement/question by
using something like ssh between source and destination.
Unfortunately I have quite a bit of code surrounding my current
approach. What are my options?
This should work, but NAT is inherently squirrelly, and can't be
trusted. If NAT is involved, then you will have to verify that the
NAT boxes are in fact working correctly. I would assume that these
gizmos could handle cascaded NAT, but I have no experience with it.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large, Director
Institute for the Enhancement of the Director's Income
--------
The path of least resistance:
it's not just for electricity any more.
--------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden