Hi Peter, Thanks for this. Is "ip l s dev eth1 up" the equivalent of ifconfig eth1 up? I'll let you know how this works in the next few days. Thanks, -Joel On 8/2/06, Peter Stuge <stuge-vlan@xxxxxxx> wrote: > > On Wed, Aug 02, 2006 at 12:01:03PM +1000, Joel Pearson wrote: > > So on the wireless router can I do this? > > vconfig wl0.2 18 > > Yes, but it's not what you want. It would create VLAN18 in the air, > and the VLAN interface wl0.2.18. > > On Linksys: > vconfig add eth0 17 > vconfig add eth0 18 > brctl addbr br1 > brctl addif br1 wl0.1 > brctl addif br1 eth0.17 > brctl addbr br2 > brctl addif br2 wl0.2 > brctl addif br2 eth0.18 > for if in eth0 eth0.17 eth0.18 wl0.1 wl0.2 br1 br2; do > ip l s dev $if up > done > > > and on the other router (eth1 is connected to the wireless router) > > vconfig eth1 18 > > > > And then create iptables rules on the other router by using > > eth1.18interface? > > On other router: > vconfig add eth1 17 > vconfig add eth1 18 > ip l s dev eth1 up > ip l s dev eth1.17 up > ip l s dev eth1.18 up > > Then wl0.1 traffic is on eth1.17, and wl0.2 on eth1.18. > > Also see the thread at > http://marc.theaimsgroup.com/?m=105098558615614 > > > //Peter > _______________________________________________ > Vlan mailing list > Vlan@xxxxxxxxxxxxxxx > http://www.candelatech.com/mailman/listinfo/vlan > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://ns2.lanforge.com/pipermail/vlan/attachments/20060803/7d7e3121/attachment.html
