bind-address-ipv4 doesn't seem to work in 2.92.

Ask for help and report issues with the Mac OS X version of Transmission
Post Reply
NoMoreNicksLeft
Posts: 12
Joined: Mon Dec 30, 2013 8:23 am

bind-address-ipv4 doesn't seem to work in 2.92.

Post by NoMoreNicksLeft »

I have set up my iMac with two IP addresses. One is DHCP from my router, another is 192.168.111.111. The DHCP takes precedence (listed at the top). If I do an ifconfig, I see that en0 has both addresses. A quick glance at tcpdump shows plenty of traffic with a src ip of the DHCP address.

If I do a

Code: Select all

ping -S 192.168.111.111 yahoo.com
I can see the pings being sent with the second ip.

However, if I do this

Code: Select all

defaults write org.m0k.transmission bind-address-ipv4 192.168.111.111
and then start Transmission, it does not use the secondary ip. I can see oodles of packets leaving with a dst port of 6xxx and the DHCP ip address.

I de-binaried the plist, opened it, and I do see the bind-address-ipv4 set to what I want it to be. Restarting Transmission doesn't lose or change the setting... it just refuses to use it. And in the past (on other machines) I have gotten this to work. Am I forgetting a step, is more required to make this work?

This is very frustrating, as I can't really use Transmission at all until I get this working. My router sends anything 192.168.111.x over a VPN, and in the meantime I'm just testing with a linux iso torrent.
NoMoreNicksLeft
Posts: 12
Joined: Mon Dec 30, 2013 8:23 am

Re: bind-address-ipv4 doesn't seem to work in 2.92.

Post by NoMoreNicksLeft »

Thanks x190. That's the problem... didn't spell the property name correctly.
Post Reply