1 (edytowany przez m80 2017-02-15 11:52:07)

Temat: mwan3 i LEDE 17.01-SNAPSHOT

Cześć

Podstawowa konfiguracja mwan3 failover (e3372 + neostrada),
Czy mwan3 ma coś skopane? bo pokazuje że połączenie lte (wan2) mam offline i tracking down
a połączenie działa jak przełączę ręcznie.

PS. Cezary czy opcja "mode lte" przy protokole ncm w config/network ma dalej zastosowanie w LEDE?

BusyBox v1.25.1 () built-in shell (ash)

     _________
    /        /\      _    ___ ___  ___
   /  LE    /  \    | |  | __|   \| __|
  /    DE  /    \   | |__| _|| |) | _|
 /_       /  LE  \  |____|___|___/|___|                      lede-project.org
 \        \   DE /
  \    LE  \    /  -----------------------------------------------------------
   \  DE    \  /    Reboot (17.01-SNAPSHOT, r3106-c53bb97)
    \________\/    -----------------------------------------------------------

 -----------------------------------------------------------------------------
 |                                                                           |
 | Build time: 2017-02-04 07:57 CET                                          |
 |                                                                           |
 | Cezary Jackiewicz (obsy), http://eko.one.pl                               |
 |                                                                           |
 -----------------------------------------------------------------------------
 | Machine: Netgear Nighthawk X4S R7800                                      |
 | Uptime: 0d, 02:12:02                                                      |
 | Load: 0.08 0.05 0.01                                                      |
 | Flash: total: 19.4MB, free: 17.1MB, used: 7%                              |
 | Memory: total: 467.5MB, free: 413.1MB, used: 11%                          |
 | WAN: 83.xxx.xxx.xxx, proto: pppoe                                           |
 | LAN: 192.168.33.1, leases: 2                                              |
 | radio1: mode: ap, ssid: domowa, channel: auto, conn: 2                    |
 -----------------------------------------------------------------------------
 | CPU freq: 1.40GHz, 1.00GHz                                                |
 | CPU temperature: 45.85 C, 44.72 C, 45.59 C, 41.32 C                       |
 -----------------------------------------------------------------------------

root@R7800:/tmp# 3ginfo
Status: Połączony
Czas polaczenia: 0d, 03:04:52
Przeslano danych: 498.2 KiB / 27.5 KiB
Operator: Play
Tryb pracy: LTE
Sila sygnalu: 41%
Urzadzenie: huawei MegaFon M150-2
MCC MNC: 260 06
LAC: 002B (43)
CID: 00428061 (4358241)
TAC: 002B (43)
CSQ: 13
RSSI: -87 dBm
RSCP: -145 dBm
Ec/IO: -32 dB
RSRP: -105 dBm
SINR: 13 dB
RSRQ: -6 dB

root@R7800:/tmp# mwan3 status
Interface status:
 interface wan is online and tracking is active
 interface wan2 is offline and tracking is down

Current ipv4 policies:
balanced:
 wan (100%)

wan2_only:
 unreachable

wan2_wan:
 wan (100%)

wan_only:
 wan (100%)

wan_wan2:
 wan (100%)


Current ipv6 policies:
balanced:
 unreachable

wan2_only:
 unreachable

wan2_wan:
 unreachable

wan_only:
 unreachable

wan_wan2:
 unreachable


Directly connected ipv4 networks:
 224.0.0.0/3
 10.76.69.19
 192.168.33.255
 10.76.69.17
 192.168.33.0
 83.1.4.253
 10.76.69.16
 192.168.33.1
 10.76.69.16/30
 127.0.0.1
 127.0.0.0
 127.255.255.255
 83.21.81.197
 10.76.69.18
 192.168.33.0/24
 127.0.0.0/8

Directly connected ipv6 networks:
 fd6c:4f7e:494d::/64
 fe80::/64

Active ipv4 user rules:
  923 51182 S https  tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            multiport sports 0:65535 multiport dports 443
 2637  178K - wan2_wan  all  --  *      *       0.0.0.0/0            0.0.0.0/0

Active ipv6 user rules:
    0     0 S https  tcp      *      *       ::/0                 ::/0                 multiport sports 0:65535 multiport dports 443
   96 14428 - wan2_wan  all      *      *       ::/0                 ::/0


root@R7800:/tmp# cat /etc/config/network

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd6c:4f7e:494d::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth1'
        option proto 'static'
        option ipaddr '192.168.33.1'
        option netmask '255.255.255.0'
        option dns '8.8.8.8 217.17.34.68 208.67.222.222 8.8.4.4'
        option ip6assign '60'

config interface 'wan'
        option ifname 'eth0'
        option proto 'pppoe'
        option username 'xxxxx'
        option password 'xxxxx'
        option keepalive '3 20'
        option peerdns '0'
        option metric '20'

config interface 'wan2'
        option proto 'ncm'
        option device '/dev/ttyUSB0'
        #option mode 'lte'
        option apn 'internet'
        option pincode 'xxxx'
        option peerdns '0'
        option metric '10'

config interface 'wan6'
        option ifname 'eth0'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '1 2 3 4 6'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 0'

root@R7800:/tmp# cat /etc/config/mwan3

config interface 'wan'
        option enabled '1'
        list track_ip '8.8.4.4'
        list track_ip '8.8.8.8'
        list track_ip '208.67.222.222'
        list track_ip '208.67.220.220'
        option reliability '2'
        option count '1'
        option timeout '2'
        option interval '5'
        option down '3'
        option up '8'

config interface 'wan2'
        option enabled '1'
        list track_ip '8.8.8.8'
        list track_ip '208.67.220.220'
        option reliability '2'
        option count '1'
        option timeout '2'
        option interval '5'
        option down '3'
        option up '8'

config member 'wan_m1_w3'
        option interface 'wan'
        option metric '1'
        option weight '3'

config member 'wan_m2_w3'
        option interface 'wan'
        option metric '2'
        option weight '3'

config member 'wan2_m1_w2'
        option interface 'wan2'
        option metric '1'
        option weight '2'

config member 'wan2_m2_w2'
        option interface 'wan2'
        option metric '2'
        option weight '2'

config policy 'wan_only'
        list use_member 'wan_m1_w3'

config policy 'wan2_only'
        list use_member 'wan2_m1_w2'

config policy 'balanced'
        list use_member 'wan_m1_w3'
        list use_member 'wan2_m1_w2'

config policy 'wan_wan2'
        list use_member 'wan_m1_w3'
        list use_member 'wan2_m2_w2'

config policy 'wan2_wan'
        list use_member 'wan_m2_w3'
        list use_member 'wan2_m1_w2'

config rule 'https'
        option sticky '1'
        option dest_port '443'
        option proto 'tcp'
        option use_policy 'balanced'

config rule 'default_rule'
        option dest_ip '0.0.0.0/0'
        option use_policy 'wan2_wan'

2

Odp: mwan3 i LEDE 17.01-SNAPSHOT

Tak, "mode" dla ncm jest obsługiwane.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

3

Odp: mwan3 i LEDE 17.01-SNAPSHOT

Cześć,

Czy udało Ci się rozwiązać problem z  niepoprawnym statusem łącza lte w mwan3?

Mam to samo z LEDE 17.01.1 i modemem QMI.

mwan3 wersja 2.0.3

4

Odp: mwan3 i LEDE 17.01-SNAPSHOT

Weź sobie mwan3 z wersji rozwojowej albo sam zmień sobie źródła - poprawka dotyczy rozpoznawania wan_4 itd.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

5

Odp: mwan3 i LEDE 17.01-SNAPSHOT

Ale ta wersja 2.0.3 to chyba rozwojowa dla trunka?

6

Odp: mwan3 i LEDE 17.01-SNAPSHOT

W wersji rozwojowej jest 2.5.2-5

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

7

Odp: mwan3 i LEDE 17.01-SNAPSHOT

No i działa:) Dzięki,