From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ve0-f175.google.com (mail-ve0-f175.google.com [209.85.128.175]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 5EC3221F0F2 for ; Thu, 21 Feb 2013 06:30:46 -0800 (PST) Received: by mail-ve0-f175.google.com with SMTP id cy12so7897848veb.6 for ; Thu, 21 Feb 2013 06:30:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=diuo70y+s/rClRldV4Frcal8vRjpc0wYqF48brshfHw=; b=uMdj5IHEHjjWIun9l6WIhCxX3qp3zOohzGzpA+FAS6aMHg9pigTCtnybOwdnFP2qKc u9rY4UIykgNxx7A6I4jDBExOpxCXnZ6oLymPGClBpTN2G7i9m9yNSuSAi6q8yElcyyUG SfUiJvmRNtfUAqLxbB7iTatwoB1uKsOGbZ9yc+iwLq+odeS5NiO5LmrEZdEw3587ewBf 8DC+zDS1O8mlTCif7hb24FF+q51K6ZZbPNuHDBEZJ4PP8pUnn+dmyceBiBnTrWSdIu4C lGf34iBhkN8W3LwPaZjWb8dmSqVpsluOlZuIcJxCDtydS/Auf3p1bHaZs66t0EUURm44 oeJA== X-Received: by 10.58.161.41 with SMTP id xp9mr31795799veb.56.1361457043312; Thu, 21 Feb 2013 06:30:43 -0800 (PST) Received: from ?IPv6:2001:4830:1600:423::2? (cl-1060.qas-01.us.sixxs.net. [2001:4830:1600:423::2]) by mx.google.com with ESMTPS id tp10sm28048610vec.1.2013.02.21.06.30.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Feb 2013 06:30:42 -0800 (PST) Message-ID: <51262F91.8020208@gmail.com> Date: Thu, 21 Feb 2013 09:30:41 -0500 From: William Katsak User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130214 Thunderbird/17.0.2 MIME-Version: 1.0 To: Maciej Soltysiak References: <8948C7F6-3F35-46D5-9367-02B79553E409@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------010005000306030802040200" Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Switch Issue X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 14:30:46 -0000 This is a multi-part message in MIME format. --------------010005000306030802040200 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Maciej, Strangely, your config restores access to my default VLAN (1), which is where I can configure the big Dell switch that I am connected to (but the trunk port on the Dell has vlan 1 as the PVID in case we ever need to access it quickly in an emergency). I am trying to incrementally add the other stuff back, but it seems to crap out again as soon as I turn VLANs back on. I also get this from swconfig: EtherStatsDropEvents : 4245175 Dot3StatsFCSErrors : 4245117 which is almost all of the packets sent. -Bill On 02/21/2013 08:53 AM, Maciej Soltysiak wrote: > Hi David, > Yup, I know, I'm not using vlans now. What I meant is that when I > tinkered with it, I screwed wired connections. > Hence I offered a working-ethernet config to William. > William, did you have any luck fixing your issue? > Regards, > Maciej Soltysiak > > On Wed, Feb 20, 2013 at 8:29 PM, David Lang > wrote: > > 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 > > To: William Katsak > > Cc: "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 > > 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 > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > --------------010005000306030802040200 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Maciej,

Strangely, your config restores access to my default VLAN (1), which is where I can configure the big Dell switch that I am connected to (but the trunk port on the Dell has vlan 1 as the PVID in case we ever need to access it quickly in an emergency).

I am trying to incrementally add the other stuff back, but it seems to crap out again as soon as I turn VLANs back on.

I also get this from swconfig:

EtherStatsDropEvents                : 4245175
Dot3StatsFCSErrors                  : 4245117

which is almost all of the packets sent.

-Bill


On 02/21/2013 08:53 AM, Maciej Soltysiak wrote:
Hi David,
 
Yup, I know, I'm not using vlans now. What I meant is that when I tinkered with it, I screwed wired connections.
Hence I offered a working-ethernet config to William.
William, did you have any luck fixing your issue?
 
Regards,
Maciej Soltysiak

On Wed, Feb 20, 2013 at 8:29 PM, David Lang <david@lang.hm> wrote:
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


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



--------------010005000306030802040200--