Maxim Rusakov
-
Posts
2 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Downloads
Blogs
Events
Posts posted by Maxim Rusakov
-
-
2.16.D.12.0-5
Нуждаюсь в диагностике DHCPv6
после первиной настройки получал адрес, раздавал и всё было ок
конфиг не менялся!, но менялась версия прошивки
сейчас наблюдаю нежелание получать от провайдера IPv6 адрес на интерфейс ISP (VLAN2)
при подключении компа в порт провайдера - адрес получает
в логе роутера ничего о пакетах IPv6 нет
нуждаюсь в диагностике netflow c порта ISP, но не знаю как мне зафильтровать всё кроме DHCPv6
Хэлп
IPv6 DHCP-Client Diagnostic
in Обмен опытом
Posted
WAN перестал получать IPv6 адрес от ISP
Возможно проблема у ISP, возможно виновато обновление прошивки роутера
Какие есть инструменты диагностики?
Мы можем проинспектировать свой конфиг
! $$$ Model: ZyXEL Keenetic Ultra
! $$$ Version: 2.06.1
! $$$ Agent: cli
system
set net.ipv4.ip_forward 1
set net.ipv4.tcp_fin_timeout 30
set net.ipv4.tcp_keepalive_time 120
set net.ipv4.netfilter.ip_conntrack_tcp_timeout_established 1200
set net.ipv4.netfilter.ip_conntrack_max 4096
set vm.swappiness 100
set net.ipv6.conf.all.forwarding 1
set net.ipv6.conf.all.accept_ra 1
hostname GW01
!
interface GigabitEthernet0/Vlan1
description "Home VLAN"
security-level private
ip dhcp client dns-routes
ip dhcp client name-servers
up
!
interface GigabitEthernet0/Vlan2
rename ISP
description A1
mac address factory wan
security-level public
ip address dhcp
ip dhcp client hostname GW01
ip dhcp client dns-routes
ip dhcp client name-servers
ip mtu 1500
ip global 700
igmp upstream
ipv6 address auto
ipv6 prefix auto
ipv6 name-servers auto
up
bandwidth-limit 85880
!
interface GigabitEthernet0/0
rename 0
role inet for ISP
switchport mode access
switchport access vlan 2
up
!
interface Bridge0
rename Home
description "Home network (Wired and wireless hosts)"
inherit GigabitEthernet0/Vlan1
include AccessPoint
include AccessPoint_5G
mac access-list type none
security-level private
ip address 192.168.1.1 255.255.255.0
ip dhcp client dns-routes
ip dhcp client name-servers
igmp downstream
up
!
ipv6 subnet Default
bind Home
number 0
mode slaac
Можем посмотреть show log
I [Mar 16 20:24:26] ndm: Core::Syslog: the system log has been cleared.
W [Mar 16 20:24:54] ndhcpc: GigabitEthernet0/Vlan2: interrupted by a stop signal.
I [Mar 16 20:24:54] ndhcpc: GigabitEthernet0/Vlan2: NDM DHCP client stopped (exit status 0).
I [Mar 16 20:24:54] ndm: Dhcp::Client: stopped DHCP client on GigabitEthernet0/Vlan2.
I [Mar 16 20:24:54] ndm: Network::Interface::IP: "GigabitEthernet0/Vlan2": IP address cleared.
I [Mar 16 20:24:54] ndm: Dhcp::Client: started DHCP client on GigabitEthernet0/Vlan2.
I [Mar 16 20:24:54] nimproxy: NDM IGMP/Multicast proxy stopped (exit status: 0).
I [Mar 16 20:24:54] ndm: Network::InternetChecker: Internet access lost.
I [Mar 16 20:24:54] upnp: shutting down MiniUPnPd
I [Mar 16 20:24:54] ndm: Core::Session: client disconnected.
I [Mar 16 20:24:56] ndhcpc: GigabitEthernet0/Vlan2: NDM DHCP Client, v3.2.45.
I [Mar 16 20:24:56] ndhcpc: GigabitEthernet0/Vlan2: created PID file "/var/run/ndhcpc-eth2.2.pid".
I [Mar 16 20:24:56] nimproxy: NDM IGMP/Multicast proxy (version 0.0.33) started.
I [Mar 16 20:24:57] ndhcpc: GigabitEthernet0/Vlan2: received OFFER for 10.61.33.73 from 10.61.0.1.
I [Mar 16 20:24:58] ndhcpc: GigabitEthernet0/Vlan2: received ACK for 10.61.33.73 from 10.61.0.1 lease 3600 sec.
I [Mar 16 20:24:58] ndm: Dhcp::Client: configuring interface ISP.
I [Mar 16 20:24:58] ndm: Network::Interface::IP: "GigabitEthernet0/Vlan2": IP address is 10.61.33.73/17.
I [Mar 16 20:24:58] ndm: Dhcp::Client: obtained IP address 10.61.33.73/17.
I [Mar 16 20:24:58] ndm: Dhcp::Client: interface "ISP" is global, priority 700.
I [Mar 16 20:24:58] ndm: Dhcp::Client: adding a default route via 10.61.0.1.
I [Mar 16 20:24:58] ndm: Dhcp::Client: adding a host route to name server 37.17.118.150.
I [Mar 16 20:24:58] ndm: Dhcp::Client: adding name server 37.17.118.150.
I [Mar 16 20:24:58] ndm: Dns::Manager: name server 37.17.118.150 added, domain (default).
I [Mar 16 20:24:58] ndm: Dhcp::Client: adding a host route to name server 37.17.118.133.
I [Mar 16 20:24:58] ndm: Dhcp::Client: adding name server 37.17.118.133.
I [Mar 16 20:24:58] ndm: Dns::Manager: name server 37.17.118.133 added, domain (default).
I [Mar 16 20:24:58] nimproxy: NDM IGMP/Multicast proxy stopped (exit status: 0).
I [Mar 16 20:24:58] ndm: Network::InternetChecker: Internet access detected.
I [Mar 16 20:25:00] nimproxy: NDM IGMP/Multicast proxy (version 0.0.33) started.
I [Mar 16 20:25:00] ndm: Core::Server: started Session /var/run/ndm.core.socket.
I [Mar 16 20:25:00] upnp: HTTP listening on port 51105
I [Mar 16 20:25:00] upnp: Listening for NAT-PMP/PCP traffic on port 5351
можем посмотреть процессы
show processes
process:
comm: dhcp6c
oom-adj: -11
oom-score: 1
oom-score-adj: -750
arg: -c
arg: /var/run/dhcp6c.conf-eth2.2
arg: -p
arg: /var/run/dhcp6c.pid-eth2.2
arg: -f
arg: eth2.2
state: S (sleeping)
pid: 1252
ppid: 164
vm-size: 1476 kB
vm-data: 264 kB
vm-stk: 136 kB
vm-exe: 120 kB
vm-lib: 924 kB
vm-swap: 0 kB
threads: 1
fds: 7
statistics:
interval: 30
cpu:
now: 18637.592868
min: 0
max: 0
avg: 0
cur: 0
object:
id: Ip6::Dhcp::Client-eth2.2
state: RUNNING
service:
configured: yes
alive: yes
started: yes
state: STARTED
process:
comm: nginx: worker process
oom-adj: -7
oom-score: 1
oom-score-adj: -500
state: S (sleeping)
pid: 18849
ppid: 331
vm-size: 6668 kB
vm-data: 2172 kB
vm-stk: 136 kB
vm-exe: 956 kB
vm-lib: 2756 kB
vm-swap: 0 kB
threads: 1
fds: 14
statistics:
interval: 30
cpu:
now: 18637.592890
min: 0
max: 1
avg: 0
cur: 1
process:
comm: ndhcpc
oom-adj: -11
oom-score: 1
oom-score-adj: -750
arg: -f
arg: -n
arg: GigabitEthernet0/Vlan2
arg: -i
arg: eth2.2
arg: -s
arg: /var/run/ndhcpc-eth2.2
arg: -p
arg: /var/run/ndhcpc-eth2.2.pid
arg: -H
arg: GW01
state: S (sleeping)
pid: 19983
ppid: 164
vm-size: 1408 kB
vm-data: 232 kB
vm-stk: 136 kB
vm-exe: 84 kB
vm-lib: 924 kB
vm-swap: 0 kB
threads: 1
fds: 7
statistics:
interval: 30
cpu:
now: 18637.592910
min: 0
max: 0
avg: 0
cur: 0
object:
id: GigabitEthernet0/Vlan2 DHCP client
state: RUNNING
service:
configured: yes
alive: yes
started: yes
state: STARTED
но итог всё так же уныл. Самоназначенные адреса
show ipv6 addresses
addresses:
address:
address: fe80::ee43:f6ff:fed9:98e0
link-local: fe80::ee43:f6ff:fed9:98e0
interface: WifiMaster0
valid-lifetime: infinite
address:
address: fe80::ee43:f6ff:fed9:98e2
link-local: fe80::ee43:f6ff:fed9:98e2
interface: WifiMaster1
valid-lifetime: infinite
address:
address: fe80::ee43:f6ff:fed9:98e0
link-local: fe80::ee43:f6ff:fed9:98e0
interface: GigabitEthernet0/Vlan1
valid-lifetime: infinite
address:
address: fe80::ee43:f6ff:fed9:98e1
link-local: fe80::ee43:f6ff:fed9:98e1
interface: ISP
valid-lifetime: infinite
address:
address: fe80::ee43:f6ff:fed9:98e0
link-local: fe80::ee43:f6ff:fed9:98e0
interface: Home
valid-lifetime: infinite
Конечно втыкание компа + wireshark вместо роутера - dfhbfyn
но толку нет, если комп адрес таки просит и получает
в то время как кинетик этого не делает
Какие есть подходы к диагностике проблемы?
куда смотрят умные люди?