/DCC SEND does not work

[Russ Allbery]

Ya'akov Miles <mi...@mindlink.bc.ca> writes:
>I have a Linux Box and am running IRCII-2.6 which I compiled myself.
>Everything works except /DCC SEND, which does nothing. According
>to /DCC the IRC is waiting to send the file, however when the other
>user attempts to /DCC GET the file, there are "no files for ..."
>Can someone please help me or tell me how to patch IRCII-2.6 so that
>/DCC SEND works. (or is this a feature of Linux 1.1.59)

IRC II 2.6 EPIC works fine under Linux 1.0.9. You may want to check and see
if you have gcc 2.5.8, and if so, compile with the -g flag instead of the -O
flag. gcc does some strange optimization on Linux that screws up parts of
the client.

--
Russ Allbery (ea...@eyrie.stanford.edu) http://www-leland.stanford.edu/~rra/

When aiming for the common denominator, be prepared for the occasional
division by zero. [Anonymous]

[Doug McLaren]

In article <61241-7...@mindlink.bc.ca>,

Ya'akov Miles <mi...@mindlink.bc.ca> wrote:

| I have a Linux Box and am running IRCII-2.6 which I compiled myself.
| Everything works except /DCC SEND, which does nothing. According
| to /DCC the IRC is waiting to send the file, however when the other
| user attempts to /DCC GET the file, there are "no files for ..."
| Can someone please help me or tell me how to patch IRCII-2.6 so that
| /DCC SEND works. (or is this a feature of Linux 1.1.59)

The problem probably isn't that you compiled ircII wrong, it's
probably more likely that you're using a SLIP/PPP link, and you're
client is telling the remote client that your IP address is either
'127.0.0.1' or whatever the address of your (local) ethernet
connection is, and your SLIP/PPP providor won't let your machine route
packets between the two interfaces (most don't.)

This really isn't a Linux problem - any machine in the same situation
will have this problem, be it 386BSD, or a Sun, SGI, etc. In fact,
even a firewall machine could have this problem ...

Two possible solutions :

1) as root, before you start IRC, do this :

# hostname slip-27-9.ots.utexas.edu

with your correct slip address name, of course. I personally
prefer not to do do this, because it can confuse things running
locally when your hostname switches. Also, if the slip line goes
down, you can suddenly find local things not working anymore, as
the route to the local machine may suddenly have just disappeared.

2) I wrote a patch to irc II 2.2.9 that allows you to set what the
ircII client thinks your hostname is. You start it up with this :

% setenv IRCHOST slip-27-9.ots.utexas.edu
% irc

it ought to work for ircII 2.6, but you'll probably have to apply
it manually. It's mutually exclusive with the 'DYNAMIC IP' option
Daemon hacked in - you'll have to make sure that's disabled, or it
will undo this.

*** source/irc.c.original Wed Apr 6 22:22:59 1994
--- source/irc.c Mon Apr 18 02:49:38 1994
***************
*** 522,527 ****
--- 522,542 ----
}
}
gethostname(MyHostName, sizeof(MyHostName));
+
+ /* Here's a quick hack that allows you to use /dcc properly from a
+ a machine that is 1) two (or more) networks 2) can't route between
+ them, and 'hostname' gives the IP address for the 'wrong' network
+
+ Many machines connected via SLIP fall in this category.
+
+ How to use : Just do a 'setenv IRCHOST whatever-the-right-address
+ -is' before starting IRC (assuming a csh style shell!)
+
+ by Doug McLaren, dou...@utpapa.ph.utexas.edu, 04/19/94 */
+
+ if (ptr = getenv("IRCHOST"))
+ strmcpy(MyHostName, ptr, sizeof(MyHostName));
+
if (hp = gethostbyname(MyHostName))
{
bcopy(hp->h_addr, (char *) &MyHostAddr, sizeof(MyHostAddr));

--
For further information, please e-mail the Department Of Useful
Guidelines on Modern Communications (DOUGMC). Their e-mail address
is: dou...@utpapa.ph.utexas.edu.
"Kirk to Enterprise -- beam down yeoman Rand and a six-pack."