Experimental Physics and
Industrial Control System

Kate Feng <[email protected]> · Thu, 30 Apr 2009 18:17:00 -0400

Hi,

Would it be possible for you to post a report of this to Tech-Talk --

just mention that you're responding to some issues mentioned at this

morning's EPICS collaboration talks.

In order to have two networks ports working independently,
I decided to choose the 2nd port on the private subnet,
which is 172.16.x.x.  The first port could be any public
subnet or a different private subnet (e.g. 10.10.x.x).
How I implement that in RTEMS  is:

static struct rtems_bsdnet_ifconfig netdriver_config[2] = {

 {"gt1",rtems_GT64260eth_driver_attach, netdriver_config+1,}, /* 100

MHz NIC */

 {"IGHZ1",rtems_i82544EI_driver_attach,

0,"172.16.1.2","255.255.255.0",} /* 1GHz NIC */

};

However, I am not sure what will happen if one does not specify the
IP address at the 2nd network port.  I do not remember if I tested it

or not. It was not important for me to test it because for our

applications,

the 2nd port has to be standardized to be an isolated subnet on 172. 16.x.x

from the 1st one for our beamline detectors.

However, I found out that by running both ports , the CPU power could
be eaten up quickly on the mvme5500 board that the performance
could be down on the 1GHz NIC.  Thus, to our applications,
the network optimization is a higher priority task than exploring
an unkown IP address on the 2nd port.

> Also, when you post this report, please mention which version
> of RTEMS and which BSP you were using.

BSP : MVME5500 on any version of  RTEMS, which is higher
than 4.6.0.   However, by utilizing a known IP addresses
on the 2nd port, one should be able to implement it on any BSP.

Cheers,
Kate

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System