Well, not really.
You can hide your own host behind BNC - there is a matter with settings, because (of course) your IP must be resolved. But you must resolve only your local IP. My settings:
IRC/Connect/Local info:
- On connect always get: Local Host
- Lookup Method: Normal
In other case when trying to dcc chat or dcc send I always get:
* Unable to resolve local host
With settings as above attempting to dcc chat from bnc session (nick _BNC_) to normal session (nick Frukto):
Chat with Frukto
Waiting for acknowledgement...
DCC Chat connection established
DCC Chat session
Client: _BNC_ (192.168.0.77)
Time: Sat Oct 04 14:45:41 2003
Acknowledging chat request...
DCC Chat connection established
and:
—I-n-v-i-s-i-o-n— Resolved _BNC_ (shell.lomag.net) to 208.185.82.7
when real IP is 80.54.64.59.
DCC chat in opposite way (from Frukto to _BNC_) is also possible without problem. Also sending from _BNC_ to Frukto without problems:
[14:49:02] *_BNC_* DCC Send 1122.jpg (
192.168.0.77)
[14:49:03] DCC Send of 1122.jpg to Frukto complete (00:00:01 6.17 KB/Sec)
[14:49:03] DCC Get of 1122.jpg from _BNC_ complete (00:00:01 6.17 KB/Sec)
And from Frukto to _BNC_:
[14:53:05] DCC Send of 1156.jpg to _BNC_ complete (00:00:01 15.5 KB/Sec)
[14:53:04] DCC Get of 1156.jpg from Frukto complete (00:00:01 15.5 KB/Sec)
As you can see only local IP is visible after dcc chat/send, not real IP - just BNC host. So it is possible to hide. At least I think so
