Date: Sat, 10 May 2003 18:57:57 +0200 From: Marcin Dalecki <mdcki@gmx.net> To: "Yevmenkin, Maksim" <Maksim.Yevmenkin@cw.com> Cc: freebsd-hackers@freebsd.org Subject: Re: USB link cable? Message-ID: <3EBD2F95.9090807@gmx.net> In-Reply-To: <2E7E8A35375D1449A6F28D5E022E67310AC4D2@USSC8MS04.Global.Cwintra.Com> References: <2E7E8A35375D1449A6F28D5E022E67310AC4D2@USSC8MS04.Global.Cwintra.Com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yevmenkin, Maksim wrote: > this will create virtual ng0 network interface, which is different from > virtual > *ethernet* interface. if you need virtual *ethernet* interface you will need > to use ng_eiface(4) module instead of ng_iface(4), i.e. > > # ngctl mkpeer udbp0: eiface data ether > > this will create virtual ngethX *ethernet* interface. Right now my USB link cable stopped to work at all on the BSD side. I mean it stopped to work *permanently*. Neither BSD Linux nor Windwos XP recon it any more as a proper USB device. However they still detect that there is something there. **** READ - the hardware BROKE DOWN PERMANENTLY **** Excellent isn't it? > > So I have to ask if anybody ever got such a link running? > > Or would it just be easier to turn udbp.c in to if_udbp.c and > > forget about the reset? > > no. netgraph gives you a choice what of what you want to do. with > netgraph you > can turn udbp(4) pipe info network interface, ethernet interface or just > connect > to it with socket. > > max >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EBD2F95.9090807>