https://github.com/spesmilo/obelisk/commit/ab768d072dfb47fa56043119295679cdd650fd7c

there is a new setting call "outgoing-connections". Set this to 0, and
tell your bitcoin node to connect to your Obelisk node.

I can also add a setting to change the Obelisk accept port if you need it.

On 08/12/13 21:01, Grazcoin wrote:
>
> but how can I notify the obelisk that there is a bitcoin node on
> 10.0.0.1:8333 ?
> how else can it find the node?
>
> On 2013-12-08 15:10, Noel Maersk wrote:
>> On Sun, Dec 08, 2013 at 10:53:47AM +0100, Grazcoin wrote:
>>> ...
>>>
>>> If you think it is too much effort to deal with the issue directly -
>>> any idea for some workaround?
>>>
>>> ...
>
>> The simplest I can think of is firewalling on that specific machine
>> running Obelisk. Something like this:
>
>> # Only allow TCP connections on/of port 8333 to 10.0.0.1
>> -A OUTPUT -p tcp -d 10.0.0.1 --dport 8333 -m state --state
> NEW,ESTABLISHED -j ACCEPT
>> -A OUTPUT -p tcp -d !10.0.0.1 --dport 8333 -m state --state
> NEW,ESTABLISHED -j REJECT
>> -A INPUT -p tcp -s 10.0.0.1 --sport 8333 -m state --state ESTABLISHED
> -j ACCEPT
>> -A INPUT -p tcp -s !10.0.0.1 --sport 8333 -m state --state ESTABLISHED
> -j REJECT
>
>> Depending on your default policies, rules 1 & 3 or 2 & 4 can be dropped.
>
>
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>