"zmap: could not detect default gateway address for 0." on VPS with strange interfaces

[sanderjo]

(git version of zmap, which BTW reports "zmap 1.0.0".)

Summary:
On a VPS, with a non-normal ifconfig, I get strange results from zmap which I cannot solve with -i nor -G

Long story:

On a VPS, I get:

root@superdoos:# zmap -p 80 -N 10 -B 1M -o -
Aug 20 18:22:20.820 [INFO] zmap: started
Aug 20 18:22:20.899 [FATAL] zmap: could not detect default gateway address for 0. Try setting default gateway mac address (-G).
root@superdoos:#

My ifconfig shows:

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:5.2.2.1 P-t-P:5.2.2.3 Bcast:0.0.0.0 Mask:255.255.255.255

(public IPv4 address a bit altered)

Specifying "-i venet0:0" or "-i venet0:0" results in the same problem.

Additionally specifying -G results in another error message, a high ETA and no useful ports found:

zmap -p 80 -N 10 -B 1M -o - -i venet0 -G 00:00:00:00:00:00

Aug 20 18:27:12.031 [INFO] zmap: started
SIOCGIFADDR: Invalid argument
0:01 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: -nan%
0:02 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: -nan%
0:03 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: -nan%
0:04 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: -nan%
0:05 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: -nan%
0:06 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: -nan%
0:07 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: -nan%

[jhalderm]

I don't think we can support venet, since it apparently doesn't work with libpcap:
https://openvz.org/Virtual_network_device

[sanderjo]

FWIW: "tcpdump" does work correctly on this VPS; it says "listening on venet0" and then reports stuff on the line:

tcpdump

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
19:09:40.416074 IP6 2607:ff2xxxxx.ssh > 2a00:cd8:4dxxxx14: Flags [P.], seq 4089851818:4089852026, ack 3083302732, win 228, options [nop,nop,TS val 3279915382 ecr 3414342], length 208

[ewust]

Can you test with the latest master commit, using the new --vpn flag? Probably will need -i venet0 --vpn. I'm not sure if venet expects some other hardware header or IP packets, but if it expects IP packets, then --vpn should work.

[sanderjo]

I did a git pull, make clean, make (no make install). The --vpn parameter gives the result below. My interpretation: 1) no errors, but 2) no results at all

root@superdoos:/git/zmap/src# ./zmap --version
zmap 1.0.0
root@superdoos:/git/zmap/src#
root@superdoos:/git/zmap/src# ./zmap -p 80 -N 10 -B 1M -o - -i venet0
Sep 01 12:30:37.909 [INFO] zmap: started
Sep 01 12:30:37.909 [FATAL] zmap: could not detect default gateway address for 0. Try setting default gateway mac address (-G).
root@superdoos:/git/zmap/src#
root@superdoos:/git/zmap/src#
root@superdoos:/git/zmap/src# ./zmap -p 80 -N 10 -B 1M -o - -i venet0 --vpn
Sep 01 12:30:42.566 [INFO] zmap: started
0:00 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
SIOCGIFADDR: Invalid argument
0:01 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:02 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:03 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:04 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:05 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:06 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:07 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:08 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:09 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:10 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:11 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:12 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:13 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:14 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:15 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%

root@superdoos:~/git/zmap/src# ./zmap -p 80 -N 10 -B 1M -o - -i venet0:0 --vpn
Sep 01 12:35:13.693 [INFO] zmap: started
0:00 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
SIOCGIFADDR: Invalid argument
0:01 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:02 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:03 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:04 0%; send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:05 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:06 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:07 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:08 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:09 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:10 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:11 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:12 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%
0:13 0% (68 years left); send: 0 0 p/s (0 p/s avg); recv: 0 0 p/s (0 p/s avg); drops: 0 p/s (0 p/s avg); hits: 0.00%

FWIW: the old, installed zmap does not know the "--vpn", so that is a proof I'm using the new zmap.

root@superdoos:/git/zmap/src# zmap -p 80 -N 10 -B 1M -o - -i venet0 --vpn
zmap: unrecognized option '--vpn'
root@superdoos:/git/zmap/src#

[andrewsmhay]

I also just tested this and had the same issue.

nmap works but you have to specify the following (perhaps it'll help):

nmap -e venet0:0 -Pn -S

The provider even gave me the upstream GW MAC and the issue persists.

I am happy to provide access to the server for testing, if required.

[andrewsmhay]

Same problem in masscan

[Esya]

Does not work here, would love a solution (Inside an OpenVZ here, with venet as well)

[hexlax]

Has anyone been able to work around this bug in the interim? Is there a way to request a different interface type from the VPS provider perhaps?

[BarryReid]

I have the same problem with the venet interface. Any fix for this yet? or anyone find a work around?

[snapo]

using openvz for this would be great....

[hexlax]

I switched VPS providers to one that uses KVM instead..

On Tuesday, February 18, 2014, snapo notifications@github.com wrote:

using openvz for this would be great....

Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-35371112
.

Please excuse brevity as this was sent from my mobile device.

[snapo]

hexlax could you tell me the vps provider that allows zmap?

[hexlax]

I really like Digital Ocean. In the event you receive an abuse complaint
for your scans, be sure to add that range to your block list..

On Tuesday, February 18, 2014, snapo notifications@github.com wrote:

hexlax could you tell me the vps provider that allows zmap?

Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-35388788
.

Please excuse brevity as this was sent from my mobile device.

[BarryReid]

@hexlax have you never got a complaint from Digital Ocean for DDOS'ing or anything? What speed to you scan at?

[hexlax]

@barry - I have received abuse complaints, at which time I am proactive in
adding those to my blocklists. I also reached out to Digital Ocean prior to
scanning to inform them I am researcher and to let me know if there are any
problems related to my scans..

On Tue, Feb 18, 2014 at 5:45 PM, Barry Reid notifications@github.comwrote:

@hexlax https://github.com/hexlax have you never got a complaint from
Digital Ocean for DDOS'ing or anything? What speed to you scan at?

Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-35444740
.

[BarryReid]

@hexlax could you please drop me an email @ barryjreid@gmail.com would like to grab some info from you and maybe get hold of that blocklist you use, that way I start off on a good note :)

[barry]

I don't know why I am being CC'ed; I have no connection to zmap. Do you
have the correct "Barry"?

On 18 February 2014 22:52, hexlax notifications@github.com wrote:

@barry - I have received abuse complaints, at which time I am proactive in
adding those to my blocklists. I also reached out to Digital Ocean prior to
scanning to inform them I am researcher and to let me know if there are any
problems related to my scans..

On Tue, Feb 18, 2014 at 5:45 PM, Barry Reid <notifications@github.com

wrote:

@hexlax https://github.com/hexlax have you never got a complaint from
Digital Ocean for DDOS'ing or anything? What speed to you scan at?

Reply to this email directly or view it on GitHub<
https://github.com/zmap/zmap/issues/35#issuecomment-35444740>
.

Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-35445392
.

[abbypan]

zmap 1.2.1 on openvz vps , add --vpn is still fail.

[zakird]

Does it allow sending an IP packet? Given that none of us use this, we're good to need more information from you to work on this at all. Can you provide tcpdump or similar?

[LaserGunJesus]

Yeah I cannot scan either. Same issue. Can Nmap achieve the same things as zmap?

[brammittendorff]

Same issue here, masscan to. I juse evilscan now: https://github.com/eviltik/evilscan

[roeea2]

So even though this issue as closed and I remember @zakird said in another post that this issue will not be fixed.
I found a way to baypass it and my solution is to install a docker on the VPS which is using a none kvm method.

It worked from within the docker (don;t use --vpn)