Dirk Jakobsmeier <dirk.jakobsmeier,AT,web,DOT,de>|
Re: interface not starting|
"Dick St.Peters" <stpeters,AT,netheaven,DOT,com>|
Mon, 13 Mar 2006 09:54:27 -0500|
"Dick St.Peters" <stpeters,AT,netheaven,DOT,com>, cipe-l,AT,inka,DOT,de|
a=rsa-sha1; c=nowsp; d=netheaven.com; s=saint; t=1142261667; h=X-DomainKeys: DomainKey-Signature:Received:Message-ID:Date:From:To:Cc:Subject: In-Reply-To:References:X-Mailer; b=s3CrIG7lt6X01QsxGrJhzIsI0nHJ1koVcW6ahI5JC9fuS1btq8sXhB6PkcT8MwMld3tjLWDq+nx+OB7QvR77ag==|
a=rsa-sha1; s=saint; d=netheaven.com; c=nofws; q=dns;h=received:message-id:date:from:to:cc:subject:in-reply-to:references:x-mailer;b=Ph28NCD96iODFKL76dBfribiEDbbl8IC6+YHEslpqqceY4K4+wJ7hmb3ETx7ykCor9Gmp4p275QaG41tJEyJTw==|
Dirk Jakobsmeier writes:
> 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: 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.
> > --
> well, my problem is that on my remote server there is no pkcipe running. It
> 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)?
First, an apology for my error in saying the ciped-cb daemon won't
stay running without a peer. Static listening daemons have been used
for years - it's just been awhile since I last used one.
However, it is true that your cipcb0 device won't be fully enabled
until you have a daemon running. If you simply load the module, it is
*normal* for ifconfig -a to show the cipcb0 device as neither UP nor
RUNNING. Running the daemon (with a valid options file) will bring
the cipcb0 device the rest of the way up.
You can start the daemon without any ptpaddr or ipaddr options in the
options file and then do a manual ifconfig, but it's normal to let the
daemon assign the addresses.
Dick St.Peters, stpeters,AT,NetHeaven,DOT,com