>
> Call me goofy, but just plugging in some wires and watching seems less
> prone to error.
>
What something does or doesn't do is different than trying to understand
why it does or doesn't do.
Of course you test, but I like to test a hypothesis based on my knowledge
and/or data.
I find it not
According to https://openwrt.org/toh/gl.inet/gl-ar750s
The switch chip on his router looks like this:
port 0: CPU
port 1: WAN
port 2: LAN1
port 3: LAN2
The usual way OpenWrt VLANs these would be:
VLAN 1: 0t 2 3
VLAN 2: 0t 1
And eth0.2 would be the WAN interface, and eth0.1 would be part of
Thanks for the ideas Russell - this is definitely fun - I will try that
when I am back from a sub-trip (trip in a trip) on 2nd January.
On Fri, Dec 27, 2019, 01:13 Russell Senior
wrote:
> For reference, this is what the full-blown output of "swconfig dev switch0
> show" from the MT7621 looks
For reference, this is what the full-blown output of "swconfig dev switch0
show" from the MT7621 looks like:
http://sprunge.us/YPQwYE
On Thu, Dec 26, 2019 at 4:07 PM Russell Senior
wrote:
>
>
> On Thu, Dec 26, 2019 at 3:54 PM Russell Senior
> wrote:
>
>> Ooh, try this: shell in and run:
On Thu, Dec 26, 2019 at 3:54 PM Russell Senior
wrote:
> Ooh, try this: shell in and run: swconfig dev switch0 show | grep port
>
> Connect your loop and run it again.
>
> Then, seeing which port link state changed, you'll know what switch ports
> are LAN1 and LAN2. Piping to less instead of grep
Ooh, try this: shell in and run: swconfig dev switch0 show | grep port
Connect your loop and run it again.
Then, seeing which port link state changed, you'll know what switch ports
are LAN1 and LAN2. Piping to less instead of grep should give you a bunch
of port stats.
Ping an address in the
Qualcomm QCA9563 SOC in GL-AR750S package.
On Fri, Dec 27, 2019, 00:12 Mike C. wrote:
> I have a theory about why it didn't work on your device. Its what I
> expected would happen and why I didn't suggest what Russell did to just
> loop one LAN port to another. I think its due to the
I have a theory about why it didn't work on your device. Its what I
expected would happen and why I didn't suggest what Russell did to just
loop one LAN port to another. I think its due to the architecture.
What make and model is your switch/router?
On Thu, Dec 26, 2019, 2:24 PM wrote:
> It
Yes. That one.
On Wed, Dec 25, 2019, 9:50 PM Russell Senior
wrote:
> > The embedded image of the Asus WL 500G wireless router that I tried to
> >> share but was rejected shows the 4 LAN ports hardwired together as a
> >> multi-port bridge all in VLAN 0.
> >>
> >
> This one?
>
>
It seems that in my case - looping LAN1 with LAN2 and sending/receiving
WAN<-->WLAN3 traffic leads to no visible traffic degradation. That probably mean
that I failed to create lan loop.
The lights were "kind of" busy on LAN1 <--> LAN2, but the wlan3 and upstream WAN
are slow enough to observe
> The embedded image of the Asus WL 500G wireless router that I tried to
>> share but was rejected shows the 4 LAN ports hardwired together as a
>> multi-port bridge all in VLAN 0.
>>
>
This one?
https://openwrt.org/_media/oldwiki/openwrtdocs/asus-internals-default.png
On Wed, Dec 25, 2019 at 9:10 PM Mike C. wrote:
> >
> > This behavior is going to depend on the switch chip embedded in the SoC
> > onTomas's device. The Linux kernel or its bridging behavior won't be
> > involved
> > until the traffic leaves the switch.
> >
>
> Ah, now I know why I didn't
>
> This behavior is going to depend on the switch chip embedded in the SoC
> onTomas's device. The Linux kernel or its bridging behavior won't be
> involved
> until the traffic leaves the switch.
>
Ah, now I know why I didn't understand this nor agree with it.
The embedded image of the Asus WL
>
> This behavior is going to depend on the switch chip embedded in the SoC
> onTomas's device. The Linux kernel or its bridging behavior won't be
> involved
> until the traffic leaves the switch.
>
I'm not sure I totally understand nor agree with what yo're saying here but
that's for another
> Even more interesting is that you might be able to even get a diagram of
> the switch/router backplane that will show you how the ports are physically
> & logically connected. Such as this diagram I found in the OpenWrt
> documentation. (See attached screenshot "Diagram")
>
A fun command in
I tried it on three routers in my testbed (all running OpenWrt, though I
don't think that's relevant here):
1) Buffalo WZR600DHP (switch0: Atheros AR8316 rev. 1 switch registered on
mdio-bus.0)
2) Ubiquiti AirRouter (switch0: Atheros AR724X/AR933X built-in rev. 2
switch registered on mdio-bus.0)
This behavior is going to depend on the switch chip embedded in the SoC on
Tomas's device. The Linux kernel or its bridging behavior won't be involved
until the traffic leaves the switch. In openwrt, there is a standard
interface for configuring the switch, called swconfig, although the future
Date: Wed, 25 Dec 2019 12:25:35 -0800
Subject: Re: [PLUG] Lan loops - follow on PoE injector
On Wed, Dec 25, 2019 at 9:33 AM Russell Senior
wrote:
> Only one way to be sure! ;-)
>
>
Said the person on top of the building when contemplating if the fall would
kill him, while another person used
Only one way to be sure! ;-)
On Wed, Dec 25, 2019 at 9:19 AM Mike C. wrote:
> >
> > I happened to have a netgear FS105 nearby. Plugging in a laptop to a
> switch
> > port, and plugging a patch cable between two other switch ports and
> pinging
> > a random ip address from the laptop set off the
>
> I happened to have a netgear FS105 nearby. Plugging in a laptop to a switch
> port, and plugging a patch cable between two other switch ports and pinging
> a random ip address from the laptop set off the broadcast storm. Running
> tcpdump from the laptop showed a bunch of "MPCP, Opcode Pause,
20 matches
Mail list logo
