Hi Craig and Robert,
I'm currently playing a bit with multiple network interfaces, partly
because I'd like to test the new socket bundling code.
In my situation, I have two network interfaces up:
en0: 192.168.1.70
en1: 192.168.1.11
both have 192.168.1.1 as default router, thus, in this case it
doesn't matter which physical interface is used to send data.
Destination: 192.168.1.12
If I Listen on en1 and send data to the destination, the IP
destination IS 192.168.1.11, but the packet gets sent over en0. I
don't know if it is a platform-dependent issue (MacOSX) or do others
have this problem too?
Below is a code snippet that shows the test I'm doing.
Hannes
*********************************************************************
PUDPSocket socket;
OpalTransportAddress destination = "udp$192.168.1.12:1000";
OpalTransportAddress source = "192.168.1.11";
PIPSocket::Address destAddr;
WORD destPort;
PIPSocket::Address localAddr;
WORD localPort;
destination.GetIpAndPort(destAddr, destPort);
source.GetIpAndPort(localAddr, localPort);
socket.Listen(localAddr);
socket.SetSendAddress(destAddr, destPort);
socket.WriteString("Test\r\n");
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Openh323-devel mailing list
Openh323-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openh323-devel
[Open H.323]
[IETF SIP]
[Gnu Gatekeeper]
[Asterisk PBX]
[Fedora Linux]
[Gimp]
[Yosemite News]
[Yosemite Photos]
[Yosemite Campsites]
[ISDN Cause Codes]