Date: Thu, 5 Apr 2001 02:47:00 -0600 From: "Alex Huppenthal" <alex@aspenworks.com> To: "Harti Brandt" <brandt@fokus.gmd.de> Cc: "Richard Hodges" <rh@matriplex.com>, <freebsd-atm@FreeBSD.ORG> Subject: Re: ATM 4.3 and so on Message-ID: <01d601c0bdac$ffe64700$1800a8c0@d7k> References: <Pine.BSF.4.33.0104051021020.6149-100000@beagle.fokus.gmd.de>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm very happy to hear this might arrive in May. Cheers to you. :-) UNI 4.x is interesting. Our ATM network vendor offers just UNI 3.1, I'm guessing 4.x is backward compatible. Will this operate at all like the 'atm' setup does? Is the intent to replace the HARP stack? Will we need a new 'atm' command? Will FreeBSD have a device entry like hfa0 and sub devices like atm0 atm1, etc associated with the PVCs? Is the 'atm' command functionality left up to a C-coder to write? :-) Sorry for all the questions, I'm new.:-) I really would love to stick with FreeBSD for this ATM cloud edge-device. I like IPFW, dummynet and other familiar places. I don't want to create this end-point ATM<=>Ethernet device using Linux. I can't get away from the fragmentation error. If I could, all else would be adequate for the near term.. Is there anyway I can debug the existing OS/driver? 4.2 is running.. albeit with a fragmentation problem. I must have a solution for deployment in a few days. Even if it's an interim solution. Desperately seeking solution. :-) ----- Original Message ----- From: "Harti Brandt" <brandt@fokus.gmd.de> To: "Alex Huppenthal" <alex@aspenworks.com> Cc: "Richard Hodges" <rh@matriplex.com>; <freebsd-atm@FreeBSD.ORG> Sent: Thursday, April 05, 2001 2:29 AM Subject: Re: ATM 4.3 and so on > On Thu, 5 Apr 2001, Alex Huppenthal wrote: > > AH>Sounds intriging. What *is* the new netgraph version of ATM? :-) Can I use > AH>it soon? (oh please oh please :-) > > Ok. I have the following netgraph nodes ready and working: > > if_fatm - this is a new driver for the FORE-PCA200E with netgraph > and NATM support > ng_atm - this is a netgraph node which gives you direct access to > the above driver > ng_sscop - this implements the ITU-T Q.2110 SSCOP protocol > ng_sscfu - this is the almost empty SSCF above SSCOP for UNI > ng_uni - this is UNI4.0 (without LIJ, which I'm probably will > not implement because it's dropped in UNI4.1) > ng_ccatm - this implements the Native ATM-API (af-saa-0108.000) > I'm working on this at the moment. > > Still missing: > > ng_clip - classical IP-over-ATM > ng_atmsock - this will probably sit on ng_ccatm to provide a socket() > interface to native ATM > > In the future: > > ng_lane - LANE client. > > How soon you can use it, I don't know. The ATM-API is really the hard > part! Try to read their document: good intent, but result even worse than > ITU-T documents :-( > > I think I will have everything except atmsock in the middle of may. > > harti > -- > harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private > brandt@fokus.gmd.de, harti@begemot.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-atm" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01d601c0bdac$ffe64700$1800a8c0>