Re: please respond to this?

re-adding [email protected]

Hey,
so, this is weird indeed, but you didn't give us enough information to
really troubleshoot this.

What OS are you running, and what version? What's the make and model of the
WiFi card you're using? Is it USB or integrated (like on a laptop)?
And, just to confirm, are you using the same computer both at home and in
the library?

BTW the library cannot "see" nmap before it starts (at least on your
computer) so what could be happening is that your OS does not recognize
your wifi card when you're in the library. But as to why, I don't know.

BTW, I tried looking for the other two messages you sent in the list
archives (https://seclists.org/nmap-dev/) to see if you already gave the
info, but I can't find them. If you already sent the info above just point
me at those please :)

On Sat, Mar 16, 2019 at 7:36 PM Mike . <[email protected]> wrote:

> ty for responding. so it gets even weirder. this is all happening at a
> public library that offers free wifi. i know what ethernt is, i used it for
> 10 years. so someone explain this if you can because i am BAFFLED! i have
> no connection at my home for the time being so i come here to the library.
> i am using a WIRELESS CARD/CONNECTION. at home i have NO CONNECTION because
> the wifi in the apt complex is locked down BUT i can still OPEN NMAP! and
> it uses "eth0" when i do!? but at the library it will not open eth0?????
> that is all it ever sees. that and the loopbacks. turning NPCAP on or off
> doesnt help mattes. now i know this library locks down their router quite
> well but how in the world could they see nmap before it is even fired
> up????? thought i knew networking but this has be stumped! the packet
> traffic at the lib shows me calling and finding a DHCP and then getting the
> proper config and going foward with a connection like any DHCP would. but
> nmap does not work?????????????? ty
>
> ------------------------------
> *From:* Claudio M <[email protected]>
> *Sent:* Saturday, March 16, 2019 11:46 AM
> *To:* Mike .
> *Cc:* nmap-group
> *Subject:* Re: please respond to this?
>
> eth0 is, normally, the identifier of an ethernet card (the one with the
> cable); wireless interfaces start with "w".
>
> To see all the interfaces available on your system use either "ifconfig"
> or "ip link show", then use that in nmap.
>
> FYI newer Linux versions are using a different way of identifying cards,
> so your card could be called something like wlp2s0.
> Read
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> for more info.
>
> On Fri, Mar 15, 2019 at 9:51 PM Mike . <[email protected]> wrote:
>
> this is my 3rd message that will prob be ignored again. anyway, does nmap
> just not work on wireless cards? went down to my local lib, plugged in and
> got this after firing it up
>
> Starting Nmap 7.70 ( https://nmap.org ) at 2019-03-15 15:49 Central
> Daylight Tim
> e
> Initiating Ping Scan at 15:49
> dnet: Failed to open device eth0
> QUITTING!
>
> odd thing though. i am not using ETH0! that is my ethernet that is
> DISABLED! so does it just not support my standard Intel  WIRELESS card?
> wlan? wont even see it listed with --iflist. what gives
> _______________________________________________
> Sent through the dev mailing list
> https://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/
>
>

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/