Re: SO_BINDTODEVICE or sendto using specific network interface
Re: SO_BINDTODEVICE or sendto using specific network interface
- Subject: Re: SO_BINDTODEVICE or sendto using specific network interface
- From: Alex Telitsine <email@hidden>
- Date: Mon, 12 Dec 2005 14:15:41 -0800
Thanks for reply. It is not multicast, not always anyway.
Will BPF (Berkley Packet Filter) write of the raw packets bypass OSX
routing?
Is there any better solution?
I definitely have to bypass routing, since each interface will be
sending to the
same destination (IP) address.
Thanks,
@
On Dec 11, 2005, at 11:41 PM, Josh Graessley wrote:
If you're using multicast packets, you can specify the interface
using a multicast specific option. Otherwise, there is no way to
control which interface the packets are sent on. That decision will
be made based on the routing table.
-josh
On Dec 9, 2005, at 7:48 PM, Alex Telitsine wrote:
I have to send UDP data from OSX, dual-ethernet system over two
sattelite phones simultaneously.
So far, it seems that MacOSX is always determenes what interface
to use based on destination (sendto) address only.
In Window, it is enough to “bind” socket to specific IP/interface
instead of ANY_ADDR, Linux has SO_BINDTODEVICE
(
see explanation at the http://zuul.slackware.biz/versions/
slackware-3.9/docs/linux-2.0.37pre10/networking/so_bindtodevice.txt
)
Any advise on how to archive it on Mac OSX ?
Thanks,
@
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.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