|
1
|
Mail I did send to PIMD-developer idi 23-6-2020
|
|
2
|
|
|
3
|
Bjorn,
|
|
4
|
|
|
5
|
I got a strange idea 15 minutes ago ..... what would happen if ...... I disable the interfaces treated more or less correctly
|
|
6
|
- so I disabled my guestlan and (vlan26)1
|
|
7
|
- I disabled my IoT-lan (vlan13)
|
|
8
|
That are two from this three
|
|
9
|
Jun 20 13:54:04 pfSense pimd[32235]: Disabling all vifs from kernel Jun 20 13:54:04 pfSense pimd[32235]: Installing lagg0.13 (192.168.13.1 on subnet 192.168.13) as vif #2 - rate 0 Jun 20 13:54:04 pfSense pimd[31825]: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0 Jun 20 13:54:04 pfSense pimd[32235]: Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #1 - rate 0
|
|
10
|
|
|
11
|
So and then
|
|
12
|
- kill pimd (pimd -q)
|
|
13
|
- start pimd (pimd -c /var/etc/pimd/pimd.conf -d -f -N)
|
|
14
|
|
|
15
|
And now see and be surprised. Now we have 7 recognised vifs, in state of the earlier 3 ......... of course still vifs missing That must be something to think about ??
|
|
16
|
|
|
17
|
And thank what ...... now I did enable the guestlan And now I have ....
|
|
18
|
18:54:00.758 Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
|
|
19
|
18:54:00.758 Installing lagg0.16 (192.168.1.1 on subnet 192.168.1) as vif #1 - rate 0
|
|
20
|
18:54:00.758 Installing lagg0.100 (192.168.100.1 on subnet 192.168.100) as vif #2 - rate 0
|
|
21
|
18:54:00.758 Installing lagg0.88 (192.168.88.3 on subnet 192.168.88) as vif #3 - rate 0
|
|
22
|
18:54:00.758 Installing ix0.14 (192.168.14.1 on subnet 192.168.14) as vif #4 - rate 0
|
|
23
|
18:54:00.758 Installing ix0.18 (192.168.18.1 on subnet 192.168.18) as vif #5 - rate 0
|
|
24
|
18:54:00.758 Installing ix1.116 (192.168.116.1 on subnet 192.168.116) as vif #6 - rate 0
|
|
25
|
18:54:00.758 Installing pppoe1 (83.162.43.161 -> 194.109.5.227) as vif #7 - rate=0
|
|
26
|
18:54:00.758 Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #8 - rate 0
|
|
27
|
18:54:00.758 Disabling all vifs from kernel Yep eight vlans with vifs
|
|
28
|
|
|
29
|
Becoming interested I decided to activate the IoT lan as well lets see what happens And now .....
|
|
30
|
18:56:34.583 Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
|
|
31
|
18:56:34.583 Installing lagg0.16 (192.168.1.1 on subnet 192.168.1) as vif #1 - rate 0
|
|
32
|
18:56:34.583 Installing lagg0.100 (192.168.100.1 on subnet 192.168.100) as vif #2 - rate 0
|
|
33
|
18:56:34.583 Installing lagg0.88 (192.168.88.3 on subnet 192.168.88) as vif #3 - rate 0
|
|
34
|
18:56:34.583 Installing ix0.14 (192.168.14.1 on subnet 192.168.14) as vif #4 - rate 0
|
|
35
|
18:56:34.583 Installing ix0.18 (192.168.18.1 on subnet 192.168.18) as vif #5 - rate 0
|
|
36
|
18:56:34.583 Installing ix1.116 (192.168.116.1 on subnet 192.168.116) as vif #6 - rate 0
|
|
37
|
18:56:34.583 Installing pppoe1 (83.162.43.161 -> 194.109.5.227) as vif #7 - rate=0
|
|
38
|
18:56:34.583 Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #8 - rate 0
|
|
39
|
18:56:34.583 Installing lagg0.13 (192.168.13.1 on subnet 192.168.13) as vif #9 - rate 0 Yep nine vlans not wan vlans have a vif assigned
|
|
40
|
|
|
41
|
So lets do a reboot
|
|
42
|
Jun 23 19:00:49 pfSense nginx: 2020/06/23 19:00:49 [error] 38862#100134: send() failed (54: Connection reset by peer) Jun 23 19:00:42 pfSense pkg-static[66778]: pfSense-repo upgraded: 2.5.0.a.20200623.0050 -> 2.5.0.a.20200623.0650 Jun 23 19:00:39 pfSense login[23484]: login on ttyv0 as root Jun 23 19:00:38 pfSense pimd[20988]: Cannot forward: no enabled vifs Jun 23 19:00:38 pfSense pimd[20988]: Local static RP: 169.254.0.1, group 232.0.0.0/8 Jun 23 19:00:38 pfSense pimd[20988]: Local static RP: 192.168.14.15, group 224.0.0.0/4 Jun 23 19:00:38 pfSense pimd[20988]: /var/etc/pimd/pimd.conf:11 - Invalid phyint address 'ix0.14'
|
|
43
|
Jun 23 19:00:38 pfSense pimd[20988]: /var/etc/pimd/pimd.conf:9 - Invalid phyint address 'ix1.116'
|
|
44
|
Jun 23 19:00:38 pfSense pimd[20988]: /var/etc/pimd/pimd.conf:8 - Invalid phyint address 'lagg0.16'
|
|
45
|
Jun 23 19:00:38 pfSense pimd[20988]: Recommended querier timeout = Robustness x query-interval + response-time / 2 = 3 x 6 + 10 / 2 = 23 Jun 23 19:00:38 pfSense pimd[20988]: Getting vifs from /var/etc/pimd/pimd.conf Jun 23 19:00:38 pfSense pimd[20988]: Disabling all vifs from kernel Jun 23 19:00:38 pfSense pimd[20988]: Installing lagg0.13 (192.168.13.1 on subnet 192.168.13) as vif #2 - rate 0 Jun 23 19:00:38 pfSense pimd[20988]: Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #1 - rate 0 Jun 23 19:00:38 pfSense pimd[20988]: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0 Jun 23 19:00:38 pfSense pimd[20988]: Getting vifs from kernel Jun 23 19:00:38 pfSense pimd[20988]: pimd version 2.3.2 starting ...
|
|
46
|
|
|
47
|
And the problem is back ..........
|
|
48
|
So something in the bootcyclus is spooling everything .......
|
|
49
|
Has of course nothing to do with the pimd configuration file, given the fact that the pimd.conf only becomes interesting after installing the vifs .....
|
|
50
|
|
|
51
|
So lets do a final test, reboot with the two interfaces disabled Jun 23 19:11:39 pfSense pimd[92845]: Cannot forward: no enabled vifs Jun 23 19:11:39 pfSense pimd[92845]: Local static RP: 169.254.0.1, group 232.0.0.0/8 Jun 23 19:11:39 pfSense pimd[92845]: Local static RP: 192.168.14.15, group 224.0.0.0/4 Jun 23 19:11:39 pfSense pimd[92845]: /var/etc/pimd/pimd.conf:10 - Invalid phyint address 'ix0.14'
|
|
52
|
Jun 23 19:11:39 pfSense pimd[92845]: /var/etc/pimd/pimd.conf:9 - Invalid phyint address 'ix1.116'
|
|
53
|
Jun 23 19:11:39 pfSense pimd[92845]: Recommended querier timeout = Robustness x query-interval + response-time / 2 = 3 x 6 + 10 / 2 = 23 Jun 23 19:11:39 pfSense pimd[92845]: Getting vifs from /var/etc/pimd/pimd.conf Jun 23 19:11:39 pfSense pimd[92845]: Disabling all vifs from kernel Jun 23 19:11:39 pfSense pimd[92845]: Installing lagg0.16 (192.168.1.1 on subnet 192.168.1) as vif #1 - rate 0 Jun 23 19:11:39 pfSense pimd[92845]: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0 Jun 23 19:11:39 pfSense pimd[92845]: Getting vifs from kernel Jun 23 19:11:39 pfSense pimd[92845]: pimd version 2.3.2 starting ...
|
|
54
|
Again not ok
|
|
55
|
|
|
56
|
So something in the boot sequence is killing the "assign vif" process .......
|
|
57
|
Question is ...... what is going wrong ..........
|
|
58
|
Two pimd evens in parallel !!??
|
|
59
|
|
|
60
|
Jun 23 19:11:35 pfSense pimd[14821]: Getting vifs from /var/etc/pimd/pimd.conf Jun 23 19:11:35 pfSense pimd[15347]: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0 Jun 23 19:11:35 pfSense pimd[14821]: Disabling all vifs from kernel Jun 23 19:11:35 pfSense pimd[14821]: Installing lagg0.16 (192.168.1.1 on subnet 192.168.1) as vif #1 - rate 0 Jun 23 19:11:35 pfSense pimd[14821]: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0 Jun 23 19:11:35 pfSense pimd[15347]: Getting vifs from kernel Jun 23 19:11:35 pfSense pimd[14821]: Getting vifs from kernel Jun 23 19:11:35 pfSense pimd[15347]: pimd version 2.3.2 starting ...
|
|
61
|
Jun 23 19:11:35 pfSense pimd[14821]: pimd version 2.3.2 starting ...
|
|
62
|
|
|
63
|
|
|
64
|
By the way no even a "light smell" from IPV6 ......
|
|
65
|
|
|
66
|
|
|
67
|
Louis
|
|
68
|
----------------------------
|
|
69
|
debug level 0xffffffff (dvmrp_detail,dvmrp_prunes,dvmrp_routes,dvmrp_neighbors,dvmrp_timers,igmp_proto,igmp_timers,igmp_members,trace,timeout,packets,interfaces,kernel,cache,rsrr,pim_detail,pim_hello,pim_register,pim_join_prune,pim_bootstrap,pim_asserts,pim_cand_rp,pim_routes,pim_timers,pim_rpf)
|
|
70
|
18:43:57.805 pimd version 2.3.2 starting ...
|
|
71
|
18:43:57.805 Got 262144 byte send buffer size in 0 iterations
|
|
72
|
18:43:57.805 Got 262144 byte recv buffer size in 0 iterations
|
|
73
|
18:43:57.805 Got 262144 byte send buffer size in 0 iterations
|
|
74
|
18:43:57.805 Got 262144 byte recv buffer size in 0 iterations
|
|
75
|
18:43:57.805 Getting vifs from kernel
|
|
76
|
18:43:57.805 Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
|
|
77
|
18:43:57.805 Installing lagg0.16 (192.168.1.1 on subnet 192.168.1) as vif #1 - rate 0
|
|
78
|
18:43:57.805 Installing lagg0.100 (192.168.100.1 on subnet 192.168.100) as vif #2 - rate 0
|
|
79
|
18:43:57.805 Installing lagg0.88 (192.168.88.3 on subnet 192.168.88) as vif #3 - rate 0
|
|
80
|
18:43:57.805 Installing ix0.14 (192.168.14.1 on subnet 192.168.14) as vif #4 - rate 0
|
|
81
|
18:43:57.805 Installing ix0.18 (192.168.18.1 on subnet 192.168.18) as vif #5 - rate 0
|
|
82
|
18:43:57.805 Installing ix1.116 (192.168.116.1 on subnet 192.168.116) as vif #6 - rate 0
|
|
83
|
18:43:57.805 Installing pppoe1 (83.162.43.161 -> 194.109.5.227) as vif #7 - rate=0
|
|
84
|
18:43:57.805 Disabling all vifs from kernel
|
|
85
|
18:43:57.805 Getting vifs from /var/etc/pimd/pimd.conf
|
|
86
|
18:43:57.805 Recommended querier timeout = Robustness x query-interval + response-time / 2 = 3 x 6 + 10 / 2 = 23
|
|
87
|
18:43:57.805 /var/etc/pimd/pimd.conf:10 - Invalid phyint address 'lagg0.26'
|
|
88
|
18:43:57.806 Local static RP: 192.168.14.15, group 224.0.0.0/4
|
|
89
|
18:43:57.806 Local static RP: 169.254.0.1, group 232.0.0.0/8
|
|
90
|
18:43:57.806 IGMP query interval : 6 sec
|
|
91
|
18:43:57.806 IGMP querier timeout : 23 sec
|
|
92
|
18:43:57.806 Cannot forward: no enabled vifs
|
|
93
|
|
|
94
|
|