Topic: 0.3.21 Mac client & UPnP (Read 1663 times)
Ah sorry, I see what you mean now. In that case yeah UPnP would help, if it were enabled in the binaries.
He didn't say he wanted more than one node running at a time.
That is correct. I don't need to ever run more than one Bitcoin client at a time behind my router. But I often switch back and forth between a desktop and several different laptops, sometimes wired with ethernet, sometimes on Wifi, and it is a total pain to get the port forwarding on the router sorted out in this situation. For this I thought UPnP would be a great help.
In any case, can we get an explanation as to why UPnP was disabled on the Mac binaries? Laszlo?
Seems like thats what he said...maybe I am confused. Or maybe he meant on different machines and not at the same time.
He didn't say he wanted more than one node running at a time.
UPnP can't do what you want. With NAT you will only ever be able to have one node listening to the outside world. If you want more than that you need to lose the NAT and get multiple IPs from your ISP.
I noticed that the new binary for the 0.3.21 build Mac client was released the other day. So far it's running great for me, much faster than the previous release, but one question:
Does the 0.3.21 Mac client support the new automatic UPnP port mapping feature? I see the option in 'Preferences' but it is greyed out.
This is one new feature I was looking forward to, as I am behind a NAT and use Bitcoin on several different machines.
Many thanks to all the developers who didn't forget about us Apple-heads.
Does the 0.3.21 Mac client support the new automatic UPnP port mapping feature? I see the option in 'Preferences' but it is greyed out.
This is one new feature I was looking forward to, as I am behind a NAT and use Bitcoin on several different machines.
Many thanks to all the developers who didn't forget about us Apple-heads.
Jump to: