Re: WORKAROUND ? Re: ISDN and 2.2.13 no way ;(

bvermeul@devel.blackstar.nl
Tue, 26 Oct 1999 09:36:10 +0200

In mailinglist.linux.kernel, you wrote:
>
>
>First of all i used :
>
>
>-rw-r--r-- 1 root root 695871 Oct 18 04:07
>isdn-9910180206.tar.gz
>-rw-r--r-- 1 root root 5101687 Oct 23 13:00
>isdn4k-utils-9910231100.tar.gz
>
>on both 2.2.12 and 2.2.13 kernels.
>
>I noticed ipppd on 2.2.13 was failing at this step :
>
>
>(line 640 of sys-linux.c on ipppd source )
>
> if (ioctl(sockfd, SIOCADDRT, &rt) < 0) {
> int severity;
> /*
> * It's not fatal IMHO if the route already
>exists!
> * Give a notice, though...
> */
>
>in the log the following was printed :
>
>Oct 25 22:54:17 localhost ipppd[363]: ioctl(SIOCADDRT) device route
>(ippp0/151.99.104.0/ffffff00): Network is down
>
>
>i forced the severity at LOG_NOTICE by putting an
>
> severity = LOG_NOTICE;
>
>just after the errno test and i was able to connect.
>
>Now , why does it happen on 2.2.13 and not on 2.2.13, with the same
>configuration ?

Ok. I've seen a similar problem before, so I'll have to check a couple
of things.

a) ISDN works correctly with a kernel with only numbers (eg 2.2.12)
b) ISDN doesn't work correctly with a kernel with other things in
the name (eg. 2.2.13-ac1)
c) It's got to do with the routing that ipppd does.

If that's the case, you might want to try the following patch to
ipppd. The last time I checked ipppd it didn't like extra-versions,
it stopped it from finding the correct linux-version. I could of
course be wrong, but if I'm not, I'm pretty sure this is the problem
you're having.

Hope this helps,

Bas Vermeulen

--- ipppd/sys-linux.c.orig Thu Feb 25 20:56:42 1999
+++ ipppd/sys-linux.c Thu Feb 25 20:57:20 1999
@@ -1228,13 +1228,6 @@
*patch = (int) strtoul (buf, &buf, 10);
}
}
-
- if (*buf != '\0')
- {
- *version =
- *modification =
- *patch = 0;
- }
}

/*

--
"God, root, what is difference?" 
	-- Pitr, User Friendly


"God is more forgiving." 
	-- Dave Aronson


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/