27 Sep, 2020
2 commits
-
Remove the .flow_dissect procedure, so the flow dissector will call the
generic variant which works for this tagging protocol.Cc: Linus Walleij
Cc: DENG Qingfang
Cc: Mauri Sandberg
Signed-off-by: Vladimir Oltean
Signed-off-by: David S. Miller -
There is no tagger that returns anything other than zero, so just change
the return type appropriately.Signed-off-by: Vladimir Oltean
Reviewed-by: Andrew Lunn
Signed-off-by: David S. Miller
09 Jul, 2020
1 commit
-
This implements the known parts of the Realtek 4 byte
tag protocol version 0xA, as found in the RTL8366RB
DSA switch.It is designated as protocol version 0xA as a
different Realtek 4 byte tag format with protocol
version 0x9 is known to exist in the Realtek RTL8306
chips.The tag and switch chip lacks public documentation, so
the tag format has been reverse-engineered from
packet dumps. As only ingress traffic has been available
for analysis an egress tag has not been possible to
develop (even using educated guesses about bit fields)
so this is as far as it gets. It is not known if the
switch even supports egress tagging.Excessive attempts to figure out the egress tag format
was made. When nothing else worked, I just tried all bit
combinations with 0xannp where a is protocol and p is
port. I looped through all values several times trying
to get a response from ping, without any positive
result.Using just these ingress tags however, the switch
functionality is vastly improved and the packets find
their way into the destination port without any
tricky VLAN configuration. On the D-Link DIR-685 the
LAN ports now come up and respond to ping without
any command line configuration so this is a real
improvement for users.Egress packets need to be restricted to the proper
target ports using VLAN, which the RTL8366RB DSA
switch driver already sets up.Cc: DENG Qingfang
Cc: Mauri Sandberg
Reviewed-by: Andrew Lunn
Reviewed-by: Florian Fainelli
Signed-off-by: Linus Walleij
Signed-off-by: David S. Miller
