RE: Device or Resource busy on reconnect.

Hi Doug,

Please check route-table (cmd:  /sbin/route )
Some times you cannot detach a device if it is in use bij some program or
protocol.

You could test for transmission over a interface with something like:
/usr/sbin/tcpdump -i <interface> <src|dst> host ip<-number>

You can remove de kernel-module after you have:
- stopped programms using the 'protocol' or link,
- removed routes,
- detached devices.

succes,

...BUT, conserning my problem:

do you use any specific compile options ??
eq. what do you use as :
- gcc compiler,
- SMP support ??

best regards,
Edwin Boonenburg


> -----Oorspronkelijk bericht-----
> Van: [email protected] [mailto:[email protected]]Namens
> Doug Milns
> Verzonden: woensdag 22 december 2004 14:27
> Aan: [email protected]
> Onderwerp: Device or Resource busy on reconnect.
>
>
> Ive been using cipe 1.5.4 for some time now with slackware 8.0 very
> successfully. Its proved a very effective solution. Thanks to everyone
> involved with developing this!
>
> Now a quick plea for help :)
>
> Im now trying to use cipe 1.6.0 (have also tried with 1.5.4) on
> slackware 10.0 with kernel 2.4.28, compile + install successful. Both
> ends setup to use pkcipe with one end initiating connection - just as
> Ive always done. The first time the connection initates perfectly and
> everything works fine. If I down the connection (ifconfig cipcbX down)
> it refuses to reestablish it. The syslog on the "server" end
> (receiving
> the pkcipe request) shows :-
>
> Dec 22 13:17:34 icom-gate ciped-cb[827]: opendev: attach: Device or
> resource busy
> Dec 22 13:17:34 icom-gate pkcipe[825]: ready: ciped returned 1
>
> "ifconfig" shows no active cipecbX interfaces (although
> cipecb0 is still
> listed in /proc/net/dev and "ifconfig cipcb0" does still return the
> usual information).
>
> I am unable to "rmmod cipcb" as it claims the module is in use. I can
> find no evidence of any cipe processes still running.
>
> I have looked through the archives and found similar reports from
> someone back in Nov 2001 with cipe 1.4 but the replies from this say
> this is solved in 1.5.
>
> Reboot and the connection initiates flawlessly ... until you
> disconnect
> it again .
>
> Is this something with slackware 10.0? Should ifconfig be removing the
> device rather than just downing it?  Where have I gone wrong ?
>
> Thanks in advance
> Doug.
>
>
> --
> Message sent by the [email protected] mailing list.
> Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive:
> <URL:http://sites.inka.de/~bigred/devel/cipe.html>
>



--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>