Dual WAN on Dlink DIR-825 B2

Installing and Using OpenWrt Network and Wireless Configuration
16

This page

recommend me factory install the:
https://downloads.openwrt.org/releases/19.07.2/targets/ar71xx/generic/openwrt-19.07.2-ar71xx-generic-dir-825-b1-squashfs-factory.bin
but in this, i found newest version:
https://downloads.openwrt.org/releases/22.03.3/targets/ath79/generic/openwrt-22.03.3-ath79-generic-dlink_dir-825-b1-squashfs-factory.bin

What to do?

17

@tmomas maybe the wiki links were not properly updated from that version.

1 Like
19

There was no factory image available after 19.07.2, but now it is again. Dataentry updated accordingly.

2 Likes
20

Why are you pretending that I'm not here?

21

Dir 825 b2 has Atheros AR7161 chipset
Old link (with "ar71xx") - good, but new link - with "ath79" ???
Is that normal?

22

From https://openwrt.org/docs/techref/targets/ath79

ath79 is the successor of ar71xx. It's modernization under the hood, with the main goal to bring the code into a form that is acceptable for Linux upstream, so that all (most) of the whole ar71xx supported devices can be handled by an upstream, unpatched Linux kernel.1)

So yes, that's normal.

1 Like
23

uci or ...?

24

Now i have:
OpenWrt 19.07.2 r10947-65030d81f3 / LuCI openwrt-19.07 branch git-20.057.55219-13dd17f
from
https://downloads.openwrt.org/releases/19.07.2/targets/ar71xx/generic/openwrt-19.07.2-ar71xx-generic-dir-825-b1-squashfs-factory.bin

But after downloading:
https://downloads.openwrt.org/releases/22.03.3/targets/ath79/generic/openwrt-22.03.3-ath79-generic-dlink_dir-825-b1-squashfs-sysupgrade.bin

I try sysupdate via luci, but:
image

25

Did you verify the SHA256 hash? Does it match with the one mentioned in the site? If yes, then proceed.

Next steps
  1. Take a backup of the current device.
  2. Untick the "Keep settings and retain current configuration"
  3. Tick the "Force upgrade" and "Continue"
    Upgrade Zyxel NBG6616 from 19.07.10 to 22.03.2 (ar71xx to ath79) - #2 by psherman
26

Ok, i reinstalled from factory with 60/60/60 method.

New problem:
In this instruction:

the man have screen with wan:

image
image1014×746 51.8 KB

but i don't have "wan" on my screen:

image
image1005×606 23.1 KB

Is it error or should be?

P.S.
My firmware:
OpenWrt 22.03.3 r20028-43d71ad93e / LuCI openwrt-22.03 branch git-22.361.69894-438c598
but on:
OpenWrt 19.07.2 r10947-65030d81f3 / LuCI openwrt-19.07 branch git-20.057.55219-13dd17f
the same situation.

27

No it is not a problem.

28

But i why i not have this option? How setup dual wan without it?

29

Your wan port is not connected to the switch.

You'll assign on of the available lan ports as wan2.

30

Thanks very much

Is it the features of hardware? Or firmware? Or am I doing something wrong?

31

Hardware spec.
Create 2 more vlans, say 5 and 10. Both tagged on CPU.
Remove lan1 from vlan1 (toggle to off) then in vlan 5 toggle it untagged,
Same for lan2 and vlan10.
Use the new vlan subinterfaces as wan1 and wan2.

32

Here my setup:

изображение
изображение984×383 48.3 KB

изображение
изображение978×309 25.5 KB

I managed to get two interfaces to work:
eth1 (DHCP) - main wan
eth0.2 (DHCP) - second wan on 4th physical port
Both providers respond through ping.
I set gateway metrics:
10-eth1
30-eth0.2
Next question:
Is it necessary to install MWAN3 or can I get by with a script that switches metrics when eth1 is up/down?

33

It depends how fast can you plan, implement, test, and finalize your scripts.

34

Sorry but the answer is a bit vague, I can't understand you.
If it is possible to get by with a script, tell me how to write it and where to put it. Sorry for persistence.
I don’t need a complex scheme

35

If you don't know how to write it, better use mwan3. Personally I don't feel like reinventing the wheel.

36

In any case, thanks for a useful experience. :+1:

1 Like