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.