Thanks for the pointers. Here is what I've tracked it down to. When the octmac kernel modules is loaded (octmac.o) the packet spew begins. Inserting this module manually has the same result as running the ACE load script. I've tried recompiling the driver and made sure that it was truly compiled for the ARM. After a reboot the module seems in insert, repeatably, just fine. After one runs the ./ixstart script the old behavior returns. I tried running through the ./ixstart script by hand several times and was unable to recreate the problem or start the ACEs. Has anyone run into this problem or similar ones in the past? I'm going to try using the kernel modules located in /lib/modules on the card next and see if maybe the versions in /opt/ixasdk/bin/arm-be are bad. Thanks for the comments, Cyrus Hall University of Colorado Software Engineering Research Laboratory On Mon, 2003-02-17 at 18:51, Abhijeet Joglekar wrote:

Cyrus,

...

board will proceed to spit out malformed Ethernet packets (each packet identical) as fast as the interface will allow. This is with the simple packet counting example.

Can you expand a little more on the problem? The Count example should only recv. packets, count and then discard them. Which interface is it spitting packets out on?

...

Is there a bare bones MicroACE, such as the counting example, that actually works on the ENP2505?

I have tried Count, l2bridge and l3fwdr and they work fine. There are not many board dependent commands in the ixsys.config file. Just comment out "interface" commands for all other ports except for 0,1,2,3. Similarly, comment out commands for other ports from the route.config-sys-l3fwdr file or bridge.config-sys-l2bridge file.

And try with "mode = 0".

Also, check out the archives of this list, there was some discussion earlier on this list about running ACE samples on the ENP-2505.

-- abhijeet

Yong- Yea, I've got the ENP-2505 workig pretty well these days. The solution to the packet spew turned out to be rather unexpected. I ended up having to isolate the card on a pure 100 Mbps network, in which it seems to behave quite correctly. Someone else recently had this same problem and fixed it by making sure all network components where 100 Mbps as well. The following e-mail was recently posted by Mick in regards to this issue: -- I'm not sure if this applies to the ENP-2305, but it did affect the IXP1200EB. Some PHY devices default 10MB mode is also loop-back mode, so on a 10MB connection, as soon as a packet is sent by the IXP1200 it gets looped back to the IXP1200, and so the process goes on, the result is a packet flood. The fix was either to connect to a 100MB device so the PHY would auto-negotiate to 100MB, or to program the PHY so that in 10MB mode it wasn't set to loopback. -- Hope that helps, Cyrus On Tue, 2003-04-22 at 00:32, Yong Liu wrote:

Hi, Cyrus

Have you solved the problems? I have similar question. How can we run the examples in IXP SDK on ENP-2505?

Thanks!

----- Original Message ----- From: "Cyrus Hall" To: Sent: Wednesday, February 19, 2003 4:22 PM Subject: Re: [ixp1200] ENP2505 Example Issues

...

Thanks for the pointers. Here is what I've tracked it down to. When the octmac kernel modules is loaded (octmac.o) the packet spew begins. Inserting this module manually has the same result as running the ACE load script. I've tried recompiling the driver and made sure that it was truly compiled for the ARM. After a reboot the module seems in insert, repeatably, just fine. After one runs the ./ixstart script the old behavior returns. I tried running through the ./ixstart script by hand several times and was unable to recreate the problem or start the ACEs.

Has anyone run into this problem or similar ones in the past? I'm going to try using the kernel modules located in /lib/modules on the card next and see if maybe the versions in /opt/ixasdk/bin/arm-be are bad.

Thanks for the comments, Cyrus Hall University of Colorado Software Engineering Research Laboratory

On Mon, 2003-02-17 at 18:51, Abhijeet Joglekar wrote:

...

Cyrus,

...

board will proceed to spit out malformed Ethernet packets (each packet identical) as fast as the interface will allow. This is with the simple packet counting example.

Can you expand a little more on the problem? The Count example should only recv. packets, count and then discard them. Which interface is it spitting packets out on?

...

Is there a bare bones MicroACE, such as the counting example, that actually works on the ENP2505?

I have tried Count, l2bridge and l3fwdr and they work fine. There are not many board dependent commands in the ixsys.config file. Just comment out "interface" commands for all other ports except for 0,1,2,3. Similarly, comment out commands for other ports from the route.config-sys-l3fwdr file or bridge.config-sys-l2bridge file.

And try with "mode = 0".

Also, check out the archives of this list, there was some discussion earlier on this list about running ACE samples on the ENP-2505.

-- abhijeet

-- Cyrus Hall University of Colorado