Good morning. Is there any way to force wine to use a specific network interface? I have the following setup: eth0 internet interface tun0 openvpn some programs use broadcasting (Starcraft). I don't know how it determines which device to use. It probably takes the first it does see. (Or is it wine doing that ?) the problem is that starcraft just send the packages out via eth0. for windows there is a tool called ForceBindIP http://www.r1ch.net/stuff/forcebindip/ which does exactly what i need. unfortunally it doesnt work in wine i know it could be solved by using a bridged vpn instead of a tunnel, but that is no option for me. perhaps anyone has come across the same problem and knows a fix. or maybe there is some firewall magic i could do to just manipulate the packages' route. thanks in advance -- Marcel W. Wysocki <maci at satgnu.net> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://www.winehq.org/pipermail/wine-users/attachments/20080312/e2cad96f/attachment.pgp
On Wed, Mar 12, 2008 at 2:23 AM, Marcel W. Wysocki <maci at satgnu.net> wrote:> for windows there is a tool called ForceBindIP http://www.r1ch.net/stuff/forcebindip/ which does exactly what i need. > unfortunally it doesnt work in wineWhat happens when you try to ues ForceBindIP? There's a chance Wine could support that app, if we can find out what the bugs are and fix them. - Dan
> Is there any way to force wine to use a specific network interface? > I have the following setup: > > eth0 internet interface > tun0 openvpn > > some programs use broadcasting (Starcraft). I don't know how it determines which device to use. It probably takes the first it does see. (Or is it wine doing that ?) > the problem is that starcraft just send the packages out via eth0. > > for windows there is a tool called ForceBindIP http://www.r1ch.net/stuff/forcebindip/ which does exactly what i need. > unfortunally it doesnt work in wine > i know it could be solved by using a bridged vpn instead of a tunnel, but that is no option for me.ok, fixed the issue, sometimes its just too easy ;) route add -host 255.255.255.255 tun0 did the trick -- Marcel W. Wysocki <maci at satgnu.net> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://www.winehq.org/pipermail/wine-users/attachments/20080316/8f6e5c20/attachment.pgp