Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
  • 0

4.0.11 сетевые интерфейсы их поведение, основной и резрвный канал

vasek00

Asked by vasek00,

 Share

Question

vasek00 Honored Flooder

vasek00

Posted
Posted (edited)

Обновление роутера на 4.0.11, два канала интернет один в WAN порт и PPPoE основное (плюс на нем проверял расписание с 00:00 до 07:00) и провод DHCP от второго провайдера резервное плюс
1. PPPoE (WAN) - основной и подняты OpenVPN0 и Wireguard0 (Warp) + поднят Wireguard4 (Proton) + расписание 00:00 - 07:00
2. ISP (Inet-2/GigabitEthernet0/Vlan9) - резервный канал
3. WifiMaster1/AccessPoint0 - расписание 00:00 - 07:00
имеем такое поведение системы :

Сработало расписание на 00:00 на PPPoE и на WifiMaster1/AccessPoint0
  

[I] Mar  3 23:59:22 kernel: Core::Syslog: last message repeated 2 times.
[I] Mar  4 00:00:00 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(хх:хх:хх:хх:хх:ab) had disassociated by AP (reason: due to inactivity). 
[I] Mar  4 00:00:00 kernel: br0: port 3(rai0) entered disabled state
[I] Mar  4 00:00:00 ndm: Network::Interface::Base: "WifiMaster1/AccessPoint0": "schedule" changed "conf" layer state "running" to "pending". 
[I] Mar  4 00:00:00 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(хх:хх:хх:хх:хх:6c) had disassociated by AP (reason: due to inactivity). 
[I] Mar  4 00:00:00 pppd[888]: Modem hangup 
[I] Mar  4 00:00:00 ndm: Network::Interface::Base: "PPPoE0": "ppp" changed "link" layer state "running" to "pending". 
[I] Mar  4 00:00:00 ndm: Network::Interface::Ppp: "PPPoE0": connection service standby. 
[I] Mar  4 00:00:00 pppd[888]: Connect time 126.7 minutes. 
[I] Mar  4 00:00:00 pppd[888]: Sent 93802173 bytes, received 3916587284 bytes. 
[I] Mar  4 00:00:00 ndm: Network::Interface::Base: "PPPoE0": "ppp" changed "link" layer state "pending" to "running". 
[I] Mar  4 00:00:00 ndm: Network::Interface::Base: "PPPoE0": "schedule" changed "conf" layer state "running" to "pending". 
[I] Mar  4 00:00:00 pppd[888]: Connection terminated. 
[I] Mar  4 00:00:00 pppd[888]: Sent PADT 
[I] Mar  4 00:00:00 ndm: Network::Interface::Ip: "PPPoE0": IP address cleared. 
[I] Mar  4 00:00:00 pppd[888]: Terminating on signal 15 
[I] Mar  4 00:00:00 pppd[888]: Exit.

2. Напомню есть резервный канал -> основной профиль и приоритеты каналов в нем 

interface PPPoE0
    description RT
    role inet
    ip global 65431

interface GigabitEthernet0/Vlan9
    description Inet-2
    ip global 65380

3. Cамое интересное - поведение интерфейсов в данной конфигурации 

[I] Mar  4 00:00:00 ndm: Wireguard::Interface: "Wireguard0": underlying interface "PPPoE0" of peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" is down, reconnecting. 
[I] Mar  4 00:00:00 ndm: Network::RoutingTable: deleted route: 162.159.193.9/32 via PPPoE0. 
[I] Mar  4 00:00:00 ndm: Wireguard::Interface: "Wireguard0": added a host route to peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (162.159.193.9) via 10.10.8.1 (GigabitEthernet0/Vlan9). 
[I] Mar  4 00:00:00 ndm: Wireguard::Interface: "Wireguard4": underlying interface "PPPoE0" of peer "YBI............iLDY=" is down, reconnecting. 
[I] Mar  4 00:00:00 ndm: Network::RoutingTable: deleted route: 169.СерверProton/32 via PPPoE0. 
[I] Mar  4 00:00:00 ndm: Wireguard::Interface: "Wireguard4": added a host route to peer "YBI.....iLDY=" (169.СерверProton) via 10.10.8.1 (GigabitEthernet0/Vlan9). 
[I] Mar  4 00:00:00 ndm: Network::Interface::Ip: "PPPoE0": removing default route via PPPoE0. 
[I] Mar  4 00:00:00 ndm: Network::Interface::Base: "PPPoE0": interface pending by "schedule". 
[I] Mar  4 00:00:00 ndm: Network::Interface::Ppp: "PPPoE0": connection service standby. 
[I] Mar  4 00:00:00 ndm: Network::InterfaceFlusher: flushed PPPoE0 conntrack and route cache. 
[I] Mar  4 00:00:00 ndm: Network::InternetChecker: Internet access lost (status: 0x0000). 
[I] Mar  4 00:00:00 upnp: shutting down MiniUPnPd 
[I] Mar  4 00:00:00 ndm: Core::Session: client disconnected. 
[I] Mar  4 00:00:00 ndm: Network::InterfaceFlusher: flushed GigabitEthernet0/Vlan9 conntrack and route cache. 
[I] Mar  4 00:00:00 ndm: Network::InterfaceFlusher: flushed PPPoE0 conntrack and route cache. 
[I] Mar  4 00:00:00 ndm: Network::InternetChecker: Internet access detected. 
[I] Mar  4 00:00:00 ndm: Http::Nginx: loaded SSL certificate for "01....................1b.keenetic.io". 
[I] Mar  4 00:00:00 ndm: Http::Nginx: loaded SSL certificate for "XXXXXXXXXXX.keenetic.pro". 

Закрытие OpenVPN

[I] Mar  4 00:00:00 ndm: Network::Interface::Ip: "OpenVPN0": IP address cleared. 
[I] Mar  4 00:00:00 ndm: OpenVpn::Routing4: "OpenVPN0": remove installed accepted routes. 
[E] Mar  4 00:00:00 OpenVPN0: event_wait : Interrupted system call (fd=-1,code=4) 
[I] Mar  4 00:00:00 OpenVPN0: /tmp/openvpn/OpenVPN0/openvpn-down tun0 1500 0 192.168.116.74 255.255.248.0 init 
[I] Mar  4 00:00:01 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 00:00:01 ndm: Core::Session: client disconnected. 
[I] Mar  4 00:00:01 OpenVPN0: SIGTERM[hard,] received, process exiting 
[I] Mar  4 00:00:01 ndm: OpenVpn::Interface: "OpenVPN0": via interface is not ready, standby. 
[I] Mar  4 00:00:01 ndm: Http::Manager: updated configuration. 
[I] Mar  4 00:00:01 ndm: Network::RoutingTable: cleanup route to 8.8.8.8/32 via 192.168.112.1 ovpn_br0. 
[I] Mar  4 00:00:01 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 00:00:01 ndm: Network::RoutingTable: cleanup route to 192.168.104.1/32 via 192.168.112.1 ovpn_br0. 
[I] Mar  4 00:00:01 ndm: Network::RoutingTable: cleanup route to 10.224.0.0/15 via 192.168.112.1 ovpn_br0. 

Очистка маршрутов OpenVPN

[I] Mar  4 00:00:01 ndm: Network::RoutingTable: cleanup route to 74.82.64.0/19 via 192.168.112.1 ovpn_br0. 
[I] Mar  4 00:00:01 ndm: Core::Session: client disconnected. 
[I] Mar  4 00:00:01 ndm: Http::Nginx: loaded SSL certificate for "01......1b.keenetic.io". 
[I] Mar  4 00:00:01 ndm: Http::Nginx: loaded SSL certificate for ".......keenetic.pro". 
[I] Mar  4 00:00:01 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 00:00:01 ndm: Core::Session: client disconnected. 
[I] Mar  4 00:00:02 ndm: Http::Manager: updated configuration. 
[I] Mar  4 00:00:02 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 00:00:02 ndm: Core::Session: client disconnected. 
[I] Mar  4 00:00:02 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 00:00:02 upnp: HTTP listening on port 1900 
[I] Mar  4 00:00:02 upnp: Listening for NAT-PMP/PCP traffic on port 5351 

[I] Mar  4 00:00:10 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (7) (162.159.193.9:хххх) because we stopped hearing back after 15 seconds
[I] Mar  4 00:00:16 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (7) (162.159.193.9:хххх) did not complete after 5 seconds, retrying (try 2)
[I] Mar  4 00:00:38 ndm: Http::Nginx: loaded SSL certificate for "01....1b.keenetic.io". 
[I] Mar  4 00:00:39 ndm: Http::Nginx: loaded SSL certificate for "............keenetic.pro". 
[I] Mar  4 00:00:39 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 00:00:39 ndm: Core::Session: client disconnected. 
[I] Mar  4 00:00:39 ndm: Http::Manager: updated configuration. 
[I] Mar  4 00:00:39 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 00:00:39 ndm: Core::Session: client disconnected. 

[I] Mar  4 00:43:23 ndhcpc: GigabitEthernet0/Vlan9: received ACK for 10.10.8.13 from 10.10.10.100 lease 1200 sec. 
[I] Mar  4 03:23:25 ndhcpc: Core::Syslog: last message repeated 16 times.

[I] Mar  4 03:33:25 ndhcpc: GigabitEthernet0/Vlan9: received ACK for 10.10.8.13 from 10.10.10.100 lease 1200 sec. 
[I] Mar  4 03:43:25 ndhcpc: GigabitEthernet0/Vlan9: received ACK for 10.10.8.13 from 10.10.10.100 lease 1200 sec. 
[E] Mar  4 03:50:15 ndm: Io::TcpSocket: failed to connect: operation in progress. 
[E] Mar  4 03:50:15 ndm: Cloud::Tunnel: "NDMP/9хххххххa": failed to connect to 95.217.20.77:9801 (RAW): operation timeout. 
[C] Mar  4 03:50:15 ndm: Cloud::DialTunnel: system failed [0xcffd00c9]. 
[I] Mar  4 03:53:25 ndhcpc: GigabitEthernet0/Vlan9: received ACK for 10.10.8.13 from 10.10.10.100 lease 1200 sec. 

[I] Mar  4 04:00:13 kernel: wireguard: Wireguard4: handshake for peer "YBI......iLDY=" (8) (169.СерверProton) did not complete after 5 seconds, retrying (try 2)
[I] Mar  4 04:00:19 kernel: wireguard: Wireguard4: handshake for peer "YBI.....iLDY=" (8) (169.СерверProton) did not complete after 5 seconds, retrying (try 3)
[I] Mar  4 04:00:24 kernel: wireguard: Wireguard4: handshake for peer "YBI.....iLDY=" (8) (169.СерверProton) did not complete after 5 seconds, retrying (try 4)
[I] Mar  4 04:03:26 ndhcpc: GigabitEthernet0/Vlan9: received ACK for 10.10.8.13 from 10.10.10.100 lease 1200 sec. 
[I] Mar  4 04:06:06 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (7) (162.159.193.9:хххх) did not complete after 5 seconds, retrying (try 2)
[I] Mar  4 04:10:14 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (7) (162.159.193.9:хххх) did not complete after 5 seconds, retrying (try 2)
[I] Mar  4 04:13:26 ndhcpc: GigabitEthernet0/Vlan9: received ACK for 10.10.8.13 from 10.10.10.100 lease 1200 sec. 
[I] Mar  4 05:03:26 ndhcpc: Core::Syslog: last message repeated 5 times.
[E] Mar  4 05:10:21 ndm: Io::TcpSocket: failed to connect: operation in progress. 

[E] Mar  4 05:10:21 ndm: Cloud::Tunnel: "NDMP/eххххххх9": failed to connect to 95.217.20.77:9801 (RAW): operation timeout. 
[C] Mar  4 05:10:21 ndm: Cloud::DialTunnel: system failed [0xcffd00c9]. 
[I] Mar  4 05:13:26 ndhcpc: GigabitEthernet0/Vlan9: received ACK for 10.10.8.13 from 10.10.10.100 lease 1200 sec. 
[I] Mar  4 06:13:27 ndhcpc: Core::Syslog: last message repeated 6 times.

В итоге PPPoE как основного нет, он потянул за собой OpenVPN0 и Wireguard0 и Wireguard4 (так и должно быть) так как доступ к их серверам был через стат маршрут интерфейса PPPoE. Никакого переключения на резервный канал не было ISP (Inet-2/GigabitEthernet0/Vlan9) до 07:00. Так же это потянуло за собой и Cloud::Tunnel.

4. 07:00 отработало расписание по включению PPPoE и WifiMaster1/AccessPoint0 

[I] Mar  4 06:13:27 ndhcpc: Core::Syslog: last message repeated 6 times.

Сработало расписание на 07:00

[I] Mar  4 06:53:28 ndhcpc: Core::Syslog: last message repeated 3 times.
[I] Mar  4 07:00:00 kernel: IPv6: ADDRCONF(NETDEV_UP): rai0: link is not ready
[I] Mar  4 07:00:00 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): rai0: link becomes ready
[I] Mar  4 07:00:00 ndm: Network::Interface::Base: "WifiMaster1/AccessPoint0": "schedule" changed "conf" layer state "pending" to "running". 
[I] Mar  4 07:00:00 kernel: br0: port 3(rai0) entered blocking state
[I] Mar  4 07:00:00 kernel: br0: port 3(rai0) entered listening state
[I] Mar  4 07:00:00 ndm: Network::Interface::Base: "PPPoE0": "schedule" changed "conf" layer state "pending" to "running". 
[I] Mar  4 07:00:02 wind: version 1.0.3 started on br0. 
[I] Mar  4 07:00:02 pppd[11305]: Plugin rp-pppoe.so loaded. 
[I] Mar  4 07:00:02 pppd[11305]: pppd 2.4.4-4 started by root, uid 0 
[I] Mar  4 07:00:02 pppd[11305]: Found unterminated session: 30539:90:хх:хх:хх:хх:ed 
[I] Mar  4 07:00:03 pppd[11305]: Sent PADT 
[I] Mar  4 07:00:03 kernel: br0: port 3(rai0) entered learning state
[I] Mar  4 07:00:03 pppd[11305]: PPP session is 28750 
[I] Mar  4 07:00:03 pppd[11305]: Using interface ppp0 
[I] Mar  4 07:00:03 pppd[11305]: Connect: ppp0 <--> eth3 
...
[I] Mar  4 07:00:03 ndm: Network::Interface::Base: "PPPoE0": interface is up. 
[I] Mar  4 07:00:03 ndm: Network::Interface::Ip: "PPPoE0": interface "PPPoE0" is global, priority 65431. 
[I] Mar  4 07:00:03 ndm: Network::Interface::Ip: "PPPoE0": adding default route via PPPoE0. 
[I] Mar  4 07:00:03 ndm: Network::Interface::Ip: "PPPoE0": IP address is ххх.ххх.ххх.202/32. 
[I] Mar  4 07:00:03 ndm: Network::Interface::Base: "PPPoE0": "ppp" changed "link" layer state "connecting" to "running". 
[I] Mar  4 07:00:03 ndm: Network::InterfaceFlusher: flushed GigabitEthernet0/Vlan9 conntrack and route cache. 
[I] Mar  4 07:00:03 ndm: Network::InternetChecker: Internet access lost (status: 0x0000). 
[I] Mar  4 07:00:03 upnp: shutting down MiniUPnPd 
[I] Mar  4 07:00:03 ndm: Core::Session: client disconnected. 
[I] Mar  4 07:00:03 ndm: Wireguard::Interface: "Wireguard0": reconnecting peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" via "PPPoE0". 
[I] Mar  4 07:00:03 ndm: Network::RoutingTable: deleted route: 162.159.193.9/32 via 10.10.8.1 (GigabitEthernet0/Vlan9). 
[I] Mar  4 07:00:03 ndm: Wireguard::Interface: "Wireguard0": added a host route to peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (162.159.193.9) via PPPoE0 (PPPoE0). 
[I] Mar  4 07:00:03 ndm: Wireguard::Interface: "Wireguard4": reconnecting peer "YBI..........iLDY=" via "PPPoE0". 
[I] Mar  4 07:00:03 ndm: Network::RoutingTable: deleted route: 169.СерверProton/32 via 10.10.8.1 (GigabitEthernet0/Vlan9). 
[I] Mar  4 07:00:03 ndm: Wireguard::Interface: "Wireguard4": added a host route to peer "YBI.......iLDY=" (169.СерверProton) via PPPoE0 (PPPoE0). 
[I] Mar  4 07:00:03 ndm: Network::InternetChecker: Internet access detected. 
[I] Mar  4 07:00:04 ndm: Http::Nginx: loaded SSL certificate for "01.......b.keenetic.io". 
[I] Mar  4 07:00:04 ndm: Http::Nginx: loaded SSL certificate for "xxxxxxxxx.keenetic.pro". 
[I] Mar  4 07:00:04 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 07:00:04 ndm: Core::Session: client disconnected. 
[I] Mar  4 07:00:04 ndm: Http::Manager: updated configuration. 
[I] Mar  4 07:00:04 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 07:00:04 ndm: Core::Session: client disconnected. 
[I] Mar  4 07:00:05 ndm: Core::Server: started Session /var/run/ndm.core.socket. 
[I] Mar  4 07:00:05 upnp: HTTP listening on port 1900 
[I] Mar  4 07:00:05 upnp: Listening for NAT-PMP/PCP traffic on port 5351

В итоге два Wireguard0 и Wireguard4 поднялись - так как стат маршрут до их серверов сработал через PPPoE :

Wireguard0 - канал через PPPoE

Wireguard4 - канал GigabitEthernet0/Vlan9

OpenVPN чуток не понятно с отображением в WEB (надо еще проверить), но так же поднялся 

[I] Mar  4 07:00:05 upnp: HTTP listening on port 1900 
[I] Mar  4 07:00:05 upnp: Listening for NAT-PMP/PCP traffic on port 5351 
[I] Mar  4 07:00:06 OpenVPN0: OpenVPN 2.6.0 [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] 
[I] Mar  4 07:00:06 OpenVPN0: library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10 
[I] Mar  4 07:00:06 OpenVPN0: Attempting to establish TCP connection with [AF_INET]51.75.75.245:1194 
[I] Mar  4 07:00:06 kernel: br0: port 3(rai0) entered forwarding state
[I] Mar  4 07:00:06 kernel: br0: topology change detected, propagating
[I] Mar  4 07:00:06 OpenVPN0: TCP connection established with [AF_INET]51.75.75.245:1194 
[I] Mar  4 07:00:06 OpenVPN0: TCPv4_CLIENT link local (bound): [AF_INET]ххх.PPPoE.ххх.ххх:48920 
[I] Mar  4 07:00:06 OpenVPN0: TCPv4_CLIENT link remote: [AF_INET]51.75.75.245:1194 
[I] Mar  4 07:00:06 OpenVPN0: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay 
[I] Mar  4 07:00:07 OpenVPN0: [antizapret-server] Peer Connection Initiated with [AF_INET]51.75.75.245:1194 
[I] Mar  4 07:00:07 ndm: OpenVpn::Routing4: "OpenVPN0": connecting via PPPoE0 (PPPoE0). 
[I] Mar  4 07:00:07 ndm: OpenVpn::Routing4: "OpenVPN0": added host route to remote endpoint 51.75.75.245 via PPPoE0. 
[I] Mar  4 07:00:08 OpenVPN0: TUN/TAP device tun0 opened 
[I] Mar  4 07:00:08 OpenVPN0: net_iface_mtu_set: mtu 1500 for tun0 
[I] Mar  4 07:00:08 ndm: Network::Interface::Ip: "OpenVPN0": IP address is 192.168.108.183/21. 
[I] Mar  4 07:00:08 OpenVPN0: /tmp/openvpn/OpenVPN0/openvpn-up tun0 1500 0 192.168.108.183 255.255.248.0 init 
[I] Mar  4 07:00:08 ndm: OpenVpn::Routing4: "OpenVPN0": install accepted route to 8.8.8.8/255.255.255.255 via 192.168.104.1. 
[I] Mar  4 07:00:08 ndm: OpenVpn::Routing4: "OpenVPN0": install accepted route to 10.224.0.0/255.254.0.0 via 192.168.104.1. 
Полученв маршруты 
[I] Mar  4 07:00:08 ndm: OpenVpn::Routing4: "OpenVPN0": install accepted route to 74.82.64.0/255.255.224.0 via 192.168.104.1. 
[I] Mar  4 07:00:08 OpenVPN0: UID set to nobody 
[I] Mar  4 07:00:08 OpenVPN0: GID set to nobody 
[I] Mar  4 07:00:08 OpenVPN0: Capabilities retained: CAP_NET_ADMIN 
[I] Mar  4 07:00:08 OpenVPN0: Initialization Sequence Completed

При отработке в ручном режиме - отключение основного PPPoE (через WEB) все переключилось на резервный GigabitEthernet0/Vlan9 и поднялись Wireguard0 с Wireguard4. C OpenVPN речь отдельная пока не понятно что с ним.

Включение основного (опять через WEB) PPPoE все вернулось через него.

 

OpenVPN - не понятно пока 

Мар 4 09:55:51 OpenVPN0 OpenVPN 2.6.0 [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
Мар 4 09:55:51 OpenVPN0 library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10
Мар 4 09:55:51 OpenVPN0 Attempting to establish TCP connection with [AF_INET]51.158.181.161:1194
Мар 4 09:55:51 OpenVPN0 TCP connection established with [AF_INET]51.158.181.161:1194
Мар 4 09:55:51 OpenVPN0 TCPv4_CLIENT link local (bound): [AF_INET]ххх.PPPoE:48920
Мар 4 09:55:51 OpenVPN0 TCPv4_CLIENT link remote: [AF_INET]51.158.181.161:1194
Мар 4 09:55:51 OpenVPN0 NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Мар 4 09:55:52 OpenVPN0 [antizapret-server] Peer Connection Initiated with [AF_INET]51.158.181.161:1194
Мар 4 09:55:52 ndm OpenVpn::Routing4: "OpenVPN0": connecting via PPPoE0 (PPPoE0).
Мар 4 09:55:52 ndm OpenVpn::Routing4: "OpenVPN0": added host route to remote endpoint 51.158.181.161 via PPPoE0.
Мар 4 09:55:53 OpenVPN0 TUN/TAP device tun0 opened
Мар 4 09:55:53 OpenVPN0 net_iface_mtu_set: mtu 1500 for tun0
Мар 4 09:55:53 ndm Network::Interface::Ip: "OpenVPN0": IP address is 192.168.124.218/21.
Мар 4 09:55:53 OpenVPN0 /tmp/openvpn/OpenVPN0/openvpn-up tun0 1500 0 192.168.124.218 255.255.248.0 init
Мар 4 09:55:53 ndm OpenVpn::Routing4: "OpenVPN0": install accepted route to 8.8.8.8/255.255.255.255 via 192.168.120.1.
Мар 4 09:55:53 ndm OpenVpn::Routing4: "OpenVPN0": install accepted route to 192.168.104.1/255.255.255.255 via 192.168.120.1.
Мар 4 09:55:53 ndm OpenVpn::Routing4: "OpenVPN0": install accepted route to 10.224.0.0/255.254.0.0 via 192.168.120.1.

Куча полученных маршрутов

Мар 4 09:55:53 ndm OpenVpn::Routing4: "OpenVPN0": install accepted route to 74.82.64.0/255.255.224.0 via 192.168.120.1.
Мар 4 09:55:53 OpenVPN0 UID set to nobody
Мар 4 09:55:53 OpenVPN0 GID set to nobody
Мар 4 09:55:53 OpenVPN0 Capabilities retained: CAP_NET_ADMIN
Мар 4 09:55:53 OpenVPN0 Initialization Sequence Completed

Но в реале маршрутов нет и в WEB

Скрытый текст

-4.thumb.jpg.cda3f6c9df7ca751055da4ec5e2a723b.jpg

 

Скрытый текст 
~ # ip ro
default dev ppp0  scope link 
10.10.8.0/24 dev eth2.9  proto kernel  scope link  src 10.10.8.13 
51.158.181.161 dev ppp0  scope link **** Сервер для OpenVPN 
....
162.159.193.9 dev ppp0  scope link **** Сервер WG0
169.СерверProton dev ppp0  scope link **** Сервер WG4
...
192.168.120.0/21 dev ovpn_br0  proto kernel  scope link  src 192.168.124.218 **** OpenVPN
192.168.130.0/24 dev br0  proto kernel  scope link  src 192.168.130.101 
192.168.130.101 dev nwg0  scope link 
...
~ #

ovpn_br0  Link encap:Ethernet  HWaddr хх:хх:хх:хх:хх:CF  
          inet addr:192.168.124.218  P-t-P:192.168.124.218  Bcast:0.0.0.0  Mask:255.255.248.0
          ...
          UP BROADCAST POINTOPOINT RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:232 (232.0 B)

~ # ping 192.168.120.1
PING 192.168.120.1 (192.168.120.1): 56 data bytes
64 bytes from 192.168.120.1: seq=0 ttl=64 time=67.334 ms
64 bytes from 192.168.120.1: seq=1 ttl=64 time=101.969 ms
^C
--- 192.168.120.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 67.334/84.651/101.969 ms
~ # traceroute 192.168.120.1
traceroute to 192.168.120.1 (192.168.120.1), 30 hops max, 46 byte packets
 1  192.168.120.1 (192.168.120.1)  66.826 ms  67.227 ms  68.861 ms
~ # 

~ # ip ro add 8.8.8.8/32 dev ovpn_br0

~ # ip ro
default dev ppp0  scope link 
8.8.8.8 dev ovpn_br0  scope link 
...
192.168.120.0/21 dev ovpn_br0  proto kernel  scope link  src 192.168.124.218 
...

~ # traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 46 byte packets
 1  192.168.120.1 (192.168.120.1)  74.320 ms  67.464 ms  81.577 ms
 2  192.168.120.1 (192.168.120.1)  78.635 ms  67.636 ms  66.933 ms

 

 

Edited by vasek00
Link to comment
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...