StarVX WAR Static Routes

[VerilanES]

Taking Lonnie's advice, I setup static routing on my new WAR boards instead of using the bridging. The goal of the configuration was to have each ethernet paired to one of the CM9 cards (I have a pair of 2 card WAR boards). Each CM9 would connect to one of the CM9's on the other WAR board and those CM9's would in turned be pair to the ethernet ports. The application is to create a wireless connection to stream video across and my client would like to have a single 'server' PC on one end of the link, and a single 'client' pc on the other side. In order to maximize throughput, we have decided to use both CM9 cards. There will be multiple video feeds, so please no posts pointing out that IP traffic cannot be split across the cards, then recompiled at the end of the link. We plan on putting two feeds on one link, and two on the other. Each PC will have 2 ehternet addresses to match up with the respective networks I created for the purpose of bridging the devices. I got it up and tested OK, although the speeds are still only in the 27mb/s range. I'm thinking it's a simple issue of how I have my antennas setup.

Anyway, when I was setting up the bridge, I didn't find any threads that described configuring this particular application. Here's my bridging configuration for anyone that is looking at a similar deployment or just wants a reference when configuring a bridge.

Server PC:
Virtual Ethernet 1: IP - 192.168.0.10/24
G/W - 192.168.0.1
Virtual Ethernet 2: IP - 192.168.100.10/24
G/W - 192.168.100.1

Server WAR:
Eth0: IP - 192.168.0.1/24
Eth1: IP - 192.168.100.1/24
WPCI0: IP - 192.168.1.1/24
WPCI1: IP - 192.168.101.1/24

*STATIC ROUTES*
192.168.10.0/24 ->192.168.1.2
192.168.110.0/24 ->192.168.101.2
192.168.100.0/24 ->192.168.100.10
192.168.101.0/24 ->192.168.100.10

Default Gateway - 192.168.0.10

Client WAR:
Eth0: IP - 192.168.10.2/24
Eth1: IP - 192.168.110.2/24
WPCI0: IP - 192.168.1.2/24
WPCI1: IP - 192.168.101.2/24

*STATIC ROUTES*
192.168.10.0/24 ->192.168.10.2
192.168.110.0/24 ->192.168.110.2
192.168.101.0/24 ->192.168.101.1

Default Gateway - 192.168.1.1

Client PC:
Virtual Ethernet 1: IP - 192.168.10.11/24
G/W -192.168.10.2
Virtual Ethernet 2: IP - 192.168.110.11/24
G/W -192.168.110.2

If anyone has any input, or if you spot a redundant route, let me know. As of testing time, I was able to pull a stable 27mb/s through each ethernet port on the client side of the the link.

[RPI]

The static routes from Server to client should read:

Server WAR:
Eth0: IP - 192.168.0.1/24
Eth1: IP - 192.168.100.1/24
WPCI0: IP - 192.168.1.1/24
WPCI1: IP - 192.168.101.1/24

*STATIC ROUTES*
192.168.10.0/24 ->192.168.1.2
192.168.110.0/24 ->192.168.101.2
Default Gateway - none required


Client WAR:
Eth0: IP - 192.168.10.2/24
Eth1: IP - 192.168.110.2/24
WPCI0: IP - 192.168.1.2/24
WPCI1: IP - 192.168.101.2/24

*STATIC ROUTES*
192.168.0.0/24 ->192.168.1.1
192.168.100.0/24 ->192.168.101.1
Default Gateway - none required

In addition, since this application has most traffic running from server to client, the server should be setup in Access Point mode while the client should be set up in Web Client mode. Bridging mode in this 2.X revision is only used when bridging _ALL_ of the interfaces together, wireless and wired.