2 Gbps WAN/LAN NAT Routing on ramips MT7621 devices

I would appreciate it! Thank you!

The image for Netgear WAX202 is up.
@keshav @fubag

3 Likes

thank you!

Has a pull request been created to include this modification in the next version?

Not yet, it's only there for snapshot for now.

The pull request is applied to the master branch!

6 Likes

Excellent. I'm excited to see this in a release.

Thank you so much for your work.

1 Like

Any plans/real chance for backport to 22.03?

Usually new features are not backported but since this is a devicetree only change, it may find its way to the current releases. It's all up to @hauke.

If it fixes some issue... Do we have an opened issue for this topic?

I always thought that it was 1000/1000. So now I'm wondering, how about other mediatek or qualcomm SoCs? Are they 1000/1000 or 500/500?

Hello arinc9,
If I understand correctly, all qualified MT7621 snapshots as of August 21, 2022 will contain your patch now?

That sounds correct, yes!

4 Likes

Thank-you.

Hello @arinc9,
I'm trying your patch for device Keenetic Giga 3 (wikidevi). But so far I don't have a very powerful CPU on which the ipefr3 -c localhost --bidir utility would show at least 2 Gbps.

After applying this patch, I noticed that the protocol type of the ports has changed from MII to Twisted Pair:

root@ZKG:/# ethtool lan1
Settings for lan1:
        Supported ports: [ TP MII ]
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 3
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

root@ZKG:/# ethtool wan
Settings for wan:
        Supported ports: [ TP MII ]
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 4
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: yes

Is this normal? And what does it say?

Why do you do this? Does the wan port not work after the changes? Also, why do you connect to localhost for speed test?

WAN port is work.

So I just tested the capabilities of my computer: ipefr3 -c localhost --bidir -t 15

Ok, I’ve never checked the output of ethtool so I don’t know what to tell you. If wan port works, I don’t see a problem.

when I use these devices as access points
I map the wan port back to the br-lan
so in this mode is the cpu now needed
to move traffic between wan and lan ports
or will it reattach it back to the switch ?

Yes, frames will go through the CPU for wan port.

1 Like