Project

General

Profile

Bug #10692 » 20200623 Pimd_VIF-issue_FoundViaInterfaceExpiriment.txt

Test_Expiriment_Description - Louis B, 06/23/2020 12:56 PM

 
1
This evening got a strange idea related to the PIMD problem ..... what would happen if ...... I disable the interfaces treated more or less correctly
2
- so I disabled my guestlan and (vlan26)1
3
- I disabled my IoT-lan (vlan13)
4
That are two from this three
5
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
6

    
7
So and then
8
- kill pimd (pimd -q)
9
- start pimd (pimd -c /var/etc/pimd/pimd.conf -d -f -N)
10

    
11
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 ??
12

    
13
And thank what ...... now I did enable the guestlan And now I have ....
14
18:54:00.758 Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
15
18:54:00.758 Installing lagg0.16 (192.168.1.1 on subnet 192.168.1) as vif #1 - rate 0
16
18:54:00.758 Installing lagg0.100 (192.168.100.1 on subnet 192.168.100) as vif #2 - rate 0
17
18:54:00.758 Installing lagg0.88 (192.168.88.3 on subnet 192.168.88) as vif #3 - rate 0
18
18:54:00.758 Installing ix0.14 (192.168.14.1 on subnet 192.168.14) as vif #4 - rate 0
19
18:54:00.758 Installing ix0.18 (192.168.18.1 on subnet 192.168.18) as vif #5 - rate 0
20
18:54:00.758 Installing ix1.116 (192.168.116.1 on subnet 192.168.116) as vif #6 - rate 0
21
18:54:00.758 Installing pppoe1 (83.162.43.161 -> 194.109.5.227) as vif #7 - rate=0
22
18:54:00.758 Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #8 - rate 0
23
18:54:00.758 Disabling all vifs from kernel Yep eight vlans with vifs
24

    
25
Becoming interested I decided to activate the IoT lan as well lets see what happens And now .....
26
18:56:34.583 Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
27
18:56:34.583 Installing lagg0.16 (192.168.1.1 on subnet 192.168.1) as vif #1 - rate 0
28
18:56:34.583 Installing lagg0.100 (192.168.100.1 on subnet 192.168.100) as vif #2 - rate 0
29
18:56:34.583 Installing lagg0.88 (192.168.88.3 on subnet 192.168.88) as vif #3 - rate 0
30
18:56:34.583 Installing ix0.14 (192.168.14.1 on subnet 192.168.14) as vif #4 - rate 0
31
18:56:34.583 Installing ix0.18 (192.168.18.1 on subnet 192.168.18) as vif #5 - rate 0
32
18:56:34.583 Installing ix1.116 (192.168.116.1 on subnet 192.168.116) as vif #6 - rate 0
33
18:56:34.583 Installing pppoe1 (83.162.43.161 -> 194.109.5.227) as vif #7 - rate=0
34
18:56:34.583 Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #8 - rate 0
35
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
36

    
37
So lets do a reboot
38
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'
39
Jun 23 19:00:38 pfSense pimd[20988]: /var/etc/pimd/pimd.conf:9 - Invalid phyint address 'ix1.116'
40
Jun 23 19:00:38 pfSense pimd[20988]: /var/etc/pimd/pimd.conf:8 - Invalid phyint address 'lagg0.16'
41
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 ...
42

    
43
And the problem is back ..........
44
So something in the bootcyclus is spooling everything .......
45
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 .....
46

    
47
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'
48
Jun 23 19:11:39 pfSense pimd[92845]: /var/etc/pimd/pimd.conf:9 - Invalid phyint address 'ix1.116'
49
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 ...
50
Again not ok
51

    
52
So something in the boot sequence is killing the "assign vif" process .......
53
Question is ...... what is going wrong ..........
54
Two pimd evens in parallel !!??
55

    
56
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 ...
57
Jun 23 19:11:35 pfSense pimd[14821]: pimd version 2.3.2 starting ...
58

    
59

    
60
By the way no even a "light smell" from IPV6 ......
61

    
62

    
63
Louis
(1-1/7)