From owner-freebsd-atm Mon Apr 9 1:35:25 2001 Delivered-To: freebsd-atm@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 719E837B424 for ; Mon, 9 Apr 2001 01:35:22 -0700 (PDT) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id KAA06433 for ; Mon, 9 Apr 2001 10:35:20 +0200 (MET DST) Date: Mon, 9 Apr 2001 10:35:20 +0200 (CEST) From: Harti Brandt To: Subject: ForeRunnerHE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, does anybody know whether there is documentation available on the API of these cards? I may want to port the Linux driver or implement a new one. 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 From owner-freebsd-atm Mon Apr 9 9: 7:42 2001 Delivered-To: freebsd-atm@freebsd.org Received: from esply02.cnt.com (mailhost.cnt.com [139.93.128.21]) by hub.freebsd.org (Postfix) with ESMTP id E090237B422 for ; Mon, 9 Apr 2001 09:07:32 -0700 (PDT) (envelope-from joe_thomas@cnt.com) Received: by esply02.cnt.com with Internet Mail Service (5.5.2650.21) id <2SFGM46T>; Mon, 9 Apr 2001 11:10:29 -0500 Message-ID: <67DB78CE91D7D41190A100508BFDF5E051EF1A@esply03.cnt.com> From: Joe Thomas To: 'Alex Huppenthal' , "Archinaco, Chris" Cc: freebsd-atm@FreeBSD.ORG Subject: RE: SR100069960 - Linux resources Date: Mon, 9 Apr 2001 11:09:50 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, having a MTU of size 48 is going to be the cause of the fragmentation problem. I don't know why the interface would come up with that value since it's supposed to be set at 9180. [This is done in the sys/netatm/atm_if.c module when the IP interfaces are defined and associated with the physical ATM interface (such as hfa0 for a FORE adapter).] Yeah, it can't be set with the ifconfig command because the SIOCSIFMTU case isn't supported. As I recall, we chose to not allow it because of the difficulty in propagating the MTU everywhere. With UNI, the MTU size is also used to define forward and backward packet sizes in UNI SETUP messages so that the ATM network can ensure there's enough buffering available. If one changed the MTU size on the fly, you would be expected to close down any open VCs across that interface and reopen them with the new value. This really confuses me as to how/why the MTU is being set to 48. Can you check for ATM_NIF_MTU in sys/netatm/atm_if.*? It should be defined to 9180 in the .h file and you should see a line like atm_if.c: ifp->if_mtu = ATM_NIF_MTU; in the .c file. The other thing that might be interesting to try is to bump up the number of IP/ATM interfaces in your rc.conf file. Somewhere there'll be a line similar to 'atm_netif_hfa0="atm 1"' where hfa0 is the physical ATM interface (hea0 for Efficient), 'atm' is the name to be used for the IP interface (what'll see with ifconfig), and 1 is the number of logical IP interfaces to create. In this example, one IP interface named 'atm0' will be created. Increment this by one or two and then reboot. Right after the system comes up, check the MTU sizes with 'ifconfig -a' again. If the new interfaces have the correct MTU size (9180), then something's happening to change the MTU after the system is up. If the new interfaces have the MTU size of 48, then the value being set when the interface is created is wrong. This might at least give folks an idea of where to start looking... Joe -----Original Message----- From: Alex Huppenthal [mailto:alex@aspenworks.com] Sent: Friday, April 06, 2001 7:37 PM To: Joe Thomas; Archinaco, Chris Cc: freebsd-atm@FreeBSD.ORG Subject: Re: SR100069960 - Linux resources MTU shows up as 48. Can't change the MTU with ifconfig -Alex Thanks to everyone for the insight and information today. ----- Original Message ----- From: "Joe Thomas" To: "'Alex Huppenthal'" ; "Archinaco, Chris" Cc: Sent: Friday, April 06, 2001 10:18 AM Subject: RE: SR100069960 - Linux resources > > The microcode was embedded as a .h structure sometime in mid/late > FBSD 3.x so no more having to download the "correct" version. To > the best of my knowledge, the microcode used has not changed since > we released the driver. Any improvement you see in your problem by > backing down to FBSD 3.5 will be because of IP changes between 3.5 > and 4.X, not from microcode or device driver changes. [The problems > in the device driver between 3.5/4.0 and 4.1+ were because of mbuf > structure changes which caused some problems with how the driver > reserves space for passing tokens/etc. with the buffers, and with > a corresponding change that caused a problem with how we used some > space in the pkthdr structure where our assumptions about who and > when those fields were used were no longer valid. The driver doesn't > and never did try to do IP fragmentation. Someone mentioned examining > the MTU size. This would be on the IPATM interface -- check with > 'ifconfig -a'.] > > Joe > > -----Original Message----- > From: Alex Huppenthal [mailto:alex@aspenworks.com] > Sent: Friday, April 06, 2001 11:07 AM > To: Joe Thomas; Archinaco, Chris > Cc: freebsd-atm@FreeBSD.ORG > Subject: Re: SR100069960 - Linux resources > > > Yes, thank you for your suggestion on how to debug the driver via mbuf > dumps. I can only hope I'm able to do that. :-) Its been many moons since I > did any kernal debugging. Perhaps Chis at Marconi can shed some light on > microcode revs too. Perhaps I'm using downloadable microcode that's not the > right revision. > > I know people have said 3.5 FreeBSD runs the ATM PCA200e well. Perhaps I > should just move back to that OS.. Forward sounds better though. > > > ----- Original Message ----- > From: "Joe Thomas" > To: "'Alex Huppenthal'" ; "Archinaco, Chris" > > Cc: > Sent: Friday, April 06, 2001 9:49 AM > Subject: RE: SR100069960 - Linux resources > > > > > > The API for the 200E line of adapters is available as > > ftp://ftp.fore.com/pub/docs/port/aali.pdf. I just checked and > > it is dated May 1997. This document never did list what the > > changes from microcode rev to rev were, they simply put out > > a new document. Quite some time ago, Fore posted info on obtaining > > driver source and documentation for their new HE line of adapters. > > The HE is not really an API since you'd be talking straight to the > > adapters registers, etc. as opposed to talking to a microcode app > > on the 200E line. I assume someone actively doing HE development > > on Linux could point you to the right specs, else someone at Macroni, > > and if all else fails, I could go through my archives but that would > > take some time to do... > > > > [Having done the initial FreeBSD FORE driver, I can attempt to > > answer questions as my job/time permits. I do not have any access > > to ATM equipment which would allow me to test anything, let alone > > do any kind of debug/development work. Fortunately, there have been > > several other folks who are active on the list that have stepped up > > to the task so hats off to them! Did you see the comments I replied > > with yesterday about examining IP mbufs as they come into ipatm_output()? > > This would be the place to start determining who's doing the fragmenting.] > > > > Joseph Thomas > > > > -----Original Message----- > > From: Alex Huppenthal [mailto:alex@aspenworks.com] > > Sent: Friday, April 06, 2001 10:32 AM > > To: Archinaco, Chris > > Cc: freebsd-atm@FreeBSD.ORG > > Subject: Re: SR100069960 - Linux resources > > > > > > Chris, > > > > Thanks a million for this info. I'm still stuggling a bit with the BSD > > driver and wonder if you can shed some light on how the ForeRunner card > > actually operates now days. Is there a place we can look to find > > documentation on the API to the card? Perhaps including a list of > functional > > changes made to PCA200E recently? > > > > I'm excited about using this card in a number of installations. > Currently, > > the FreeBSD version of the driver seems to fragment PDUs in a way which > > Xedia routers (lucent) interpret as a 'tiny fragment' attack. At that > point > > they discard the entire PDU. > > > > New development is going on and I just wonder if you have information > which > > could verify how things work. > > > > I'm copying the group which is currently very interested in making > FreeBSD > > a high performance platform using your ATM PCI solution. > > > > Thank you, > > > > Alex > > > > PS: to listen in on the discussion about FreeBSD and ATM.. Send an email > to: > > mailto:subscribe-freebsd-atm@freebsd.org > > > > > > ----- Original Message ----- > > From: "Archinaco, Chris" > > To: > > Sent: Wednesday, March 14, 2001 2:41 PM > > Subject: FW: SR100069960 - Linux resources > > > > > > > > Hi Alex, > > > > > > > > Here are the Linux resources I was telling you about. I asked the > > > > TSE who was running the PCA on Linux about FreeBSD but he told me that > > he > > > > had never actually tried it with our adapter. Let me know if you have > > any > > > > problems getting the source via Tactics Online. Let me know if you > have > > > > any questions. > > > > > > > > > > > > LINUX Adapter code for Marconi ATM adapters. > > > > The following are listed as a convenience for persons interested in > > LINUX > > > > drivers available for Marconi ATM Cards. Marconi assumes no liability > > for > > > > the utilization of any of the software referenced. > > > > The referencing of this software should not be construed as an > > endorsement > > > > by Marconi for the use of the software or appropriateness of purpose > for > > > > any particular task. > > > > These are not the only drivers available. > > > > > > > > HE-series card driver: > > > > > > > > > > > > PCA200E card driver: > > > > > > > > > > > > LE25/155 card driver: > > > > > > > > > > > > Linux ATM Resources (Help on installation): > > > > > > > > > > > > Hope this helps, > > > > > > > > Chris > > > > > > > > Chris Archinaco > > > > Level 2 Technical Support Engineer - Edge Products > > > > Marconi Services > > > > phone: (800) 671-3673 > > > > fax: (724) 742-6275 > > > > email: chris.archinaco@marconi.com > > > > URL: http://www.marconi.com > > > > Tactics Online: http://tactics.marconi.com > > > > > > > > > > > > > > > > > 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 > 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 From owner-freebsd-atm Mon Apr 9 10:23:28 2001 Delivered-To: freebsd-atm@freebsd.org Received: from aspenworks.com (aspenworks.com [192.94.236.1]) by hub.freebsd.org (Postfix) with ESMTP id CCA3537B422 for ; Mon, 9 Apr 2001 10:23:16 -0700 (PDT) (envelope-from alex@aspenworks.com) Received: from d7k (matrix.aspenworks.com [216.38.199.82]) by aspenworks.com (8.9.3/8.9.3) with SMTP id LAA09521; Mon, 9 Apr 2001 11:22:57 -0600 (MDT) (envelope-from alex@aspenworks.com) Message-ID: <008201c0c119$b84c3880$1700a8c0@d7k> From: "Alex Huppenthal" To: "Joe Thomas" , "Archinaco, Chris" Cc: References: <67DB78CE91D7D41190A100508BFDF5E051EF1A@esply03.cnt.com> Subject: Re: SR100069960 - Linux resources Date: Mon, 9 Apr 2001 11:22:54 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is what my system says: fore.h:#define FORE_IFF_MTU 9188 /* Network interface MTU */ what's the extra 8 bytes for? Perhaps a part of a fragment later.. I see ifp->if_mtu = ATM_NIF_MTU; in atm_if.c ----- Original Message ----- From: "Joe Thomas" To: "'Alex Huppenthal'" ; "Archinaco, Chris" Cc: Sent: Monday, April 09, 2001 10:09 AM Subject: RE: SR100069960 - Linux resources > Well, having a MTU of size 48 is going to be the cause of the > fragmentation problem. I don't know why the interface would > come up with that value since it's supposed to be set at 9180. > [This is done in the sys/netatm/atm_if.c module when the IP interfaces > are defined and associated with the physical ATM interface (such as > hfa0 for a FORE adapter).] > > Yeah, it can't be set with the ifconfig command because the > SIOCSIFMTU > case isn't supported. As I recall, we chose to not allow it because of the > difficulty in propagating the MTU everywhere. With UNI, the MTU size is also > used to define forward and backward packet sizes in UNI SETUP messages so > that > the ATM network can ensure there's enough buffering available. If one > changed > the MTU size on the fly, you would be expected to close down any open VCs > across that interface and reopen them with the new value. > > This really confuses me as to how/why the MTU is being set to 48. > Can you check for ATM_NIF_MTU in sys/netatm/atm_if.*? It should be defined > to 9180 in the .h file and you should see a line like > atm_if.c: ifp->if_mtu = ATM_NIF_MTU; > in the .c file. The other thing that might be interesting to try is to bump > up the number of IP/ATM interfaces in your rc.conf file. Somewhere there'll > be a line similar to 'atm_netif_hfa0="atm 1"' where hfa0 is the physical > ATM interface (hea0 for Efficient), 'atm' is the name to be used for the > IP interface (what'll see with ifconfig), and 1 is the number of logical > IP interfaces to create. In this example, one IP interface named 'atm0' will > be created. Increment this by one or two and then reboot. Right after the > system comes up, check the MTU sizes with 'ifconfig -a' again. If the new > interfaces have the correct MTU size (9180), then something's happening to > change the MTU after the system is up. If the new interfaces have the MTU > size of 48, then the value being set when the interface is created is wrong. > This might at least give folks an idea of where to start looking... > > Joe > > -----Original Message----- > From: Alex Huppenthal [mailto:alex@aspenworks.com] > Sent: Friday, April 06, 2001 7:37 PM > To: Joe Thomas; Archinaco, Chris > Cc: freebsd-atm@FreeBSD.ORG > Subject: Re: SR100069960 - Linux resources > > > MTU shows up as 48. > > Can't change the MTU with ifconfig > > -Alex > > Thanks to everyone for the insight and information today. > > > ----- Original Message ----- > From: "Joe Thomas" > To: "'Alex Huppenthal'" ; "Archinaco, Chris" > > Cc: > Sent: Friday, April 06, 2001 10:18 AM > Subject: RE: SR100069960 - Linux resources > > > > > > The microcode was embedded as a .h structure sometime in mid/late > > FBSD 3.x so no more having to download the "correct" version. To > > the best of my knowledge, the microcode used has not changed since > > we released the driver. Any improvement you see in your problem by > > backing down to FBSD 3.5 will be because of IP changes between 3.5 > > and 4.X, not from microcode or device driver changes. [The problems > > in the device driver between 3.5/4.0 and 4.1+ were because of mbuf > > structure changes which caused some problems with how the driver > > reserves space for passing tokens/etc. with the buffers, and with > > a corresponding change that caused a problem with how we used some > > space in the pkthdr structure where our assumptions about who and > > when those fields were used were no longer valid. The driver doesn't > > and never did try to do IP fragmentation. Someone mentioned examining > > the MTU size. This would be on the IPATM interface -- check with > > 'ifconfig -a'.] > > > > Joe > > > > -----Original Message----- > > From: Alex Huppenthal [mailto:alex@aspenworks.com] > > Sent: Friday, April 06, 2001 11:07 AM > > To: Joe Thomas; Archinaco, Chris > > Cc: freebsd-atm@FreeBSD.ORG > > Subject: Re: SR100069960 - Linux resources > > > > > > Yes, thank you for your suggestion on how to debug the driver via mbuf > > dumps. I can only hope I'm able to do that. :-) Its been many moons since > I > > did any kernal debugging. Perhaps Chis at Marconi can shed some light on > > microcode revs too. Perhaps I'm using downloadable microcode that's not > the > > right revision. > > > > I know people have said 3.5 FreeBSD runs the ATM PCA200e well. Perhaps I > > should just move back to that OS.. Forward sounds better though. > > > > > > ----- Original Message ----- > > From: "Joe Thomas" > > To: "'Alex Huppenthal'" ; "Archinaco, Chris" > > > > Cc: > > Sent: Friday, April 06, 2001 9:49 AM > > Subject: RE: SR100069960 - Linux resources > > > > > > > > > > The API for the 200E line of adapters is available as > > > ftp://ftp.fore.com/pub/docs/port/aali.pdf. I just checked and > > > it is dated May 1997. This document never did list what the > > > changes from microcode rev to rev were, they simply put out > > > a new document. Quite some time ago, Fore posted info on obtaining > > > driver source and documentation for their new HE line of adapters. > > > The HE is not really an API since you'd be talking straight to the > > > adapters registers, etc. as opposed to talking to a microcode app > > > on the 200E line. I assume someone actively doing HE development > > > on Linux could point you to the right specs, else someone at Macroni, > > > and if all else fails, I could go through my archives but that would > > > take some time to do... > > > > > > [Having done the initial FreeBSD FORE driver, I can attempt to > > > answer questions as my job/time permits. I do not have any access > > > to ATM equipment which would allow me to test anything, let alone > > > do any kind of debug/development work. Fortunately, there have been > > > several other folks who are active on the list that have stepped up > > > to the task so hats off to them! Did you see the comments I replied > > > with yesterday about examining IP mbufs as they come into > ipatm_output()? > > > This would be the place to start determining who's doing the > fragmenting.] > > > > > > Joseph Thomas > > > > > > -----Original Message----- > > > From: Alex Huppenthal [mailto:alex@aspenworks.com] > > > Sent: Friday, April 06, 2001 10:32 AM > > > To: Archinaco, Chris > > > Cc: freebsd-atm@FreeBSD.ORG > > > Subject: Re: SR100069960 - Linux resources > > > > > > > > > Chris, > > > > > > Thanks a million for this info. I'm still stuggling a bit with the BSD > > > driver and wonder if you can shed some light on how the ForeRunner card > > > actually operates now days. Is there a place we can look to find > > > documentation on the API to the card? Perhaps including a list of > > functional > > > changes made to PCA200E recently? > > > > > > I'm excited about using this card in a number of installations. > > Currently, > > > the FreeBSD version of the driver seems to fragment PDUs in a way which > > > Xedia routers (lucent) interpret as a 'tiny fragment' attack. At that > > point > > > they discard the entire PDU. > > > > > > New development is going on and I just wonder if you have information > > which > > > could verify how things work. > > > > > > I'm copying the group which is currently very interested in making > > FreeBSD > > > a high performance platform using your ATM PCI solution. > > > > > > Thank you, > > > > > > Alex > > > > > > PS: to listen in on the discussion about FreeBSD and ATM.. Send an email > > to: > > > mailto:subscribe-freebsd-atm@freebsd.org > > > > > > > > > ----- Original Message ----- > > > From: "Archinaco, Chris" > > > To: > > > Sent: Wednesday, March 14, 2001 2:41 PM > > > Subject: FW: SR100069960 - Linux resources > > > > > > > > > > > Hi Alex, > > > > > > > > > > Here are the Linux resources I was telling you about. I asked the > > > > > TSE who was running the PCA on Linux about FreeBSD but he told me > that > > > he > > > > > had never actually tried it with our adapter. Let me know if you > have > > > any > > > > > problems getting the source via Tactics Online. Let me know if you > > have > > > > > any questions. > > > > > > > > > > > > > > > LINUX Adapter code for Marconi ATM adapters. > > > > > The following are listed as a convenience for persons interested in > > > LINUX > > > > > drivers available for Marconi ATM Cards. Marconi assumes no > liability > > > for > > > > > the utilization of any of the software referenced. > > > > > The referencing of this software should not be construed as an > > > endorsement > > > > > by Marconi for the use of the software or appropriateness of purpose > > for > > > > > any particular task. > > > > > These are not the only drivers available. > > > > > > > > > > HE-series card driver: > > > > > > > > > > > > > > > PCA200E card driver: > > > > > > > > > > > > > > > LE25/155 card driver: > > > > > > > > > > > > > > > Linux ATM Resources (Help on installation): > > > > > > > > > > > > > > > Hope this helps, > > > > > > > > > > Chris > > > > > > > > > > Chris Archinaco > > > > > Level 2 Technical Support Engineer - Edge Products > > > > > Marconi Services > > > > > phone: (800) 671-3673 > > > > > fax: (724) 742-6275 > > > > > email: chris.archinaco@marconi.com > > > > > URL: http://www.marconi.com > > > > > Tactics Online: http://tactics.marconi.com > > > > > > > > > > > > > > > > > > > > > > > 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 > > > > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Mon Apr 9 10:24:37 2001 Delivered-To: freebsd-atm@freebsd.org Received: from aspenworks.com (aspenworks.com [192.94.236.1]) by hub.freebsd.org (Postfix) with ESMTP id 2208337B422 for ; Mon, 9 Apr 2001 10:24:22 -0700 (PDT) (envelope-from alex@aspenworks.com) Received: from d7k (matrix.aspenworks.com [216.38.199.82]) by aspenworks.com (8.9.3/8.9.3) with SMTP id LAA09530; Mon, 9 Apr 2001 11:24:16 -0600 (MDT) (envelope-from alex@aspenworks.com) Message-ID: <008601c0c119$e6f234f0$1700a8c0@d7k> From: "Alex Huppenthal" To: "Joe Thomas" , "Archinaco, Chris" Cc: References: <67DB78CE91D7D41190A100508BFDF5E051EF1A@esply03.cnt.com> Subject: Re: SR100069960 - Linux resources Date: Mon, 9 Apr 2001 11:24:13 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org oops atm_if.h:#define ATM_NIF_MTU 9180 /* Default network interface MTU * has that NIF_MTU set properly. ----- Original Message ----- From: "Joe Thomas" To: "'Alex Huppenthal'" ; "Archinaco, Chris" Cc: Sent: Monday, April 09, 2001 10:09 AM Subject: RE: SR100069960 - Linux resources > Well, having a MTU of size 48 is going to be the cause of the > fragmentation problem. I don't know why the interface would > come up with that value since it's supposed to be set at 9180. > [This is done in the sys/netatm/atm_if.c module when the IP interfaces > are defined and associated with the physical ATM interface (such as > hfa0 for a FORE adapter).] > > Yeah, it can't be set with the ifconfig command because the > SIOCSIFMTU > case isn't supported. As I recall, we chose to not allow it because of the > difficulty in propagating the MTU everywhere. With UNI, the MTU size is also > used to define forward and backward packet sizes in UNI SETUP messages so > that > the ATM network can ensure there's enough buffering available. If one > changed > the MTU size on the fly, you would be expected to close down any open VCs > across that interface and reopen them with the new value. > > This really confuses me as to how/why the MTU is being set to 48. > Can you check for ATM_NIF_MTU in sys/netatm/atm_if.*? It should be defined > to 9180 in the .h file and you should see a line like > atm_if.c: ifp->if_mtu = ATM_NIF_MTU; > in the .c file. The other thing that might be interesting to try is to bump > up the number of IP/ATM interfaces in your rc.conf file. Somewhere there'll > be a line similar to 'atm_netif_hfa0="atm 1"' where hfa0 is the physical > ATM interface (hea0 for Efficient), 'atm' is the name to be used for the > IP interface (what'll see with ifconfig), and 1 is the number of logical > IP interfaces to create. In this example, one IP interface named 'atm0' will > be created. Increment this by one or two and then reboot. Right after the > system comes up, check the MTU sizes with 'ifconfig -a' again. If the new > interfaces have the correct MTU size (9180), then something's happening to > change the MTU after the system is up. If the new interfaces have the MTU > size of 48, then the value being set when the interface is created is wrong. > This might at least give folks an idea of where to start looking... > > Joe > > -----Original Message----- > From: Alex Huppenthal [mailto:alex@aspenworks.com] > Sent: Friday, April 06, 2001 7:37 PM > To: Joe Thomas; Archinaco, Chris > Cc: freebsd-atm@FreeBSD.ORG > Subject: Re: SR100069960 - Linux resources > > > MTU shows up as 48. > > Can't change the MTU with ifconfig > > -Alex > > Thanks to everyone for the insight and information today. > > > ----- Original Message ----- > From: "Joe Thomas" > To: "'Alex Huppenthal'" ; "Archinaco, Chris" > > Cc: > Sent: Friday, April 06, 2001 10:18 AM > Subject: RE: SR100069960 - Linux resources > > > > > > The microcode was embedded as a .h structure sometime in mid/late > > FBSD 3.x so no more having to download the "correct" version. To > > the best of my knowledge, the microcode used has not changed since > > we released the driver. Any improvement you see in your problem by > > backing down to FBSD 3.5 will be because of IP changes between 3.5 > > and 4.X, not from microcode or device driver changes. [The problems > > in the device driver between 3.5/4.0 and 4.1+ were because of mbuf > > structure changes which caused some problems with how the driver > > reserves space for passing tokens/etc. with the buffers, and with > > a corresponding change that caused a problem with how we used some > > space in the pkthdr structure where our assumptions about who and > > when those fields were used were no longer valid. The driver doesn't > > and never did try to do IP fragmentation. Someone mentioned examining > > the MTU size. This would be on the IPATM interface -- check with > > 'ifconfig -a'.] > > > > Joe > > > > -----Original Message----- > > From: Alex Huppenthal [mailto:alex@aspenworks.com] > > Sent: Friday, April 06, 2001 11:07 AM > > To: Joe Thomas; Archinaco, Chris > > Cc: freebsd-atm@FreeBSD.ORG > > Subject: Re: SR100069960 - Linux resources > > > > > > Yes, thank you for your suggestion on how to debug the driver via mbuf > > dumps. I can only hope I'm able to do that. :-) Its been many moons since > I > > did any kernal debugging. Perhaps Chis at Marconi can shed some light on > > microcode revs too. Perhaps I'm using downloadable microcode that's not > the > > right revision. > > > > I know people have said 3.5 FreeBSD runs the ATM PCA200e well. Perhaps I > > should just move back to that OS.. Forward sounds better though. > > > > > > ----- Original Message ----- > > From: "Joe Thomas" > > To: "'Alex Huppenthal'" ; "Archinaco, Chris" > > > > Cc: > > Sent: Friday, April 06, 2001 9:49 AM > > Subject: RE: SR100069960 - Linux resources > > > > > > > > > > The API for the 200E line of adapters is available as > > > ftp://ftp.fore.com/pub/docs/port/aali.pdf. I just checked and > > > it is dated May 1997. This document never did list what the > > > changes from microcode rev to rev were, they simply put out > > > a new document. Quite some time ago, Fore posted info on obtaining > > > driver source and documentation for their new HE line of adapters. > > > The HE is not really an API since you'd be talking straight to the > > > adapters registers, etc. as opposed to talking to a microcode app > > > on the 200E line. I assume someone actively doing HE development > > > on Linux could point you to the right specs, else someone at Macroni, > > > and if all else fails, I could go through my archives but that would > > > take some time to do... > > > > > > [Having done the initial FreeBSD FORE driver, I can attempt to > > > answer questions as my job/time permits. I do not have any access > > > to ATM equipment which would allow me to test anything, let alone > > > do any kind of debug/development work. Fortunately, there have been > > > several other folks who are active on the list that have stepped up > > > to the task so hats off to them! Did you see the comments I replied > > > with yesterday about examining IP mbufs as they come into > ipatm_output()? > > > This would be the place to start determining who's doing the > fragmenting.] > > > > > > Joseph Thomas > > > > > > -----Original Message----- > > > From: Alex Huppenthal [mailto:alex@aspenworks.com] > > > Sent: Friday, April 06, 2001 10:32 AM > > > To: Archinaco, Chris > > > Cc: freebsd-atm@FreeBSD.ORG > > > Subject: Re: SR100069960 - Linux resources > > > > > > > > > Chris, > > > > > > Thanks a million for this info. I'm still stuggling a bit with the BSD > > > driver and wonder if you can shed some light on how the ForeRunner card > > > actually operates now days. Is there a place we can look to find > > > documentation on the API to the card? Perhaps including a list of > > functional > > > changes made to PCA200E recently? > > > > > > I'm excited about using this card in a number of installations. > > Currently, > > > the FreeBSD version of the driver seems to fragment PDUs in a way which > > > Xedia routers (lucent) interpret as a 'tiny fragment' attack. At that > > point > > > they discard the entire PDU. > > > > > > New development is going on and I just wonder if you have information > > which > > > could verify how things work. > > > > > > I'm copying the group which is currently very interested in making > > FreeBSD > > > a high performance platform using your ATM PCI solution. > > > > > > Thank you, > > > > > > Alex > > > > > > PS: to listen in on the discussion about FreeBSD and ATM.. Send an email > > to: > > > mailto:subscribe-freebsd-atm@freebsd.org > > > > > > > > > ----- Original Message ----- > > > From: "Archinaco, Chris" > > > To: > > > Sent: Wednesday, March 14, 2001 2:41 PM > > > Subject: FW: SR100069960 - Linux resources > > > > > > > > > > > Hi Alex, > > > > > > > > > > Here are the Linux resources I was telling you about. I asked the > > > > > TSE who was running the PCA on Linux about FreeBSD but he told me > that > > > he > > > > > had never actually tried it with our adapter. Let me know if you > have > > > any > > > > > problems getting the source via Tactics Online. Let me know if you > > have > > > > > any questions. > > > > > > > > > > > > > > > LINUX Adapter code for Marconi ATM adapters. > > > > > The following are listed as a convenience for persons interested in > > > LINUX > > > > > drivers available for Marconi ATM Cards. Marconi assumes no > liability > > > for > > > > > the utilization of any of the software referenced. > > > > > The referencing of this software should not be construed as an > > > endorsement > > > > > by Marconi for the use of the software or appropriateness of purpose > > for > > > > > any particular task. > > > > > These are not the only drivers available. > > > > > > > > > > HE-series card driver: > > > > > > > > > > > > > > > PCA200E card driver: > > > > > > > > > > > > > > > LE25/155 card driver: > > > > > > > > > > > > > > > Linux ATM Resources (Help on installation): > > > > > > > > > > > > > > > Hope this helps, > > > > > > > > > > Chris > > > > > > > > > > Chris Archinaco > > > > > Level 2 Technical Support Engineer - Edge Products > > > > > Marconi Services > > > > > phone: (800) 671-3673 > > > > > fax: (724) 742-6275 > > > > > email: chris.archinaco@marconi.com > > > > > URL: http://www.marconi.com > > > > > Tactics Online: http://tactics.marconi.com > > > > > > > > > > > > > > > > > > > > > > > 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 > > > > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Mon Apr 9 10:33:11 2001 Delivered-To: freebsd-atm@freebsd.org Received: from esply02.cnt.com (mailhost.cnt.com [139.93.128.21]) by hub.freebsd.org (Postfix) with ESMTP id 77F8637B423 for ; Mon, 9 Apr 2001 10:32:59 -0700 (PDT) (envelope-from joe_thomas@cnt.com) Received: by esply02.cnt.com with Internet Mail Service (5.5.2650.21) id <2SFGMV0V>; Mon, 9 Apr 2001 12:36:00 -0500 Message-ID: <67DB78CE91D7D41190A100508BFDF5E051EF1B@esply03.cnt.com> From: Joe Thomas To: 'Alex Huppenthal' , "Archinaco, Chris" Cc: freebsd-atm@FreeBSD.ORG Subject: RE: SR100069960 - Linux resources Date: Mon, 9 Apr 2001 12:35:21 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The extra 8 bytes allows for some overhead when setting up the forward and backward sizes which reserve network resources as part of the VC SETUP. If I recall correctly, this allows the AAL overhead to be passed. Otherwise, when you took your IP PDU and encapsulated it in the AAL layer, you couldn't guarantee that there would be room for the extra AAL info to make it across the network. Unless ATM_NIF_MTU has been redefined, you IP/ATM interfaces ought to have an MTU of 9180, not 48. -----Original Message----- From: Alex Huppenthal [mailto:alex@aspenworks.com] Sent: Monday, April 09, 2001 12:23 PM To: Joe Thomas; Archinaco, Chris Cc: freebsd-atm@FreeBSD.ORG Subject: Re: SR100069960 - Linux resources This is what my system says: fore.h:#define FORE_IFF_MTU 9188 /* Network interface MTU */ what's the extra 8 bytes for? Perhaps a part of a fragment later.. I see ifp->if_mtu = ATM_NIF_MTU; in atm_if.c ----- Original Message ----- From: "Joe Thomas" To: "'Alex Huppenthal'" ; "Archinaco, Chris" Cc: Sent: Monday, April 09, 2001 10:09 AM Subject: RE: SR100069960 - Linux resources > Well, having a MTU of size 48 is going to be the cause of the > fragmentation problem. I don't know why the interface would > come up with that value since it's supposed to be set at 9180. > [This is done in the sys/netatm/atm_if.c module when the IP interfaces > are defined and associated with the physical ATM interface (such as > hfa0 for a FORE adapter).] > > Yeah, it can't be set with the ifconfig command because the > SIOCSIFMTU > case isn't supported. As I recall, we chose to not allow it because of the > difficulty in propagating the MTU everywhere. With UNI, the MTU size is also > used to define forward and backward packet sizes in UNI SETUP messages so > that > the ATM network can ensure there's enough buffering available. If one > changed > the MTU size on the fly, you would be expected to close down any open VCs > across that interface and reopen them with the new value. > > This really confuses me as to how/why the MTU is being set to 48. > Can you check for ATM_NIF_MTU in sys/netatm/atm_if.*? It should be defined > to 9180 in the .h file and you should see a line like > atm_if.c: ifp->if_mtu = ATM_NIF_MTU; > in the .c file. The other thing that might be interesting to try is to bump > up the number of IP/ATM interfaces in your rc.conf file. Somewhere there'll > be a line similar to 'atm_netif_hfa0="atm 1"' where hfa0 is the physical > ATM interface (hea0 for Efficient), 'atm' is the name to be used for the > IP interface (what'll see with ifconfig), and 1 is the number of logical > IP interfaces to create. In this example, one IP interface named 'atm0' will > be created. Increment this by one or two and then reboot. Right after the > system comes up, check the MTU sizes with 'ifconfig -a' again. If the new > interfaces have the correct MTU size (9180), then something's happening to > change the MTU after the system is up. If the new interfaces have the MTU > size of 48, then the value being set when the interface is created is wrong. > This might at least give folks an idea of where to start looking... > > Joe > > -----Original Message----- > From: Alex Huppenthal [mailto:alex@aspenworks.com] > Sent: Friday, April 06, 2001 7:37 PM > To: Joe Thomas; Archinaco, Chris > Cc: freebsd-atm@FreeBSD.ORG > Subject: Re: SR100069960 - Linux resources > > > MTU shows up as 48. > > Can't change the MTU with ifconfig > > -Alex > > Thanks to everyone for the insight and information today. > > > ----- Original Message ----- > From: "Joe Thomas" > To: "'Alex Huppenthal'" ; "Archinaco, Chris" > > Cc: > Sent: Friday, April 06, 2001 10:18 AM > Subject: RE: SR100069960 - Linux resources > > > > > > The microcode was embedded as a .h structure sometime in mid/late > > FBSD 3.x so no more having to download the "correct" version. To > > the best of my knowledge, the microcode used has not changed since > > we released the driver. Any improvement you see in your problem by > > backing down to FBSD 3.5 will be because of IP changes between 3.5 > > and 4.X, not from microcode or device driver changes. [The problems > > in the device driver between 3.5/4.0 and 4.1+ were because of mbuf > > structure changes which caused some problems with how the driver > > reserves space for passing tokens/etc. with the buffers, and with > > a corresponding change that caused a problem with how we used some > > space in the pkthdr structure where our assumptions about who and > > when those fields were used were no longer valid. The driver doesn't > > and never did try to do IP fragmentation. Someone mentioned examining > > the MTU size. This would be on the IPATM interface -- check with > > 'ifconfig -a'.] > > > > Joe > > > > -----Original Message----- > > From: Alex Huppenthal [mailto:alex@aspenworks.com] > > Sent: Friday, April 06, 2001 11:07 AM > > To: Joe Thomas; Archinaco, Chris > > Cc: freebsd-atm@FreeBSD.ORG > > Subject: Re: SR100069960 - Linux resources > > > > > > Yes, thank you for your suggestion on how to debug the driver via mbuf > > dumps. I can only hope I'm able to do that. :-) Its been many moons since > I > > did any kernal debugging. Perhaps Chis at Marconi can shed some light on > > microcode revs too. Perhaps I'm using downloadable microcode that's not > the > > right revision. > > > > I know people have said 3.5 FreeBSD runs the ATM PCA200e well. Perhaps I > > should just move back to that OS.. Forward sounds better though. > > > > > > ----- Original Message ----- > > From: "Joe Thomas" > > To: "'Alex Huppenthal'" ; "Archinaco, Chris" > > > > Cc: > > Sent: Friday, April 06, 2001 9:49 AM > > Subject: RE: SR100069960 - Linux resources > > > > > > > > > > The API for the 200E line of adapters is available as > > > ftp://ftp.fore.com/pub/docs/port/aali.pdf. I just checked and > > > it is dated May 1997. This document never did list what the > > > changes from microcode rev to rev were, they simply put out > > > a new document. Quite some time ago, Fore posted info on obtaining > > > driver source and documentation for their new HE line of adapters. > > > The HE is not really an API since you'd be talking straight to the > > > adapters registers, etc. as opposed to talking to a microcode app > > > on the 200E line. I assume someone actively doing HE development > > > on Linux could point you to the right specs, else someone at Macroni, > > > and if all else fails, I could go through my archives but that would > > > take some time to do... > > > > > > [Having done the initial FreeBSD FORE driver, I can attempt to > > > answer questions as my job/time permits. I do not have any access > > > to ATM equipment which would allow me to test anything, let alone > > > do any kind of debug/development work. Fortunately, there have been > > > several other folks who are active on the list that have stepped up > > > to the task so hats off to them! Did you see the comments I replied > > > with yesterday about examining IP mbufs as they come into > ipatm_output()? > > > This would be the place to start determining who's doing the > fragmenting.] > > > > > > Joseph Thomas > > > > > > -----Original Message----- > > > From: Alex Huppenthal [mailto:alex@aspenworks.com] > > > Sent: Friday, April 06, 2001 10:32 AM > > > To: Archinaco, Chris > > > Cc: freebsd-atm@FreeBSD.ORG > > > Subject: Re: SR100069960 - Linux resources > > > > > > > > > Chris, > > > > > > Thanks a million for this info. I'm still stuggling a bit with the BSD > > > driver and wonder if you can shed some light on how the ForeRunner card > > > actually operates now days. Is there a place we can look to find > > > documentation on the API to the card? Perhaps including a list of > > functional > > > changes made to PCA200E recently? > > > > > > I'm excited about using this card in a number of installations. > > Currently, > > > the FreeBSD version of the driver seems to fragment PDUs in a way which > > > Xedia routers (lucent) interpret as a 'tiny fragment' attack. At that > > point > > > they discard the entire PDU. > > > > > > New development is going on and I just wonder if you have information > > which > > > could verify how things work. > > > > > > I'm copying the group which is currently very interested in making > > FreeBSD > > > a high performance platform using your ATM PCI solution. > > > > > > Thank you, > > > > > > Alex > > > > > > PS: to listen in on the discussion about FreeBSD and ATM.. Send an email > > to: > > > mailto:subscribe-freebsd-atm@freebsd.org > > > > > > > > > ----- Original Message ----- > > > From: "Archinaco, Chris" > > > To: > > > Sent: Wednesday, March 14, 2001 2:41 PM > > > Subject: FW: SR100069960 - Linux resources > > > > > > > > > > > Hi Alex, > > > > > > > > > > Here are the Linux resources I was telling you about. I asked the > > > > > TSE who was running the PCA on Linux about FreeBSD but he told me > that > > > he > > > > > had never actually tried it with our adapter. Let me know if you > have > > > any > > > > > problems getting the source via Tactics Online. Let me know if you > > have > > > > > any questions. > > > > > > > > > > > > > > > LINUX Adapter code for Marconi ATM adapters. > > > > > The following are listed as a convenience for persons interested in > > > LINUX > > > > > drivers available for Marconi ATM Cards. Marconi assumes no > liability > > > for > > > > > the utilization of any of the software referenced. > > > > > The referencing of this software should not be construed as an > > > endorsement > > > > > by Marconi for the use of the software or appropriateness of purpose > > for > > > > > any particular task. > > > > > These are not the only drivers available. > > > > > > > > > > HE-series card driver: > > > > > > > > > > > > > > > PCA200E card driver: > > > > > > > > > > > > > > > LE25/155 card driver: > > > > > > > > > > > > > > > Linux ATM Resources (Help on installation): > > > > > > > > > > > > > > > Hope this helps, > > > > > > > > > > Chris > > > > > > > > > > Chris Archinaco > > > > > Level 2 Technical Support Engineer - Edge Products > > > > > Marconi Services > > > > > phone: (800) 671-3673 > > > > > fax: (724) 742-6275 > > > > > email: chris.archinaco@marconi.com > > > > > URL: http://www.marconi.com > > > > > Tactics Online: http://tactics.marconi.com > > > > > > > > > > > > > > > > > > > > > > > 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 > > > > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Wed Apr 11 19:14:57 2001 Delivered-To: freebsd-atm@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id E335A37B424 for ; Wed, 11 Apr 2001 19:14:54 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id f3C2EpK17459; Wed, 11 Apr 2001 19:14:51 -0700 (PDT) Date: Wed, 11 Apr 2001 19:14:51 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200104120214.f3C2EpK17459@portnoy.lbl.gov> To: brandt@fokus.gmd.de, freebsd-atm@FreeBSD.ORG Subject: Re: ForeRunnerHE Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It should be available at www.marconi.com. I do not have details in my hand, but I will dig out what is the current status. I have discontinued working on it since GigE NIC is much cheaper and has copper interface instead of using fiber. Once I can find the document site, I will upload the FreeBSD driver to there, and send you a note, then you can download it from there. -Jin > does anybody know whether there is documentation available on the API of > these cards? I may want to port the Linux driver or implement a new one. > > 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 From owner-freebsd-atm Fri Apr 13 20:57:26 2001 Delivered-To: freebsd-atm@freebsd.org Received: from zehn.mine.nu (ad202.166.108.108.magix.com.sg [202.166.108.108]) by hub.freebsd.org (Postfix) with ESMTP id 671F337B446 for ; Fri, 13 Apr 2001 20:57:23 -0700 (PDT) (envelope-from bennyc@magix.com.sg) Received: (from bennyc@localhost) by zehn.mine.nu (8.9.3/8.9.3) id LAA08941 for freebsd-atm@freebsd.org; Sat, 14 Apr 2001 11:44:40 +0800 Date: Sat, 14 Apr 2001 11:44:40 +0800 From: Benny Chee To: freebsd-atm@freebsd.org Subject: ForeRunner PCA200E on 4.2 Message-ID: <20010414114440.A8908@magix.com.sg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i-nntp Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, i just started setting up my freebsd box on a 4.2 and placed a FORE PCA200E card on it, connected to a Fore 200BX ATM switch and with the following kernel options, i managed to get it to recognize my card. options ATM_CORE #core ATM protocol family options ATM_IP #IP over ATM support options ATM_SIGPVC #SIGPVC signalling manager options ATM_SPANS #SPANS signalling manager options ATM_UNI #UNI signalling manager device hfa #FORE PCA-200E ATM PCI i pulled out the atm-config.sh file from /usr/share/examples/atm and did some modifications on it. I intend to configure my ATM card to do both SVC and PVC. ie have it point to an arpserver (SVC), and running a PVC all the way to an ATM router. Something like this: /sbin/fore_dnld -d /etc /sbin/atm set netif hfa0 atm 2 /sbin/atm attach hfa0 uni31 /sbin/ilmid # Interface atm0 is configure to run SVC # # This interface points to a arpserver with the following NSAP address # /sbin/ifconfig atm0 10.0.0.10 255.255.255.0 up /sbin/atm set arpserver atm0 47.000004621010023f.0000.0000.004621010051.01 # Interface atm1 is configure to run PVC to an ATM router # /sbin/ifconfig atm1 192.168.0.10 255.255.255.0 up /sbin/atm add pvc hfa0 0 100 aal5 null ip atm1 192.168.0.10 exit 0 I just can't seem to get any interface up. Is there something i missed out? Does it have to point to an arpserver ip address (10.0.0.1) as well? Do i have to run atmarpd? Or is there something wrong with my syntax? -- Benny Chee PGP KeyID: E4533B55 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Sat Apr 14 11:20:18 2001 Delivered-To: freebsd-atm@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id AE70937B449 for ; Sat, 14 Apr 2001 11:20:15 -0700 (PDT) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id LAA72710; Sat, 14 Apr 2001 11:20:05 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Sat, 14 Apr 2001 11:20:04 -0700 (PDT) From: Richard Hodges To: Benny Chee Cc: freebsd-atm@FreeBSD.ORG Subject: Re: ForeRunner PCA200E on 4.2 In-Reply-To: <20010414114440.A8908@magix.com.sg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 14 Apr 2001, Benny Chee wrote: > /sbin/fore_dnld -d /etc > /sbin/atm set netif hfa0 atm 2 > /sbin/atm attach hfa0 uni31 > /sbin/ilmid That looks fine. > # Interface atm0 is configure to run SVC # > # This interface points to a arpserver with the following NSAP address # > /sbin/ifconfig atm0 10.0.0.10 255.255.255.0 up > /sbin/atm set arpserver atm0 47.000004621010023f.0000.0000.004621010051.01 > > # Interface atm1 is configure to run PVC to an ATM router # > /sbin/ifconfig atm1 192.168.0.10 255.255.255.0 up > /sbin/atm add pvc hfa0 0 100 aal5 null ip atm1 192.168.0.10 That also looks fine. > I just can't seem to get any interface up. What seems to be the problem? Do you get an error message? What does it say? Or does everything look "normal", but packets just disappear? If this is the case, I suggest using the PCA200E patch I posted: http://www.freebsd.org/cgi/query-pr.cgi?pr=23620 > Does it have to point to an arpserver ip address (10.0.0.1) as well? > Do i have to run atmarpd? Or is there something wrong with my syntax? No, no, no, it looks like you are doing everyting right... The information from these might help: atm sho conf atm sho int atm sho stat vcc atm sho stat int All the best, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Sat Apr 14 11:53:48 2001 Delivered-To: freebsd-atm@freebsd.org Received: from aspenworks.com (aspenworks.com [192.94.236.1]) by hub.freebsd.org (Postfix) with ESMTP id 00DC237B43F for ; Sat, 14 Apr 2001 11:53:45 -0700 (PDT) (envelope-from alex@aspenworks.com) Received: from d7k (matrix.aspenworks.com [216.38.199.82]) by aspenworks.com (8.9.3/8.9.3) with SMTP id MAA08419; Sat, 14 Apr 2001 12:53:23 -0600 (MDT) (envelope-from alex@aspenworks.com) Message-ID: <003b01c0c514$20b4c6f0$1700a8c0@d7k> From: "Alex Huppenthal" To: "Richard Hodges" , "Benny Chee" Cc: References: Subject: Re: ForeRunner PCA200E on 4.2 Date: Sat, 14 Apr 2001 12:52:59 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Benny and other readers, I'm not sure if Richard's patch was applied to the 4.2 version. Can any comment on the state of the Fore Driver in 4.2? I ended up patching the driver with Richard's fix on the FreeBSD site. Has that patch ever been released? Do we need to be running 4.-current ? Are you seeing PDUs in only one direction? I echo Richard's questions. My fragmentation problem still exists. I'm updating the entire OS to FreeBSD 4 - current to check behavior re: tiny fragment errors. The version in use right now is 4.2 of March 20th fame. It supports the Dell RAID controller. -Alex ----- Original Message ----- From: "Richard Hodges" To: "Benny Chee" Cc: Sent: Saturday, April 14, 2001 12:20 PM Subject: Re: ForeRunner PCA200E on 4.2 > On Sat, 14 Apr 2001, Benny Chee wrote: > > > /sbin/fore_dnld -d /etc > > /sbin/atm set netif hfa0 atm 2 > > /sbin/atm attach hfa0 uni31 > > /sbin/ilmid > > That looks fine. > > > # Interface atm0 is configure to run SVC # > > # This interface points to a arpserver with the following NSAP address # > > /sbin/ifconfig atm0 10.0.0.10 255.255.255.0 up > > /sbin/atm set arpserver atm0 47.000004621010023f.0000.0000.004621010051.01 > > > > # Interface atm1 is configure to run PVC to an ATM router # > > /sbin/ifconfig atm1 192.168.0.10 255.255.255.0 up > > /sbin/atm add pvc hfa0 0 100 aal5 null ip atm1 192.168.0.10 > > That also looks fine. > > > I just can't seem to get any interface up. > > What seems to be the problem? Do you get an error message? What > does it say? > > Or does everything look "normal", but packets just disappear? > If this is the case, I suggest using the PCA200E patch I posted: > http://www.freebsd.org/cgi/query-pr.cgi?pr=23620 > > > Does it have to point to an arpserver ip address (10.0.0.1) as well? > > Do i have to run atmarpd? Or is there something wrong with my syntax? > > No, no, no, it looks like you are doing everyting right... > > The information from these might help: > > atm sho conf > atm sho int > atm sho stat vcc > atm sho stat int > > All the best, > > -Richard > > ------------------------------------------- > Richard Hodges | Matriplex, inc. > Product Manager | 769 Basque Way > rh@matriplex.com | Carson City, NV 89706 > 775-886-6477 | www.matriplex.com > > > 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 From owner-freebsd-atm Sat Apr 14 12: 0: 7 2001 Delivered-To: freebsd-atm@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 33AEC37B42C for ; Sat, 14 Apr 2001 12:00:02 -0700 (PDT) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id LAA72787; Sat, 14 Apr 2001 11:59:51 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Sat, 14 Apr 2001 11:59:51 -0700 (PDT) From: Richard Hodges To: Alex Huppenthal Cc: Benny Chee , freebsd-atm@FreeBSD.ORG Subject: Re: ForeRunner PCA200E on 4.2 In-Reply-To: <003b01c0c514$20b4c6f0$1700a8c0@d7k> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 14 Apr 2001, Alex Huppenthal wrote: > Benny and other readers, > > I'm not sure if Richard's patch was applied to the 4.2 version. No, it is not in 4.2 > Can any comment on the state of the Fore Driver in 4.2? I ended up > patching the driver with Richard's fix on the FreeBSD site. Has that > patch ever been released? As far as I know, none of the committers want to touch it :-( I wrote twice to -hackers asking *someone* to commit it to -stable so that it might be included in 4.3 The second message got a couple responses, but as far as I know, it is still in limbo. Sorry, I still don't have any idea about the tiny fragments... All the best, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Sat Apr 14 19:45:25 2001 Delivered-To: freebsd-atm@freebsd.org Received: from zehn.mine.nu (ad202.166.108.33.magix.com.sg [202.166.108.33]) by hub.freebsd.org (Postfix) with ESMTP id E017D37B423 for ; Sat, 14 Apr 2001 19:45:21 -0700 (PDT) (envelope-from bennyc@magix.com.sg) Received: (from bennyc@localhost) by zehn.mine.nu (8.9.3/8.9.3) id KAA16031; Sun, 15 Apr 2001 10:32:35 +0800 Date: Sun, 15 Apr 2001 10:32:35 +0800 From: Benny Chee To: Richard Hodges Cc: Alex Huppenthal , freebsd-atm@FreeBSD.ORG Subject: Re: ForeRunner PCA200E on 4.2 Message-ID: <20010415103235.A16019@magix.com.sg> References: <003b01c0c514$20b4c6f0$1700a8c0@d7k> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i-nntp In-Reply-To: ; from rh@matriplex.com on Sat, Apr 14, 2001 at 11:59:51AM -0700 Organization: Singapore Telecommunications Ltd Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rich, spare a link for that patch? Benny On Sat, Apr 14, 2001 at 11:59:51AM -0700, Richard Hodges wrote: | On Sat, 14 Apr 2001, Alex Huppenthal wrote: | | > Benny and other readers, | > | > I'm not sure if Richard's patch was applied to the 4.2 version. | | No, it is not in 4.2 | | > Can any comment on the state of the Fore Driver in 4.2? I ended up | > patching the driver with Richard's fix on the FreeBSD site. Has that | > patch ever been released? | | As far as I know, none of the committers want to touch it :-( I wrote | twice to -hackers asking *someone* to commit it to -stable so that it | might be included in 4.3 The second message got a couple responses, | but as far as I know, it is still in limbo. | | Sorry, I still don't have any idea about the tiny fragments... | | All the best, | | -Richard | | ------------------------------------------- | Richard Hodges | Matriplex, inc. | Product Manager | 769 Basque Way | rh@matriplex.com | Carson City, NV 89706 | 775-886-6477 | www.matriplex.com | | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-atm" in the body of the message -- I don't want Perl to be beautiful, I want you to write beautiful programs in Perl. --Larry Wall, Culture of Perl, August 1997 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message From owner-freebsd-atm Sat Apr 14 20:47:16 2001 Delivered-To: freebsd-atm@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id A724137B43E for ; Sat, 14 Apr 2001 20:47:10 -0700 (PDT) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id UAA73516; Sat, 14 Apr 2001 20:47:06 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Sat, 14 Apr 2001 20:47:05 -0700 (PDT) From: Richard Hodges To: Benny Chee Cc: freebsd-atm@FreeBSD.ORG Subject: Re: ForeRunner PCA200E on 4.2 In-Reply-To: <20010415103235.A16019@magix.com.sg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 15 Apr 2001, Benny Chee wrote: > Rich, > > spare a link for that patch? It is in the problem report: http://www.freebsd.org/cgi/query-pr.cgi?pr=23620 But here it is by itself: diff -U5 sys/dev/hfa/fore.h sys.new/dev/hfa/fore.h --- sys/dev/hfa/fore.h Fri Aug 27 17:41:48 1999 +++ sys.new/dev/hfa/fore.h Mon Dec 18 10:26:49 2000 @@ -115,11 +115,11 @@ * BUF_DATA_ALIGN) - BUF1_SM_HDR) * #define BUF1_SM_SIZE MAX(BUF1_SM_LEN - BUF1_SM_DOFF, 64) * */ #if ((BSD >= 199103) && defined(FORE_PCI)) -#define BUF1_SM_DOFF ((BUF1_SM_HOFF + SIZEOF_Buf_handle) - BUF1_SM_HDR) +#define BUF1_SM_DOFF (SIZEOF_Buf_handle) #define BUF1_SM_SIZE (BUF1_SM_LEN - BUF1_SM_DOFF) #endif #if ((BSD < 199103) && defined(FORE_SBUS) && defined(sun4c)) #define BUF1_SM_DOFF (BUF_DATA_ALIGN - BUF1_SM_HDR) #define BUF1_SM_SIZE (BUF1_SM_LEN - BUF1_SM_DOFF) diff -U5 sys/dev/hfa/fore_receive.c sys.new/dev/hfa/fore_receive.c --- sys/dev/hfa/fore_receive.c Fri Aug 27 17:41:51 1999 +++ sys.new/dev/hfa/fore_receive.c Mon Dec 18 10:29:16 2000 @@ -417,10 +417,13 @@ } /* * It looks like we've got a valid PDU - count it quick!! */ + mhead->m_pkthdr.rcvif = NULL; + mhead->m_pkthdr.csum_flags = 0; + mhead->m_pkthdr.aux = NULL; KB_PLENSET(mhead, pdulen); fup->fu_pif.pif_ipdus++; fup->fu_pif.pif_ibytes += pdulen; vcp = fvp->fv_connvc->cvc_vcc; vcp->vc_ipdus++; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message