Hacking on the rtl8366S

[Dave Taht]

On Fri, Jun 3, 2011 at 6:42 AM, Juliusz Chroboczek <jch at pps.jussieu.fr>wrote:

> > (the switch is bridged to the wireless interfaces, normally)
>
> Are you sure about that?


Pretty sure. The mac addr obtained for the bridge appears to be derived from
the wireless chip. When I tried to break apart the wired and wireless
devices completely in my testing last week, I was unable to get the wired
interface to work at all without disabling the wireless, due to the lack of
a distinct mac for it (or so I thought)



> The usual configuration is to use a hardware
> switch between the wired ports, but bridge the wired and wireless ports
> in software.  Can you post the output of brctl show?
>
>
>
This is from last nights cerowrt build...

root at cero1:~# brctl show
bridge name    bridge id        STP enabled    interfaces
br-lan        8000.c43dc7a37679    no        eth0.1
                            wlan0
                            wlan3

And the mac addr for eth0 is the same as wlan0

root at cero1:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr C4:3D:C7:A3:76:79
          inet6 addr: fe80::c63d:c7ff:fea3:7679/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3420 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:16
          RX bytes:0 (0.0 B)  TX bytes:460327 (449.5 KiB)
          Interrupt:4

root at cero1:~# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr C4:3D:C7:A3:76:7A
          inet addr:192.168.1.110  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::c63d:c7ff:fea3:767a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:118658 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62344 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:5
          RX bytes:153610689 (146.4 MiB)  TX bytes:5861647 (5.5 MiB)
          Interrupt:5

root at cero1:~# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr C4:3D:C7:A3:76:79
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3413 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:4
          RX bytes:0 (0.0 B)  TX bytes:506686 (494.8 KiB)



> At any rate, you should be able to program the switch to put each port
> on a different vlan -- that's how the separation between LAN and WAN
> ports is usually implemented.
>

Although an interesting idea, I wasn't planning to route, at this point,
each individual wired port - just break apart the wired and wireless
interfaces enough to look at and optimize their behavior better.

The external interface (to the internet) runs through the switch (on a
dedicated port) and has it's own phy, so far as I can tell.

The internal (to-the-switch) interface is just borrowing the wireless mac,
so far as I can tell, at present. That's basically all the wifi setup script
does.

There's a wiring diagram that more or less explains these oddities on pages
16 and 17 of:

rtl8366_8369_datasheet_1-1.pdf

which appears to be the most comprehensive document on this chipset series.
There is a mildly better diagram on the 1.4 data sheet specific to the
8366S.

-- Juliusz
>
>
>


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat-devel/attachments/20110603/2f53f969/attachment-0002.html>