RIP Injection: -i 0.0.0.0 option results in random RIP Address

[octknot]

I have builded nemesis 1.7 release.

Run the following command:

$ nemesis rip -v -d wlan0 -c 1 -V 1 -a 0 -R 0 -i  0.0.0.0 -k 0.0.0.0 -h 0.0.0.0 -m 16 -S 10.10.10.1                                                                                     
                                                                                                                                       
RIP Packet Injection -=- The NEMESIS Project v1.7                                                                                      

               [MAC] 20:7C:8F:11:39:13 > FF:FF:FF:FF:FF:FF
     [Ethernet type] IP (0x0800)

                [IP] 10.10.10.1 > 224.0.0.9
             [IP ID] 39436
          [IP Proto] UDP (17)
            [IP TTL] 1
            [IP TOS] 0x10
    [IP Frag offset] 0x0000
     [IP Frag flags]
         [UDP Ports] 520 > 520

       [RIP Command] Request (1)
       [RIP Version] 1
[RIP Routing domain] 0
[RIP Address family] Unknown (0)
     [RIP Route tag] 0
       [RIP Address] 117.64.14.67
  [RIP Network mask] 0.0.0.0
      [RIP Next hop] 0.0.0.0
        [RIP Metric] 16

Wrote 66 byte RIP packet through linktype DLT_EN10MB.

The [RIP Address] should have been set by -i 0.0.0.0 option, but as showed above, it is randomized.

If setting -i with a non 0.0.0.0 IP, everything is fine.

The all-zero IP address is useful for the purpose of RIP testing, so it might be better to leave the choice to the users.

[troglobit]

Awesome find, thank you for taking the time to report this! 😃