IPSEC wireless router ?

>>some clue to help your mind:
>>what is br0 ? how to set it up ?
>>have you ever seen a hardware NIC that the driver makes available as br0 ?
>>if it's really a linux running around, why arnt there eth0 and eth1 in the routing
>>tables ???
>
>
> It's Linux:
> ~ # uname -a
> Linux router 2.4.20 #2 Thu Apr 21 19:40:17 CEST 2005 mips unknown
>
> br0 is the bridge port and can be linked to any of the other bridged
> ethernet ports on the switch. I'll guess (not sure) that the routeing
> table uses br0 instead of eth0 because br0 is the filtered port name
> while eth0 is the unfiltered port name.

thats wrong, and your next past confirms it ...

br0 is NOT a brige port

and you can NOT choose the port of the switch you link to.

you OBVIOuSLY dont know how this device is soldered.

And finally, your guess IS WRONG.

br0 IS NOT an alias nor a filter.

I told you to read about wds because tutos tell about this difference. Maybe you
readed words, but your brain did not understood them.

> Incidentally eth0 and eth1 are there.
>
> ~ # ifconfig
> br0 Link encap:Ethernet HWaddr 00:0C:41:9C:3D:10
> inet addr:192.168.111.33 Bcast:192.168.111.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:87104 errors:0 dropped:0 overruns:0 frame:0
> TX packets:111983 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:10605896 (10.1 MiB) TX bytes:47923183 (45.7 MiB)
>
> eth0 Link encap:Ethernet HWaddr 00:0C:41:9C:3D:10
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:268597 errors:0 dropped:0 overruns:0 frame:0
> TX packets:274490 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:70588908 (67.3 MiB) TX bytes:64626923 (61.6 MiB)
> Interrupt:3 Base address:0x2000
>
> eth1 Link encap:Ethernet HWaddr 00:0C:41:9C:3D:11
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 B) TX bytes:6331 (6.1 KiB)
> Interrupt:4 Base address:0x8000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
> RX packets:1170 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1170 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:96923 (94.6 KiB) TX bytes:96923 (94.6 KiB)
>
> vlan0 Link encap:Ethernet HWaddr 00:0C:41:9C:3D:10
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:87085 errors:0 dropped:0 overruns:0 frame:0
> TX packets:188737 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:11164196 (10.6 MiB) TX bytes:53280155 (50.8 MiB)
>
> vlan1 Link encap:Ethernet HWaddr 00:0C:41:9C:3D:11
> inet addr:63.198.98.51 Bcast:63.198.98.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:181414 errors:0 dropped:0 overruns:0 frame:0
> TX packets:85673 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:54582227 (52.0 MiB) TX bytes:11338413 (10.8 MiB)

without br0, eth0 and wlan0 are just ... independant !

there is NO hardware brige, and there is no default hard link.

briging eth to wlan IS SOFTWARE !!!

wlan0 is NOT an ethernet NIC with an antena, but a NIC dedicated to wireless.

> Clueless? Run a Google Groups search for posting with my name. Read
> a few. Then come back and call me clueless.

the fact you wrote 1000000messages in groups does not mean you know what you write
about.

> All 802.11 wireless cards are bridged. You can attach a router at
> both ends and hide the bridging from the client, but the basic
> protocol is bridging.

NO wireless card is briged. NONE.

Briging IS NOT A PROTOCOL, but asoftware setup.

> 802.11 wireless is bridging by definition.

did you ever set up MANUALLY a wireless card ?
what is wlan0 ?
how is br0 set up un the WRT ?

there is no such protocol as briging !
and 802.11 is only supported by dedicated cards.

> There's no other
> way to connect between wireless and wired devices other than bridging.

there IS, and I do it every morning:
iptables.

*********

the more I read your old posts, the more I see you speak cluelessly.

--
DEMAINE Benoit-Pierre (aka DoubleHP ) http://www.demaine.info/
\_o< If computing were an exact science, IT engineers would not have work >o_/