From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) (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 CF4E9208ABD for ; Thu, 21 Feb 2013 11:43:40 -0800 (PST) Received: by mail-vc0-f176.google.com with SMTP id fk10so6016623vcb.35 for ; Thu, 21 Feb 2013 11:43:39 -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=io7IRVx7gydBICwG3QFe6KXcp26degPmpbAjBRyTzMc=; b=iVDxYpYsD0Y/3jJJOuv/a85TkllLTLEUfrJzMc53N3yJx8crDeqgJM5zv1g25vFnVa DyVHB+mqHMN2lehHW+dTdExwNw3fo0R+Ssfd+WOI7Vu80nF8D0v3x7yQ78kQgn3C1jQM C9ZmamA3VhfmN5AV4+XCYRtXd5v/MHvbBD42aP2mOoTXVVc1+JaR6jM+0GA4g1JTrD5q OPmbTWF7IH7bVZ5J8IR8c+YowyJ6iHy23LK3qpO7R04xlja7/pOJmFxcraS7JPlS6n2v YLEkgAp/6ucwYmQfo6pcMNR7g4KUsKm4riSXpHAn9QAWMCtyeGVzzHmLZGbTVZzgcYCb BZRg== X-Received: by 10.220.214.6 with SMTP id gy6mr32308374vcb.8.1361475819331; Thu, 21 Feb 2013 11:43:39 -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 d13sm115810367vdj.8.2013.02.21.11.43.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Feb 2013 11:43:38 -0800 (PST) Message-ID: <512678E9.1050002@gmail.com> Date: Thu, 21 Feb 2013 14:43:37 -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="------------050205020208060509050907" 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 19:43:41 -0000 This is a multi-part message in MIME format. --------------050205020208060509050907 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hey guys, Thanks for the help troubleshooting. So it turns out that one of the machines on the restricted VLAN (this is a small charity/nonprofit, this VLAN is for their clients to browse the web) got infected with something and was generating a mind-blowing amount of broadcast traffic. Since the cero router is the device that routes between the VLANs, the switch was getting hit with all of this traffic and locking up. The fact that I had all three VLANs trunked over one port made it so that I couldn't see anything to figure out how to fix it...once I got someone on site to start poking at cables, I was able to split each VLAN to a different wire, then was able to get to the Dell managed switch interface and figure out who was the culprit. Thanks again! -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 > > --------------050205020208060509050907 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hey guys,

Thanks for the help troubleshooting.

So it turns out that one of the machines on the restricted VLAN (this is a small charity/nonprofit, this VLAN is for their clients to browse the web) got infected with something and was generating a mind-blowing amount of broadcast traffic. Since the cero router is the device that routes between the VLANs, the switch was getting hit with all of this traffic and locking up.

The fact that I had all three VLANs trunked over one port made it so that I couldn't see anything to figure out how to fix it...once I got someone on site to start poking at cables, I was able to split each VLAN to a different wire, then was able to get to the Dell managed switch interface and figure out who was the culprit.

Thanks again!
-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



--------------050205020208060509050907--