-
Notifications
You must be signed in to change notification settings - Fork 9
/
ipv4.feature
3718 lines (3275 loc) · 190 KB
/
ipv4.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Feature: nmcli: ipv4
# Please do use tags as follows:
# @bugzilla_link (rhbz123456)
# @version_control (ver+=1.10,rhelver-=8,fedoraver+30,[not_with_]rhel_pkg,[not_with_]fedora_pkg) - see version_control.py
# @other_tags (see environment.py)
# @test_name (compiled from scenario name)
# Scenario:
@ipv4_method_static_no_IP
Scenario: nmcli - ipv4 - method - static without IP
* Add "ethernet" connection named "con_ipv4" for device "eth3"
* Open editor for connection "con_ipv4"
* Submit "set ipv4.method static" in editor
* Save in editor
Then Error type "connection verification failed: ipv4" while saving in editor
@rhbz979288
@ipv4_method_manual_with_IP
Scenario: nmcli - ipv4 - method - manual + IP
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.122.253
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "5" seconds
Then "192.168.122.253/32" is visible with command "ip a s eth3"
Then "dhclient-eth3.pid" is not visible with command "ps aux|grep dhclient"
@ipv4_method_static_with_IP
Scenario: nmcli - ipv4 - method - static + IP
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.122.253
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "5" seconds
Then "192.168.122.253/32" is visible with command "ip a s eth3"
@ipv4_addresses_manual_when_asked
Scenario: nmcli - ipv4 - addresses - IP allowing manual when asked
* Add "ethernet" connection named "con_ipv4" for device "eth3"
* Open editor for connection "con_ipv4"
* Submit "set ipv4.addresses 192.168.122.253" in editor
* Submit "yes" in editor
* Save in editor
* Quit editor
* Bring "up" connection "con_ipv4"
Then "192.168.122.253/32" is visible with command "ip a s eth3"
@rhbz1034900
@ipv4_addresses_IP_slash_mask
Scenario: nmcli - ipv4 - addresses - IP slash netmask
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.122.253/24
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "5" seconds
Then "192.168.122.253/24 brd 192.168.122.255" is visible with command "ip a s eth3"
@ipv4_change_in_address
Scenario: nmcli - ipv4 - addresses - change in address
* Add "ethernet" connection named "con_ipv4" for device "eth3"
* Open editor for connection "con_ipv4"
* Submit "set ipv4.method manual" in editor
* Submit "set ipv4.addresses 1.1.1.99/24" in editor
* Submit "set ipv4.gateway 1.1.1.1" in editor
* Save in editor
* Submit "goto ipv4" in editor
* Submit "goto gateway" in editor
* Submit "change" in editor
* Backspace in editor
* Submit "4" in editor
* Submit "back" in editor
* Submit "back" in editor
* Save in editor
* Submit "print" in editor
* Quit editor
* Bring "up" connection "con_ipv4"
Then "1.1.1.99/24 brd 1.1.1.255" is visible with command "ip a s eth3"
Then "default via 1.1.1.4" is visible with command "ip route"
Then "default via 1.1.1.1" is not visible with command "ip route"
@ipv4_addresses_IP_slash_invalid_mask
Scenario: nmcli - ipv4 - addresses - IP slash invalid netmask
* Add "ethernet" connection named "con_ipv4" for device "eth3"
* Open editor for connection "con_ipv4"
* Submit "set ipv4.method static" in editor
* Submit "set ipv4.addresses 192.168.122.253/192.168.122.1" in editor
Then Error type "failed to set 'addresses' property: invalid prefix '192.168.122.1'; <[01]-32> allowed" while saving in editor
@rhbz1073824
@delete_testeth0 @restart_if_needed
@ipv4_take_manually_created_keyfile_with_ip
Scenario: nmcli - ipv4 - use manually created ipv4 profile
* Create keyfile "/etc/NetworkManager/system-connections/con_ipv4.nmconnection"
"""
[connection]
uuid=aa17d688-a38d-481d-888d-6d69cca781b8
autoconnect=yes
interface-name=eth3
type=ethernet
id=con_ipv4
[ipv4]
method=manual
address1=10.0.0.2/24,10.0.0.1
"""
* Restart NM
Then "aa17d688-a38d-481d-888d-6d69cca781b8" is visible with command "nmcli -f UUID connection show -a" in "5" seconds
@ipv4_addresses_IP_slash_mask_and_route
Scenario: nmcli - ipv4 - addresses - IP slash netmask and route
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.122.253/24
ipv4.gateway 192.168.122.96
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "5" seconds
Then "192.168.122.253/24" is visible with command "ip a s eth3"
Then "default via 192.168.122.96 dev eth3\s+proto static\s+metric" is visible with command "ip route"
Then "192.168.122.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.122.253" is visible with command "ip route"
Then "eth0" is visible with command "ip r |grep 'default via 1'" in "5" seconds
Then "eth3" is visible with command "ip r |grep 'default via 1'" in "5" seconds
@ipv4_addresses_more_IPs_slash_mask_and_route
Scenario: nmcli - ipv4 - addresses - several IPs slash netmask and route
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses '192.168.22.253/24, 192.168.122.253/16, 192.168.222.253/8'
ipv4.gateway 192.168.22.96
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "5" seconds
Then "192.168.22.253/24" is visible with command "ip a s eth3"
Then "192.168.122.253/16" is visible with command "ip a s eth3"
Then "192.168.222.253/8" is visible with command "ip a s eth3"
Then "default via 192.168.22.96 dev eth3\s+proto static\s+metric" is visible with command "ip route"
Then "eth3" is visible with command "ip r |grep 'default via 1'" in "5" seconds
@rhbz663730
@ver+=1.9.2
@route_priorities
Scenario: nmcli - ipv4 - route priorities
* Add "ethernet" connection named "con_ipv4" for device "eth2" with options "autoconnect no ipv4.may-fail no"
* Add "ethernet" connection named "con_ipv42" for device "eth3" with options "autoconnect no ipv4.may-fail no"
* Bring "up" connection "con_ipv4"
* Bring "up" connection "con_ipv42"
When "metric 1" is visible with command "ip r |grep default |grep eth2"
When "metric 1" is visible with command "ip r |grep default |grep eth3"
* Modify connection "con_ipv42" changing options "ipv4.route-metric 200"
* Bring "up" connection "con_ipv42"
When "metric 1" is visible with command "ip r |grep default |grep eth2"
When "metric 200" is visible with command "ip r |grep default |grep eth3"
* Modify connection "con_ipv42" changing options "ipv4.route-metric -1"
* Bring "up" connection "con_ipv42"
When "metric 1" is visible with command "ip r |grep default |grep eth2"
When "metric 1" is visible with command "ip r |grep default |grep eth3"
@ver-=1.39.2
@ipv4_method_back_to_auto
Scenario: nmcli - ipv4 - addresses - delete IP and set method back to auto
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses '192.168.22.253/24, 192.168.122.253/16'
ipv4.gateway 192.168.22.96
"""
* Modify connection "con_ipv4" changing options "ipv4.method auto ipv4.addresses '' ipv4.gateway ''"
* Bring "up" connection "con_ipv4"
Then "192.168.22.253/24" is not visible with command "ip a s eth3"
Then "192.168.22.96" is not visible with command "ip route"
Then "192.168.122.253/24" is not visible with command "ip a s eth3"
Then "192.168.122.95" is not visible with command "ip route"
@rhbz1943153
@ver+=1.39.3
@ipv4_method_back_to_auto
Scenario: nmcli - ipv4 - addresses - delete IP and set method back to auto
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses '192.168.22.253/24, 192.168.122.253/16'
ipv4.gateway 192.168.22.96
"""
* Modify connection "con_ipv4" changing options "ipv4.method auto ipv4.addresses '' ipv4.gateway ''"
* Bring "up" connection "con_ipv4"
Then "192.168.22.253/24" is not visible with command "ip a s eth3"
Then "192.168.22.96" is not visible with command "ip route"
Then "192.168.122.253/24" is not visible with command "ip a s eth3"
Then "192.168.122.95" is not visible with command "ip route"
Then "dhcp4.dhcp_server_identifier" is visible with command "cat /run/NetworkManager/devices/$(ip link show eth3 | cut -d ':' -f 1 | head -n 1)"
And "dhcp4.dhcp_lease_time" is visible with command "cat /run/NetworkManager/devices/$(ip link show eth3 | cut -d ':' -f 1 | head -n 1)"
@ipv4_route_set_basic_route
Scenario: nmcli - ipv4 - routes - set basic route
* Add "ethernet" connection named "con_ipv4" for device "eth2" with options
"""
ipv4.method static
ipv4.addresses 192.168.1.10/24
ipv4.gateway 192.168.4.1
ipv4.routes '192.168.2.0/24 192.168.1.11 2'
ipv4.route-metric 22
"""
* Add "ethernet" connection named "con_ipv4_2" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.routes '192.168.5.0/24 192.168.3.11 1'
ipv4.route-metric 21
"""
Then "192.168.1.0/24 dev eth2\s+proto kernel\s+scope link\s+src 192.168.1.10" is visible with command "ip route" in "5" seconds
Then "192.168.2.0/24 via 192.168.1.11 dev eth2\s+proto static\s+metric" is visible with command "ip route"
Then "192.168.4.1 dev eth2\s+proto static\s+scope link\s+metric 22" is visible with command "ip route"
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10" is visible with command "ip route" in "5" seconds
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 21" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric" is visible with command "ip route"
@rhbz1373698
@ver+=1.8.0
@ver-=1.21.90
@ipv4_route_set_route_with_options
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 1024 cwnd=14 lock-mtu=true mtu=1600'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 1024\s+mtu lock 1600 cwnd 14" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
@rhbz1373698 @rhbz1714438
@ver+=1.22.0
@ver-=1.35.0
@ipv4_route_set_route_with_options
Scenario: nmcli - ipv4 - routes - set route with options
* Doc: "Configuring a static route using an nmcli command"
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 1024 cwnd=14 lock-mtu=true mtu=1600, 0.0.0.0/0 192.168.4.1 mtu=1600'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 1024\s+mtu lock 1600 cwnd 14" is visible with command "ip route"
And "default via 192.168.4.1 dev eth3 proto static metric 256 mtu 1600" is visible with command "ip r"
And "default via 192.168.4.1 dev eth3 proto static metric 256" is visible with command "ip r"
@rhbz1373698 @rhbz1714438 @rhbz1937823 @rhbz2013587
@ver+=1.36.0
@ver-=1.39.9
@ipv4_route_set_route_with_options
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 1024 cwnd=14 lock-mtu=true mtu=1600, 0.0.0.0/0 192.168.4.1 mtu=1600, 192.168.6.0/24 type=blackhole'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 1024\s+mtu lock 1600 cwnd 14" is visible with command "ip route"
And "default via 192.168.4.1 dev eth3 proto static metric 256 mtu 1600" is visible with command "ip r"
And "default via 192.168.4.1 dev eth3 proto static metric 256" is visible with command "ip r"
And "blackhole 192.168.6.0/24 proto static scope link metric 256" is visible with command "ip r"
* Modify connection "con_ipv4" changing options "ipv4.routes '192.168.7.0/24 type=prohibit, 192.168.8.0/24 type=unreachable'"
* Bring "up" connection "con_ipv4"
Then "unreachable 192.168.8.0/24 proto static scope link metric 256" is visible with command "ip r"
And "prohibit 192.168.7.0/24 proto static scope link metric 256" is visible with command "ip r"
@rhbz1373698 @rhbz1714438 @rhbz1937823 @rhbz2013587 @rhbz2090946
@ver+=1.39.10
@ipv4_route_set_route_with_options
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '
192.168.5.0/24 192.168.3.11 1024 cwnd=14 lock-mtu=true mtu=1600,
0.0.0.0/0 192.168.4.1 mtu=1600,
192.168.6.0/24 type=blackhole
'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 1024\s+mtu lock 1600 cwnd 14" is visible with command "ip route"
And "default via 192.168.4.1 dev eth3 proto static metric 256 mtu 1600" is visible with command "ip r"
And "default via 192.168.4.1 dev eth3 proto static metric 256" is visible with command "ip r"
And "blackhole 192.168.6.0/24 proto static scope link metric 256" is visible with command "ip r"
* Modify connection "con_ipv4" changing options "ipv4.routes '192.168.7.0/24 type=prohibit, 192.168.8.0/24 type=unreachable'"
* Modify connection "con_ipv4" changing options "+ipv4.routes '1.1.1.1/24 192.168.4.1 advmss=1440 quickack=1 rto_min=100'"
* Bring "up" connection "con_ipv4"
Then "unreachable 192.168.8.0/24 proto static scope link metric 256" is visible with command "ip r"
And "prohibit 192.168.7.0/24 proto static scope link metric 256" is visible with command "ip r"
And "advmss\s+1440\s+rto_min\s+100ms\s+quickack\s+1" is visible with command "ip r"
@ver+=1.41.7
@ipv4_route_set_single_route_with_weight
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 weight=5'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 256" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
@ver+=1.41.7
@ipv4_route_set_ecmp_route_with_weight
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 weight=5, 192.168.5.0/24 192.168.3.12 weight=10'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev eth3 weight 10" is visible with command "ip route"
Then "nexthop via 192.168.3.11 dev eth3 weight 5" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
@rhbz2158365
@ver+=1.41.7
@ipv4_route_set_ecmp_route_with_weight_and_drop_weight
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 weight=5, 192.168.5.0/24 192.168.3.12 weight=10'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev eth3 weight 10" is visible with command "ip route"
Then "nexthop via 192.168.3.11 dev eth3 weight 5" is visible with command "ip route"
* Execute "nmcli connection modify con_ipv4 ipv4.routes '192.168.5.0/24 192.168.3.11, 192.168.5.0/24 192.168.3.12'"
* Execute "nmcli c up con_ipv4"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.12 dev eth3\s+proto static\s+metric 256" is visible with command "ip route"
@ver+=1.41.7
@ipv4_route_set_ecmp_route_with_weight_and_modify
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 weight=5, 192.168.5.0/24 192.168.3.12 weight=10'
"""
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
Then "192.168.5.0/24\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev eth3 weight 10" is visible with command "ip route"
Then "nexthop via 192.168.3.11 dev eth3 weight 5" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
* Execute "nmcli connection modify con_ipv4 ipv4.routes '192.168.5.0/24 192.168.3.11 weight=5'"
* Execute "nmcli c up con_ipv4"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev eth3 weight 10" is not visible with command "ip route"
Then "nexthop via 192.168.3.11 dev eth3 weight 5" is not visible with command "ip route"
@ver+=1.41.7
@ver-1.45.9
@ipv4_route_set_ecmp_routes_in_two_profiles
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.12 weight=10'
"""
* Add "ethernet" connection named "con_ipv4_2" for device "eth2" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.20/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 weight=5'
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "5" seconds
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4_2" in "5" seconds
Then "192.168.5.0/24\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev eth3 weight 10" is visible with command "ip route"
Then "nexthop via 192.168.3.11 dev eth2 weight 5" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
@RHEL-1682
@ver+=1.45.9
@ipv4_route_set_ecmp_routes_in_two_profiles
Scenario: nmcli - ipv4 - routes - set route with options
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.12 weight=10'
"""
* Add "ethernet" connection named "con_ipv4_2" for device "eth2" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.20/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.11 weight=5'
"""
Then "192.168.5.0/24\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev eth3 weight 10" is visible with command "ip route"
Then "nexthop via 192.168.3.11 dev eth2 weight 5" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
And "at most" "1" lines with pattern "proto static metric 256" are visible with command "ip -4 route show to 192.168.5.0/24"
@rhbz2158394
@ver+=1.41.7
@ipv4_route_set_ecmp_routes_dummy_and_reactivate_connection
Scenario: nmcli - ipv4 - routes - set ecmp route with dummy and reactivate connection
* Add "dummy" connection named "con_ipv4" for device "dummy0" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.5.0/24 192.168.3.12 weight=10, 192.168.5.0/24 192.168.3.11 weight=5'
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "5" seconds
Then "192.168.5.0/24\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev dummy0 weight 10" is visible with command "ip route"
Then "nexthop via 192.168.3.11 dev dummy0 weight 5" is visible with command "ip route"
* Bring "down" connection "con_ipv4"
Then "192.168.5.0/24\s+proto static\s+metric 256" is not visible with command "ip route"
Then "nexthop via 192.168.3.12 dev dummy0 weight 10" is not visible with command "ip route"
Then "nexthop via 192.168.3.11 dev dummy0 weight 5" is not visible with command "ip route"
* Bring "up" connection "con_ipv4"
Then "192.168.5.0/24\s+proto static\s+metric 256" is visible with command "ip route"
Then "nexthop via 192.168.3.12 dev dummy0 weight 10" is visible with command "ip route"
Then "nexthop via 192.168.3.11 dev dummy0 weight 5" is visible with command "ip route"
@rhbz1373698
@ver+=1.8.0
@restart_if_needed
@ipv4_route_set_route_with_src_new_syntax
Scenario: nmcli - ipv4 - routes - set route with src in new syntax
* Note the number of lines with pattern "eth0" of "ip r" as value "1"
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.122.3 src=192.168.3.10'
"""
When "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
And "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
And "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
And "192.168.122.3 dev eth3\s+proto static\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
* Note the number of lines with pattern "eth0" of "ip r" as value "2"
Then Check noted values "1" and "2" are the same
And "192.168.122.3/32\s+src=192.168.3.10" is visible with command "nmcli -g ipv4.routes connection show con_ipv4"
@rhbz1373698
@ver+=1.8.0
@restart_if_needed
@ipv4_route_set_route_with_src_new_syntax_restart_persistence
Scenario: nmcli - ipv4 - routes - set route with src new syntaxt restart persistence
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.route-metric 256
ipv4.routes '192.168.122.3 src=192.168.3.10'
"""
* Stop NM
* Execute "ip addr flush dev eth3"
* Execute "rm -rf /var/run/NetworkManager"
* Start NM
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 256" is visible with command "ip route" in "20" seconds
And "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
And "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 256" is visible with command "ip route"
And "192.168.122.3 dev eth3\s+proto static\s+scope link\s+src 192.168.3.10\s+metric 256" is visible with command "ip route"
And "default" is visible with command "ip r |grep eth0"
And "192.168.122.3/32 src=192.168.3.10" is visible with command "nmcli -g ipv4.routes connection show con_ipv4"
@rhbz1302532
@restart_if_needed
@no_metric_route_connection_restart_persistence
Scenario: nmcli - ipv4 - routes - no\s+metric route connection restart persistence
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.routes '192.168.5.0/24 192.168.3.11'
"""
When "eth3:connected:con_ipv4" is visible with command "nmcli -t -f DEVICE,STATE,CONNECTION device" in "10" seconds
* Restart NM
Then "eth3:connected:con_ipv4" is visible with command "nmcli -t -f DEVICE,STATE,CONNECTION device" in "10" seconds
@rhbz1436531
@ver+=1.10
@flush_300
@ipv4_route_set_route_with_tables
Scenario: nmcli - ipv4 - routes - set route with tables
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options "ipv4.may-fail no ipv4.route-table 300"
When "connected" is visible with command "nmcli -g state,device device |grep eth3$" in "20" seconds
# This is cripppled in kernel VVV 1535977
# Then "default" is visible with command "ip r show table 300"
And "192.168.10[0-3].0\/2[2-4] dev eth3 proto kernel scope link src 192.168.10[0-3].* metric 1" is visible with command "ip r show table 300"
And "eth3" is not visible with command "ip r"
* Execute "ip route add table 300 10.20.30.0/24 via $(nmcli -g IP4.ADDRESS con show con_ipv4 |awk -F '/' '{print $1}') dev eth3"
When "10.20.30.0\/24 via 192.168.10[0-3].* dev eth3" is visible with command "ip r show table 300"
And "192.168.10[0-3].0\/2[2-4] dev eth3 proto kernel scope link src 192.168.10[0-3].* metric 1" is visible with command "ip r show table 300"
* Bring "up" connection "con_ipv4"
When "connected" is visible with command "nmcli -g state,device device |grep eth3$" in "20" seconds
Then "10.20.30.0\/24 via 192.168.10[0-3].* dev eth3" is not visible with command "ip r show table 300"
And "192.168.10[0-3].0\/2[2-4] dev eth3 proto kernel scope link src 192.168.10[0-3].* metric 1" is visible with command "ip r show table 300"
And "eth3" is not visible with command "ip r"
@rhbz1436531
@ver+=1.10
@flush_300
@ipv4_route_set_route_with_tables_reapply
Scenario: nmcli - ipv4 - routes - set route with tables reapply
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options "ipv4.may-fail no"
When "connected" is visible with command "nmcli -g state,device device |grep eth3$" in "20" seconds
# This is cripppled in kernel VVV 1535977
# Then "default" is visible with command "ip r show table 300"
And "192.168.10[0-3].0\/2[2-4] dev eth3 proto kernel scope link src 192.168.10[0-3].* metric 1" is visible with command "ip r show"
* Execute "ip route add table 300 10.20.30.0/24 via $(nmcli -g IP4.ADDRESS con show con_ipv4 |awk -F '/' '{print $1}') dev eth3"
When "10.20.30.0\/24 via 192.168.10[0-3].* dev eth3" is visible with command "ip r show table 300"
And "192.168.10[0-3].0\/2[2-4] dev eth3 proto kernel scope link src 192.168.10[0-3].* metric 1" is visible with command "ip r show"
* Execute "nmcli device reapply eth3"
When "connected" is visible with command "nmcli -g state,device device |grep eth3$" in "20" seconds
Then "10.20.30.0\/24 via 192.168.10[0-3].* dev eth3" is visible with command "ip r show table 300"
And "192.168.10[0-3].0\/2[2-4] dev eth3 proto kernel scope link src 192.168.10[0-3].* metric 1" is visible with command "ip r show"
@rhbz1907661
@ver+=1.31
@ver+=1.30.3
@rhelver+=8
@check_local_routes
Scenario: nmcli - ipv4 - test handling of local routes
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method manual
ipv4.address '192.0.2.1/24,192.0.2.2/24'
ipv6.method manual
ipv6.addresses '1:2:3:4:5::1/64,1:2:3:4:5::2/64'
"""
When "eth3\:ethernet\:connected\:con_ipv4" is visible with command "nmcli -t device" in "5" seconds
When "192.0.2.1" is visible with command "ip a s eth3"
# Obsolete by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=94c821c74bf5fe0c25e09df5334a16f98608db90
# When "broadcast 192.0.2.0 dev eth3 table local proto kernel scope link src 192.0.2.1" is visible with command "ip r show table all"
When "192.0.2.0/24 dev eth3 proto kernel scope link src 192.0.2.1 metric 1" is visible with command "ip r show table all"
When "local 192.0.2.1 dev eth3 table local proto kernel scope host src 192.0.2.1" is visible with command "ip r show table all"
When "local 192.0.2.2 dev eth3 table local proto kernel scope host src 192.0.2.1" is visible with command "ip r show table all"
When "broadcast 192.0.2.255 dev eth3 table local proto kernel scope link src 192.0.2.1" is visible with command "ip r show table all"
When "local 1:2:3:4:5::1 dev eth3 table local proto kernel metric 0 pref medium" is visible with command "ip -6 route show table all" in "5" seconds
When "local 1:2:3:4:5::2 dev eth3 table local proto kernel metric 0 pref medium" is visible with command "ip -6 route show table all" in "5" seconds
* Execute "nmcli device modify eth3 ipv4.address 192.0.2.2/24"
When "192.0.2.1" is not visible with command "ip route show table all"
When "local 192.0.2.2 dev eth3 table local proto kernel scope host src 192.0.2.2" is visible with command "ip route show table all"
When "local 1:2:3:4:5::1 dev eth3 table local proto kernel metric 0 pref medium" is visible with command "ip -6 route show table all" in "5" seconds
When "local 1:2:3:4:5::2 dev eth3 table local proto kernel metric 0 pref medium" is visible with command "ip -6 route show table all" in "5" seconds
* Execute "nmcli device modify eth3 ipv6.address 1:2:3:4:5::2/64"
When "192.0.2.1" is not visible with command "ip route show table all"
When "local 192.0.2.2 dev eth3 table local proto kernel scope host src 192.0.2.2" is visible with command "ip route show table all"
When "1:2:3:4:5::1" is not visible with command "ip -6 route show table all"
When "local 1:2:3:4:5::2 dev eth3 table local proto kernel metric 0 pref medium" is visible with command "ip -6 route show table all" in "5" seconds
@rhbz1503769
@ver+=1.10
@ipv4_restore_default_route_externally
Scenario: nmcli - ipv4 - routes - restore externally
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options "ipv4.may-fail no"
When "connected" is visible with command "nmcli -g state,device device |grep eth3$" in "20" seconds
And "default" is visible with command "ip r |grep eth3"
* Execute "ip route delete default dev eth3"
When "default" is not visible with command "ip r |grep eth3"
* Execute "ip route add default via 192.168.100.1 metric 1"
Then "default" is visible with command "ip r |grep eth3"
@rhbz1164441
@ver+=1.10.2
@ipv4_route_remove_basic_route
Scenario: nmcli - ipv4 - routes - remove basic route
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.may-fail no
ipv4.method static
ipv4.addresses 192.168.3.10/24
ipv4.gateway 192.168.4.1
ipv4.routes '192.168.5.0/24 192.168.3.11 200'
"""
* Add "ethernet" connection named "con_ipv42" for device "eth2" with options
"""
ipv4.may-fail no
ipv4.method static
ipv4.addresses 192.168.1.10/24
ipv4.gateway 192.168.4.1
ipv4.routes '192.168.2.0/24 192.168.1.11 300'
"""
* Modify connection "con_ipv4" changing options "ipv4.routes ''"
* Modify connection "con_ipv4" changing options "ipv4.routes ''"
* Bring "up" connection "con_ipv4"
* Bring "up" connection "con_ipv42"
Then "default via 192.168.4.1 dev eth3\s+proto static\s+metric 1" is visible with command "ip route" in "5" seconds
Then "default via 192.168.4.1 dev eth2\s+proto static\s+metric 1" is visible with command "ip route" in "5" seconds
Then "192.168.1.0/24 dev eth2\s+proto kernel\s+scope link\s+src 192.168.1.10" is visible with command "ip route"
Then "192.168.2.0/24 via 192.168.1.11 dev eth2\s+proto static\s+metric 200" is not visible with command "ip route"
Then "192.168.3.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.3.10" is visible with command "ip route"
Then "192.168.4.1 dev eth3\s+proto static\s+scope link\s+metric 1" is visible with command "ip route"
Then "192.168.4.1 dev eth2\s+proto static\s+scope link\s+metric 1" is visible with command "ip route"
Then "192.168.5.0/24 via 192.168.3.11 dev eth3\s+proto static\s+metric 300 " is not visible with command "ip route"
@ipv4_route_set_device_route
Scenario: nmcli - ipv4 - routes - set device route
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.may-fail no
ipv4.method static
ipv4.addresses 192.168.122.2/24
ipv4.gateway 192.168.122.1
ipv4.routes '192.168.1.0/24 0.0.0.0, 192.168.2.0/24 192.168.122.5'
"""
Then "^connected" is visible with command "nmcli -t -f STATE,DEVICE device |grep eth3" in "5" seconds
Then "default via 192.168.122.1 dev eth3\s+proto static\s+metric" is visible with command "ip route"
Then "192.168.1.0/24 dev eth3\s+proto static\s+scope link\s+metric" is visible with command "ip route"
Then "192.168.2.0/24 via 192.168.122.5 dev eth3\s+proto static\s+metric" is visible with command "ip route"
Then "192.168.122.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.122.2" is visible with command "ip route"
@rhbz1439376
@ver+=1.8.0
@ipv4_host_destination_route
Scenario: nmcli - ipv4 - routes - host destination
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ip4 192.168.122.123/24
ipv4.routes '10.20.30.10/24 192.168.122.2'
"""
Then "^connected" is visible with command "nmcli -t -f STATE,DEVICE device |grep eth3" in "5" seconds
@preserve_route_to_generic_device
Scenario: nmcli - ipv4 - routes - preserve generic device route
* Create "dummy" device named "dummy0"
* Execute "ip link set dev dummy0 up"
* Execute "ip r add default via 0.0.0.0 dev dummy0"
* Execute "ip a add 1.2.3.4/24 dev dummy0"
Then "default dev dummy0" is visible with command "ip route"
Then "1.2.3.0/24 dev dummy0\s+proto kernel\s+scope link\s+src 1.2.3.4" is visible with command "ip route"
Then "IP4.ADDRESS\[1\]:\s+1.2.3.4/24" is visible with command "nmcli dev show dummy0" in "10" seconds
Then "IP4.GATEWAY:\s+0.0.0.0" is visible with command "nmcli dev show dummy0"
@ipv4_route_set_invalid_non_IP_route
Scenario: nmcli - ipv4 - routes - set invalid route - non IP
* Add "ethernet" connection named "con_ipv4" for device "eth3"
* Open editor for connection "con_ipv4"
* Submit "set ipv4.method static" in editor
* Submit "set ipv4.addresses 192.168.122.2/24" in editor
* Submit "set ipv4.routes 255.255.255.256" in editor
Then Error type "failed to set 'routes' property:" while saving in editor
@ipv4_route_set_invalid_missing_gw_route
Scenario: nmcli - ipv4 - routes - set invalid route - missing gw
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.122.2/24
ipv4.gateway 192.168.122.1
ipv4.routes 192.168.1.0/24
"""
Then "default via 192.168.122.1 dev eth3\s+proto static\s+metric" is visible with command "ip route" in "5" seconds
Then "192.168.1.0/24 dev eth3\s+proto static\s+scope link\s+metric" is visible with command "ip route"
Then "192.168.122.0/24 dev eth3\s+proto kernel\s+scope link\s+src 192.168.122.2" is visible with command "ip route"
@ver+=1.4.0
@ver-=1.11.2
@ipv4_routes_not_reachable
Scenario: nmcli - ipv4 - routes - set unreachable route
* Add "ethernet" connection named "con_ipv4" for device "eth3"
* Open editor for connection "con_ipv4"
* Submit "set ipv4.method static" in editor
* Submit "set ipv4.addresses 192.168.122.2/24" in editor
* Submit "set ipv4.gateway 192.168.122.1" in editor
* Submit "set ipv4.routes 192.168.1.0/24 192.168.3.11 1" in editor
* Submit "set ipv6.method ignore" in editor
* Save in editor
* Quit editor
* Bring "up" connection "con_ipv4" ignoring error
Then "\(disconnected\)" is visible with command "nmcli device show eth3" in "5" seconds
@ver+=1.11.3
@ipv4_routes_not_reachable
Scenario: nmcli - ipv4 - routes - set unreachable route
# Since version 1.11.3 NM automatically adds a device route to the
# route gateway when it is not directly reachable
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.122.2/24
ipv4.gateway 192.168.122.1
ipv4.routes '192.168.1.0/24 192.168.3.11 1'
"""
Then "\(connected\)" is visible with command "nmcli device show eth3" in "5" seconds
Then "192.168.3.11\s+dev eth3\s+proto static" is visible with command "ip r"
@ipv4_dns_manual
Scenario: nmcli - ipv4 - dns - method static + IP + dns
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.122.253/24
ipv4.gateway 192.168.122.1
ipv4.dns '8.8.8.8, 8.8.4.4'
"""
Then Nameserver "8.8.8.8" is set in "10" seconds
Then Nameserver "8.8.4.4" is set
Then Nameserver "192.168.100.1" is not set
@ipv4_dns_manual_when_method_auto
Scenario: nmcli - ipv4 - dns - method auto + dns
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options "ipv4.dns '8.8.8.8, 8.8.4.4'"
Then Nameserver "8.8.8.8" is set in "10" seconds
Then Nameserver "8.8.4.4" is set
Then Nameserver "192.168.100.1" is set in "5" seconds
@ipv4_dns_manual_when_ignore_auto_dns
Scenario: nmcli - ipv4 - dns - method auto + dns + ignore automaticaly obtained
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.method static
ipv4.addresses 192.168.122.253/24
ipv4.gateway 192.168.122.1
ipv4.dns '8.8.8.8, 8.8.4.4'
ipv4.ignore-auto-dns yes
"""
Then Nameserver "8.8.8.8" is set in "10" seconds
Then Nameserver "8.8.4.4" is set
Then Nameserver "192.168.100.1" is not set
@rhbz1405431
@ver+=1.6.0
@not_with_systemd_resolved
@restart_if_needed @delete_testeth0
@ipv4_ignore_resolveconf_with_ignore_auto_dns
Scenario: nmcli - ipv4 - preserve resolveconf if ignore_auto_dns
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.ignore-auto-dns yes
ipv6.ignore-auto-dns yes
"""
* Bring "down" connection "con_ipv4"
* Stop NM
* Execute "echo 'search boston.com' > /etc/resolv.conf"
* Execute "echo 'nameserver 1.2.3.4' >> /etc/resolv.conf"
* Start NM
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
* Restart NM
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
* Restart NM
Then Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
@rhbz1426748
@ver+=1.8.0
@not_with_systemd_resolved
@restart_if_needed @delete_testeth0
@ipv4_ignore_resolveconf_with_ignore_auto_dns_var1
Scenario: NM - ipv4 - preserve resolveconf if ignore_auto_dns with NM service up
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.ignore-auto-dns yes
ipv6.ignore-auto-dns yes
"""
* Bring "down" connection "con_ipv4"
* Execute "echo 'search boston.com' > /etc/resolv.conf"
* Execute "echo 'nameserver 1.2.3.4' >> /etc/resolv.conf"
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
* Restart NM
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
* Restart NM
Then Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
@rhbz1344303
@ver+=1.8.0
@rhelver-=8
@not_with_systemd_resolved
@restore_hostname @delete_testeth0
@ipv4_ignore_resolveconf_with_ignore_auto_dns_var2
Scenario: NM - ipv4 - preserve resolveconf when hostnamectl is called and ignore_auto_dns set
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.ignore-auto-dns yes
ipv6.ignore-auto-dns yes
"""
* Bring "down" connection "con_ipv4"
* Execute "echo 'search boston.com' > /etc/resolv.conf"
* Execute "echo 'nameserver 1.2.3.4' >> /etc/resolv.conf"
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
* Execute "hostnamectl set-hostname braunberg"
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
* Execute "hostnamectl set-hostname --transient BraunBerg"
Then Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
@rhbz1422610
@ver+=1.8.0
@not_with_systemd_resolved
@restore_hostname @eth3_disconnect @delete_testeth0
@ipv4_ignore_resolveconf_with_ignore_auto_dns_var3
Scenario: NM - ipv4 - preserve resolveconf when hostnamectl is called and ignore_auto_dns set
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options
"""
ipv4.ignore-auto-dns yes
ipv6.ignore-auto-dns yes
"""
* Bring "down" connection "con_ipv4"
* Execute "echo 'search boston.com' > /etc/resolv.conf"
* Execute "echo 'nameserver 1.2.3.4' >> /etc/resolv.conf"
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
* Execute "hostnamectl set-hostname --static ''"
* Execute "hostnamectl set-hostname --transient BraunBerg"
When Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
And "BraunBerg" is visible with command "hostnamectl --transient" in "5" seconds
* Execute "ip add add 1.2.3.1/24 dev eth3"
And Domain "boston.com" is set
And Nameserver "1.2.3.4" is set
@rhbz1423490
@ver+=1.8.0
@rhelver-=7 @rhel_pkg
@not_with_systemd_resolved
@restore_resolvconf @restart_if_needed
@ipv4_dns_resolvconf_rhel7_default
Scenario: nmcli - ipv4 - dns - rhel7 default
When "activated" is visible with command "nmcli -g GENERAL.STATE con show testeth0" in "45" seconds
* Execute "cp /etc/resolv.conf /tmp/resolv_orig.conf"
* Execute "mv -f /etc/resolv.conf /tmp/resolv.conf"
* Execute "ln -s /tmp/resolv.conf /etc/resolv.conf"
* Add "ethernet" connection named "con_ipv4" for device "eth3" with options "ipv4.dns 8.8.8.8"
* Bring "up" connection "con_ipv4"
Then Nameserver "8.8.8.8" is set in "20" seconds
And "nameserver 8.8.8.8" is visible with command "cat /var/run/NetworkManager/resolv.conf"
And "are identical" is not visible with command "diff -s /tmp/resolv.conf /tmp/resolv_orig.conf"
And "/etc/resolv.conf -> /tmp/resolv.conf" is visible with command "ls -all /etc/resolv.conf"
@rhbz1423490
@ver+=1.8.0
@not_with_systemd_resolved
@restore_resolvconf @restart_if_needed
@ipv4_dns_resolvconf_symlinked
Scenario: nmcli - ipv4 - dns - symlink
* Add "ethernet" connection named "con_ipv4" for device "eth0" with options
"""
ipv4.may-fail no
"""
* Bring "up" connection "con_ipv4"
* Create NM config file "95-nmci-resolv.conf" with content
"""
[main]
rc-manager=symlink
"""
* Restart NM
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "45" seconds
When Nameserver "nameserver" is set in "0" seconds
* Execute "cp /etc/resolv.conf /tmp/resolv_orig.conf"
* Execute "mv -f /etc/resolv.conf /tmp/resolv.conf"
* Execute "ln -s /tmp/resolv.conf /etc/resolv.conf"
* Add "ethernet" connection named "con_ipv42" for device "eth3" with options
"""
ipv4.dns 8.8.8.8
"""
When "activated" is visible with command "nmcli -g GENERAL.STATE con show con_ipv4" in "45" seconds
Then "nameserver 8.8.8.8" is visible with command "cat /var/run/NetworkManager/resolv.conf"
And "nameserver 8.8.8.8" is not visible with command "cat /etc/resolv.conf"
And "are identical" is visible with command "diff -s /tmp/resolv.conf /tmp/resolv_orig.conf"
And "/etc/resolv.conf -> /tmp/resolv.conf" is visible with command "ls -all /etc/resolv.conf"
@rhbz1423490
@ver+=1.8.0
@rhel_pkg @not_with_systemd_resolved
@restore_resolvconf @restart_if_needed
@ipv4_dns_resolvconf_file
Scenario: nmcli - ipv4 - dns - file
* Add "ethernet" connection named "con_ipv4" for device "eth0" with options
"""
ipv4.may-fail no
"""
* Bring "up" connection "con_ipv4"
* Create NM config file "95-nmci-resolv.conf" with content
"""
[main]
rc-manager=file