I figured it would be something like that. Well, at least I have
something to work on.
Thanks again.
Steven Critchfield wrote:
On Thu, 2005-01-06 at 22:05 +, Niksa Baldun wrote:
Thanks, that was it. Now I can accept incoming RAS connections. But,
what about outgoing connecti
On Thu, 2005-01-06 at 22:05 +, Niksa Baldun wrote:
> Thanks, that was it. Now I can accept incoming RAS connections. But,
> what about outgoing connections? Is it possible to make * behave like
> ISDN router, i.e. have it establish a connection when someone on the
> LAN requests specific IP add
Thanks, that was it. Now I can accept incoming RAS connections. But,
what about outgoing connections? Is it possible to make * behave like
ISDN router, i.e. have it establish a connection when someone on the
LAN requests specific IP address?
Thanks again.
Steven Critchfield wrote:
On Thu,
On Thu, 2005-01-06 at 18:10 +, Niksa Baldun wrote:
> Hello,
>
> I am using * with latest bristuff. I tried to make use of ZapRAS
> application (with the little or no documentation available), but I get
> the following error when trying to establish RAS connection:
>
> app_zapras.c:149 run_ras
Hello,
I am using * with latest bristuff. I tried to make use of ZapRAS
application (with the little or no documentation available), but I get
the following error when trying to establish RAS connection:
app_zapras.c:149 run_ras: wait4 returned -1: No child processes
Anyone has an idea what this
