Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Switch Issue
Date: Wed, 20 Feb 2013 11:29:36 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1302201126210.21566@nftneq.ynat.uz> (raw)
In-Reply-To: <CAMZR1YDVqAMOV4oJ-804W4LBndTrFsak+LcCQTWu16J0Q0QVtQ@mail.gmail.com>

[-- Attachment #1: Type: TEXT/Plain, Size: 3660 bytes --]

you have vlans disabled in this config "option enable_vlan 0"

if you want to use vlans > 15 you need "option enable_vlan4k 1" as well

David Lang

On Wed, 20 Feb 2013, Maciej Soltysiak wrote:

> Date: Wed, 20 Feb 2013 20:17:19 +0100
> From: Maciej Soltysiak <maciej@soltysiak.com>
> To: William Katsak <wkatsak@gmail.com>
> Cc: "cerowrt-devel@lists.bufferbloat.net"
>     <cerowrt-devel@lists.bufferbloat.net>
> Subject: Re: [Cerowrt-devel] Switch Issue
> 
> I recently played with VLANs and screwed up it's switching capability
> exactly as you say.
> I managed to fix it by restoring the default setup in /etc/config/network
> (Especially config switch_vlan and ports)
>
> Compare your /etc/config/network with what I have (and works):
> config switch
>        option name     rtl8366s
>        option reset    1
>        option enable_vlan 0
>        # Blinkrate: 0=43ms; 1=84ms; 2=120ms; 3=170ms; 4=340ms; 5=670ms
>        option blinkrate        2
>        option max_length 3
>
> config switch_vlan
>        option device   rtl8366s
>        option vlan     1
>        option ports    "0 1 2 3 5t"
>
> config switch_port
>        # Port 1 controls the GREEN configuration of LEDs for
>        # the switch and the section does not correspond to a real
>        # switch port.
>        #
>        # 0=LED off; 1=Collision/FDX; 2=Link/activity; 3=1000 Mb/s;
>        # 4=100 Mb/s; 5=10 Mb/s; 6=1000 Mb/s+activity; 7=100 Mb/s+activity;
>        # 8=10 Mb/s+activity; 9=10/100 Mb/s+activity; 10: Fiber;
>        # 11: Fault; 12: Link/activity(tx); 13: Link/activity(rx);
>        # 14: Link (master); 15: separate register
>
>        option device           rtl8366s
>        option port             1
>        option led              6
>
> config switch_port
>        # Port 2 controls the ORANGE configuration of LEDs for
>        # the switch and the section does not correspond to a real
>        # switch port.
>        #
>        # See the key above for switch port 1 for the meaning of the
>        # 'led' setting below.
>
>        option device           rtl8366s
>        option port             2
>        option led              9
>
> config switch_port
>        # Port 5 controls the configuration of the WAN LED and the
>        # section does not correspond to a real switch port.
>        #
>        # To toggle the use of green or orange LEDs for the WAN port,
>        # see the LED setting for wndr3700:green:wan in /etc/config/system.
>        #
>        # See the key above for switch port 1 for the meaning of the
>        # 'led' setting below.
>
>        option device           rtl8366s
>        option port             5
>        option led              2
>
> Best regards,
> Maciej Soltysiak
>
> On Wed, Feb 20, 2013 at 5:01 PM, William Katsak <wkatsak@gmail.com> wrote:
>
>> Hello,
>>
>> Just wanted to see if anyone has seen an issue like this:
>>
>> I have a 3800 running Sugarland at a remote site. It was running nice and
>> reliably, connected to the local network by a VLAN trunked connection (I
>> have interfaces for the default VLAN, and VLANS 100 and 200 passing
>> through). Last night it suddenly stopped working. There seems to be no data
>> flowing through the switch at all, even though I can ssh to the router,
>> reboot, poke at it, etc. from over the Internet.
>>
>> I see no error messages regarding the switch in the logs or dmesg. Anyone
>> else see a 3800 switch crap out unceremoniously?
>>
>> Thanks,
>> Bill Katsak
>>
>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>

[-- Attachment #2: Type: TEXT/PLAIN, Size: 164 bytes --]

_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

  reply	other threads:[~2013-02-20 19:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 16:01 William Katsak
2013-02-20 16:09 ` dpreed
2013-02-20 16:12 ` Dave Taht
2013-02-20 16:28   ` William Katsak
2013-02-20 19:15   ` William Katsak
2013-02-20 19:17 ` Maciej Soltysiak
2013-02-20 19:29   ` David Lang [this message]
2013-02-21 13:53     ` Maciej Soltysiak
2013-02-21 14:30       ` William Katsak
2013-02-21 19:43       ` William Katsak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1302201126210.21566@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox