Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 353 subscribers
  • Views 289 views
  • Users 0 members are here
Related

Picozed enabling second Ethernet port

Former Member

I purchased a Picozed 7030 processor card with an FMC carrier card. The Picozed came preloaded with WIndriver Pulsar Linux.

ifconfig lists three devices: br0, eth0 and lo. I assumed br0 and eth0 correspond to the two Ethernet ports on the FMC carrier since ifconfig shows that br0 and eth0 have unique mac addresses.

I configured eth0 with a static IP address, connect it to a switch that is also connected to a laptop. Communication works fine with this port

I configured br0 with a static IP address, connect it to the same switch and remove the eth0 connection. Communication does not work. But when I connect eth0 to the switch communication over br0 works. When I disconnect br0 but leave eth0 plugged in to the switch communication to br0 works.

I found that br0 is configured as a bridge. When I issue the command: brctl show, it lists br0 as a bridge.

Assuming that br0 corresponds to the second Ethernet port on the FMC, how do I disable the bridge and configure br0 as an independent port?

  • 0

    Hi,

    In Pulsar 7 Linux user space, there are three separate containers that make up the environment:  cube-essential, cube-dom0 and cube-server.  The top level environment is cube-server, which is the one you typically log into at boot.  You can learn more about containers and how they operate at:

    https://knowledge.windriver.com/en-us/000_Products/000/060/000/000/000_Wind_River_Pulsar_Linux_System_Administration_Guide%2C_7.0/020

    Each container may or may not have it's own Ethernet device, but to simplify the interface they are essentially bound together through the br0 construct.  I believe you can think of this as a router, with connections from the containers as internal inputs and a single interface going out to the LAN or Internet on the other side.  The out of the box system is configured to use the Ethernet port on the carrier card, and the second port is not enabled at all.   In Pulsar 8, one of the improvements has been to remove br0 and replace it with the more familiar device eth0 as the top level interface.

    If you want to access the second ethernet port, you would need to modify the hardware platform configuration to enable the second port in the PS.  Then you would modify the device tree to activate the entry for the second port and connect the device driver to a second physical interface.

    Ron