Most important is to specify a connection list (or even one node).
To disable other connections I could use firewall rules (just like Noel
noted).

On 2013-12-08 16:46, Amir Taaki wrote:
> Just to clarify, do you want to be able to specify a connection list for
> a node together with the ability to disable automatic connections? This
> is to limit bandwidth used.
>
> ATM are you telling your bitcoind to connect to Obelisk? Would it be
> better if you could disable just outbound connections, not inbound ones?
>
> On 08/12/13 09:53, Grazcoin wrote:
>> Amir - thanks for the quick action!
>> Offline setup should be fine now.
>>
>> Now back to the orig issue:
>>
>> Keeping multiple bitcoin setups on my LAN (development purposes) is
>> expensive bw-wise.
>>
>> One bitcoin node (either bitcoind or obelisk) is no problem though.
>> Other bitcoind can connect to the main one on the LAN using
>> connect=10.0.0.1:8333 or addnode=10.0.0.1:8333 to a trusted node. This
>> is currently not the case with obelisk, as it just makes connections
>> in parallel and takes too much of my limited bw resources.
>>
>> If you think it is too much effort to deal with the issue directly -
>> any idea for some workaround?
>>
>> This is not urgent, but a "very nice to have".
>>
>> Thanks,
>> Grazcoin
>>
>>
>> On 12/07/2013 10:47 PM, Amir Taaki wrote:
>>> Added:
>>
>>>
https://github.com/spesmilo/obelisk/commit/0ff0fc6ad40d4d7bd5ce832f048571c999ba5557
>>
>> _______________________________________________
>> Libbitcoin mailing list
>> Libbitcoin@???
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>>
>
>
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin