Re: IP address used by Sockets

Scott,

Thank you for the reply.

I did not mean to imply that I wanted to send the data through an
unencrypted tunnel - that would, obviously, be unacceptable! I was trying
to say that, in the absence of the "correct" solution, I would see if the
network folks would add bb.bb.bb.bb to the tunnel and the traffic would be
secure and allowed.

As you suggest, I will investigate the routing table.....but that will have
to come later. For the moment, I have it working by binding it to
aa.aa.aa.aa.

Thanks again,

Joe

Joe Wells
University of Alabama Health Services Foundation
500 22nd Street South, Suite 308
Birmingham, AL 35233
205-731-5610

CONFIDENTIALITY NOTICE
This e-mail is intended for the sole use of the individual(s) to whom it is
addressed, and may contain information that is privileged, confidential and
exempt from disclosure under applicable law. You are hereby notified that
any dissemination, duplication or distribution of this transmission by
someone other than the intended addressee or its designated agent is
strictly prohibited. If you receive this e-mail in error, please notify me
immediately by replying to this e-mail.

On 9/30/2009 at 11:48 AM, in message

<4AC38BDB.6000903@xxxxxxxxxxxxxxxx>,
Scott Klement<rpg400-l@xxxxxxxxxxxxxxxx> wrote:

Joe Wells wrote:

While testing yesterday, the connection timed out.
Netstat showed that the local ip was bb.bb.bb.bbb. This is why it would

not

connect.

No. This isn't why it wouldn't connect. Instead, it's a symptom of the

fact that something is wrong with your routing table. It won't connect
because the system has chosen the wrong route to get to the remote
server. Using the wrong route caused it to pick the wrong network
interface and therefore IP address. It also caused it not to connect.

I tried again this morning and it used aa.aa.aa.aa and it ran fine.
I will try to get the hospital network folks to open up bb.bb.bb.bbb

like

aa.aa.aa.aa,

Why would you do that?! That's your only assurance that it's using the
correct route (and therefore going through the encrypted tunnel.) You
need to FIX your routing so that data goes through the protected tunnel.

Your reaction to this is to allow non-protected data?

Unless I'm misunderstanding the situation?

In theory, I understand what Michael is suggesting. Unfortunately, I am

new

to sockets and am struggling with how/where to specify the ip address.

The

bind() that is called in the server program does not specify an ip, only

a

port.

Set sin_addr to the IP address (in binary form) you want to bind to.
It's not any different from when you set the address in the same
structure when you use it with connect()