From: Maciej Soltysiak <maciej@soltysiak.com>
To: David Lang <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Switch Issue
Date: Thu, 21 Feb 2013 14:53:07 +0100 [thread overview]
Message-ID: <CAMZR1YBeuZv0n_pn-ZtUHvxKsAzEv66B-1i6PNykT2LGAYeaSg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1302201126210.21566@nftneq.ynat.uz>
[-- 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 --]
next prev parent reply other threads:[~2013-02-21 13:53 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
2013-02-21 13:53 ` Maciej Soltysiak [this message]
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=CAMZR1YBeuZv0n_pn-ZtUHvxKsAzEv66B-1i6PNykT2LGAYeaSg@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/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