* [Cerowrt-devel] Switch Issue
@ 2013-02-20 16:01 William Katsak
2013-02-20 16:09 ` dpreed
` (2 more replies)
0 siblings, 3 replies; 10+ messages in thread
From: William Katsak @ 2013-02-20 16:01 UTC (permalink / raw)
To: cerowrt-devel
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
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [Cerowrt-devel] Switch Issue 2013-02-20 16:01 [Cerowrt-devel] Switch Issue William Katsak @ 2013-02-20 16:09 ` dpreed 2013-02-20 16:12 ` Dave Taht 2013-02-20 19:17 ` Maciej Soltysiak 2 siblings, 0 replies; 10+ messages in thread From: dpreed @ 2013-02-20 16:09 UTC (permalink / raw) To: William Katsak; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 1477 bytes --] Not the 3800's switch, but lots of other ones. Often caused by a human cabling error. E.g. a cable connecting one port on a switch to another, which "amplifies" broadcast/multicast traffic into a storm that is also broadcast to other switches, locking up the switch and others. Just before the switch failed were any events logged related to port up/down? Not that it needs to be the 3800 switch that is the cause. -----Original Message----- From: "William Katsak" <wkatsak@gmail.com> Sent: Wednesday, February 20, 2013 11:01am To: "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net> Subject: [Cerowrt-devel] Switch Issue 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/html, Size: 1899 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-20 16:01 [Cerowrt-devel] Switch Issue 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 2 siblings, 2 replies; 10+ messages in thread From: Dave Taht @ 2013-02-20 16:12 UTC (permalink / raw) To: William Katsak; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 1651 bytes --] I only recently tried to get vlans to work. I ran into major issues trying to get babel to work across them, am not sure if I was running into bugs in quagga or not and gave up (the symptom was that it didn't like having the same fe80 address on the same LAN despite being vlan'd. ) This obviously isn't your problem. I have not tried of late to jam jumbo packets through it, I have generally been concerned that bad things would happen if anyone tried. Aside from that, no clue. There are various means of monitoring the switch behavior including snmp stuff buried inside the switch (?) command. On Wed, Feb 20, 2013 at 11:01 AM, 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 > -- Dave Täht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html [-- Attachment #2: Type: text/html, Size: 2195 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-20 16:12 ` Dave Taht @ 2013-02-20 16:28 ` William Katsak 2013-02-20 19:15 ` William Katsak 1 sibling, 0 replies; 10+ messages in thread From: William Katsak @ 2013-02-20 16:28 UTC (permalink / raw) To: Dave Taht; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 2157 bytes --] Dave, Do you know what these registers should read? [ 40.871093] ar71xx: pll_reg 0xb8050010: 0x11110000 [ 40.871093] se00: link up (1000Mbps/Full duplex) [ 43.886718] ar71xx: pll_reg 0xb8050014: 0x1099 [ 43.886718] ge00: link up (100Mbps/Full duplex) On my other cero router, these are both the same (0x11110000), but I'm not using VLANs there, so I don't know if this has anything to do with it. -Bill On Feb 20, 2013, at 11:12 AM, Dave Taht <dave.taht@gmail.com> wrote: > I only recently tried to get vlans to work. I ran into major issues trying to get babel to work across them, am not sure if I was running into bugs in quagga or not and gave up (the symptom was that it didn't like having the same fe80 address on the same LAN despite being vlan'd. ) > > This obviously isn't your problem. I have not tried of late to jam jumbo packets through it, I have generally been concerned that bad things would happen if anyone tried. Aside from that, no clue. There are various means of monitoring the switch behavior including snmp stuff buried inside the switch (?) command. > > On Wed, Feb 20, 2013 at 11:01 AM, 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 > > > > -- > Dave Täht > > Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html [-- Attachment #2: Type: text/html, Size: 3212 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-20 16:12 ` Dave Taht 2013-02-20 16:28 ` William Katsak @ 2013-02-20 19:15 ` William Katsak 1 sibling, 0 replies; 10+ messages in thread From: William Katsak @ 2013-02-20 19:15 UTC (permalink / raw) To: Dave Taht; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 1811 bytes --] Can you tell me more about this switch command. I don't see it anywhere… -Bill On Feb 20, 2013, at 11:12 AM, Dave Taht <dave.taht@gmail.com> wrote: > I only recently tried to get vlans to work. I ran into major issues trying to get babel to work across them, am not sure if I was running into bugs in quagga or not and gave up (the symptom was that it didn't like having the same fe80 address on the same LAN despite being vlan'd. ) > > This obviously isn't your problem. I have not tried of late to jam jumbo packets through it, I have generally been concerned that bad things would happen if anyone tried. Aside from that, no clue. There are various means of monitoring the switch behavior including snmp stuff buried inside the switch (?) command. > > On Wed, Feb 20, 2013 at 11:01 AM, 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 > > > > -- > Dave Täht > > Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html [-- Attachment #2: Type: text/html, Size: 2731 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-20 16:01 [Cerowrt-devel] Switch Issue William Katsak 2013-02-20 16:09 ` dpreed 2013-02-20 16:12 ` Dave Taht @ 2013-02-20 19:17 ` Maciej Soltysiak 2013-02-20 19:29 ` David Lang 2 siblings, 1 reply; 10+ messages in thread From: Maciej Soltysiak @ 2013-02-20 19:17 UTC (permalink / raw) To: William Katsak; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 3099 bytes --] 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/html, Size: 4447 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-20 19:17 ` Maciej Soltysiak @ 2013-02-20 19:29 ` David Lang 2013-02-21 13:53 ` Maciej Soltysiak 0 siblings, 1 reply; 10+ messages in thread From: David Lang @ 2013-02-20 19:29 UTC (permalink / raw) To: Maciej Soltysiak; +Cc: cerowrt-devel [-- 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-20 19:29 ` David Lang @ 2013-02-21 13:53 ` Maciej Soltysiak 2013-02-21 14:30 ` William Katsak 2013-02-21 19:43 ` William Katsak 0 siblings, 2 replies; 10+ messages in thread From: Maciej Soltysiak @ 2013-02-21 13:53 UTC (permalink / raw) To: David Lang; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 4461 bytes --] 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> >> " >> <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<Cerowrt-devel@lists.bufferbloat.net> >>> https://lists.bufferbloat.net/**listinfo/cerowrt-devel<https://lists.bufferbloat.net/listinfo/cerowrt-devel> >>> >>> > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > [-- Attachment #2: Type: text/html, Size: 5925 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-21 13:53 ` Maciej Soltysiak @ 2013-02-21 14:30 ` William Katsak 2013-02-21 19:43 ` William Katsak 1 sibling, 0 replies; 10+ messages in thread From: William Katsak @ 2013-02-21 14:30 UTC (permalink / raw) To: Maciej Soltysiak; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 6004 bytes --] 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 > <mailto: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 > <mailto:maciej@soltysiak.com>> > To: William Katsak <wkatsak@gmail.com <mailto:wkatsak@gmail.com>> > Cc: "cerowrt-devel@lists.bufferbloat.net > <mailto:cerowrt-devel@lists.bufferbloat.net>" > <cerowrt-devel@lists.bufferbloat.net > <mailto: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 <mailto: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 > <mailto:Cerowrt-devel@lists.bufferbloat.net> > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > <mailto:Cerowrt-devel@lists.bufferbloat.net> > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > [-- Attachment #2: Type: text/html, Size: 9873 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Cerowrt-devel] Switch Issue 2013-02-21 13:53 ` Maciej Soltysiak 2013-02-21 14:30 ` William Katsak @ 2013-02-21 19:43 ` William Katsak 1 sibling, 0 replies; 10+ messages in thread From: William Katsak @ 2013-02-21 19:43 UTC (permalink / raw) To: Maciej Soltysiak; +Cc: cerowrt-devel [-- Attachment #1: Type: text/plain, Size: 6224 bytes --] 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 > <mailto: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 > <mailto:maciej@soltysiak.com>> > To: William Katsak <wkatsak@gmail.com <mailto:wkatsak@gmail.com>> > Cc: "cerowrt-devel@lists.bufferbloat.net > <mailto:cerowrt-devel@lists.bufferbloat.net>" > <cerowrt-devel@lists.bufferbloat.net > <mailto: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 <mailto: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 > <mailto:Cerowrt-devel@lists.bufferbloat.net> > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > <mailto:Cerowrt-devel@lists.bufferbloat.net> > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > [-- Attachment #2: Type: text/html, Size: 10036 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-02-21 19:43 UTC | newest] Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2013-02-20 16:01 [Cerowrt-devel] Switch Issue 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 2013-02-21 13:53 ` Maciej Soltysiak 2013-02-21 14:30 ` William Katsak 2013-02-21 19:43 ` William Katsak
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox