Source routing in V3

[nuclearcat]

There is in MATCH-RULES: from, to, nfmar and tos.
As i know in iproute2 there is also "dev". I will explain the idea:

Usually customer have wireless "gateway" setup, this means 1 ethernet, and 1 wireless. To not keep routing tables at all i think more good to do such setup (i will speak in iproute2 language):
lets say we have
wifi0 10.1.1.1/24 , next point is 10.1.1.2/24
eth0 10.1.2.1/24, next point 10.1.2.2/24

ip rule add dev eth0 table 200
ip route add table 200 default via 10.1.1.2
ip route default via 10.1.2.2

Then wireless gateway will looks transparent, and there is also minimum routing tables, this mean less load for host CPU.

Btw. Is in StarV3 bridging works good? It can simplify task, and i will do just bridge, if there no routing required. My preference to run big routing tables on border router, not on poor ARM cpu :)

[nuclearcat]

Thanks for the fast reply.

[lonnie]

As long as you are happy I guess we can feel OK too. Sometimes things slip, thanks for prodding this one for us.

If the wireless is a gateway I would assume default route is to the wireless AP and a simple default route is all you require for the unit to get customer Ethernet traffic sent to the AP. The AP will require that you have a route for the customer Ethernet subnet.

In the 3 weeks since your question we have added full transparent Client mode bridging. It requires our V3 AP and it works very well. Simply add the wireless and Ethernet to same bridge group at the Client and add the wireless to a bridge group at the AP. The AP does not require that you attach an Ethernet to the group, but it also works if you do.


Thanks for the fast reply.

[nuclearcat]

In the 3 weeks since your question we have added full transparent Client mode bridging. It requires our V3 AP and it works very well.

Perfect! Thats what i need.


The AP will require that you have a route for the customer Ethernet subnet.

What if customer subnet is complicated list of 10-100 IP's based on RIP... sure, i can enable RIP (eat some memory, CPU resources), but i think more optimal to run source routing or bridging. On my opinion bridging is better, if it stable...