<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: "Dick St.Peters" <stpeters,AT,netheaven,DOT,com>
Subject: Re: interface not starting
From: Dirk Jakobsmeier <dirk.jakobsmeier,AT,web,DOT,de>
Date: Sat, 11 Mar 2006 11:08:14 +0100
Cc: cipe-l,AT,inka,DOT,de
In-reply-to: <17425.61049.692477.368574@saint.heaven.net>
References: <200603102102.19220.dirk.jakobsmeier@web.de> <17425.61049.692477.368574@saint.heaven.net>

Am Freitag, 10. März 2006 22:24 schrieben Sie:
> Dirk Jakobsmeier writes:
> > iÂŽm having a problem while loading cipe module. After patching version
> > 1.6.0 with patch for kernel 2.6.14 i could load module cipcb0 an got the
> > following messages in message file:
> >
> > kernel: cipcb: CIPE driver vers 1.6.0 (c) Olaf Titz 1996-2003, 100
> > channels, \ debug=1
> > kernel: cipcb: cipe_alloc_dev 0
> >
> > After that if i try to start the interface i got:
> >
> > /etc/dev.d/net/50-ifup.dev[17524]: SIOCSIFFLAGS: No such device or
> > address ifup: Cannot enable interface cipcb0
> > ifup-route: interface cipcb0 is not up
> >
> > Doing an ifconfig -a i can see cipcb0 but not without -a. So the
> > interface was not startet.
>
> The device won't be fully enabled until you have a ciped-cb daemon
> running - and the daemon won't stay running until it has a peer to
> talk to.
>
> Rather than trying to access a device that's not really there yet, try
> using it - bring up a tunnel, using pkcipe for example.
>
> --
Hello,

well, my problem is that on my remote server there is no pkcipe running. It 
is 
running a cipe daemon, waitiing for a connection. So i have to do it this 
way. Using pkcipe means to use it on both sides i think (hopefully read 
correct in documentation)?

Thanks for your answer.
-- 


<< | Thread Index | >> ]    [ << | Date Index | >> ]