etherswitchcfg reports no vlan capabilities on rtl8366rb

Luiz Otavio O Souza loos.br at gmail.com
Tue May 6 04:23:16 UTC 2014


On Sun, May 4, 2014 at 9:36 PM, Adrian Chadd <adrian at freebsd.org> wrote:
> Hi,
>
> Hm, it sounds like the support for vlan configuration from Luiz broke things.
>
> Luiz, do you have some time to help Harm figure out why your vlan
> config stuff broke the rtl8366 switch support?
>

Sure, i'll try to fix it before BSDCan, but the clock is ticking fast
this week :/

Luiz

>
>
> On 4 May 2014 14:44, Harm Weites <harm at weites.com> wrote:
>> Hi,
>>
>> My 1043ND is running HEAD @ r265004M and it's a bit unhappy when
>> configuring vlans on the RTL8366RB. Only after reverting revisions
>> 253569 253568 and 250382 things went back to running normal.
>>
>> This is from before reverting:
>>
>> # etherswitchcfg -v info
>> etherswitch0: Realtek RTL8366RB with 6 ports and 16 VLAN groups
>> etherswitch0: VLAN capabilities=0<>
>> port0:
>>         flags=0<>
>>         media: Ethernet autoselect (none)
>>         status: no carrier
>> port1:
>>         flags=0<>
>>         media: Ethernet autoselect (1000baseT <full-duplex>)
>>         status: active
>> port2:
>>         flags=0<>
>>         media: Ethernet autoselect (none)
>>         status: no carrier
>> port3:
>>         flags=0<>
>>         media: Ethernet autoselect (none)
>>         status: no carrier
>> port4:
>>         flags=0<>
>>         media: Ethernet autoselect (none)
>>         status: no carrier
>> port5:
>>         flags=0<>
>>         media: Ethernet 1000baseT <half-duplex,rxpause,txpause>
>>         status: active
>> vlangroup0:
>>         vlan: 4094
>>         members 5t
>> vlangroup1:
>>         vlan: 1
>>         members 0,5t
>> vlangroup2:
>>         vlan: 2
>>         members 1,2,3,4,5t
>> vlangroup3:
>>         vlan: 4
>>         members none
>> [..]
>>
>> # etherswitchcfg config vlan_mode
>> vlan_mode needs an argument
>>
>> This is annoying as well, though setting it to port produces no output
>> and apparently doesn't work out anyway.
>>
>> # etherswitchcfg port1 pvid
>> pvid needs an argument
>> port1:
>>         flags=0<>
>>         media: Ethernet autoselect (1000baseT <full-duplex>)
>>         status: active
>> # etherswitchcfg port1 pvid 2
>> etherswitchcfg: ioctl(IOETHERSWITCHSETPORT): Device not configured
>>
>> I decided to just leave out those revisions to make it usable again,
>> since those were the most notable changes in the etherswitch area.
>>
>> Regards,
>> Harm


More information about the freebsd-embedded mailing list