From: Anshuman Singh Rawat <asr245@nyu.edu>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: getting MAC addresses (was: Re: opening a port without root permission)
Date: Thu, 01 Jul 2004 01:16:09 -0400 [thread overview]
Message-ID: <18716fd18765db.18765db18716fd@homemail.nyu.edu> (raw)
> Others already suggested "sudo" as the way to deal with the arping
> problem.
> But... are you really able to use arping to get MAC addresses of
> hosts not
> on the Ethernet local to the host you arping from? (I assume that
> is what
> you mean by "in a different subnet".)
>
> I was curious about this, so I tested it here. With the current
> Debian-Sid
> version of arping, arping'ing the IP address of a host on my DMZ
> from my
> LAN returns the MAC address of my router (since it does proxy
> arp), NOT the
> MAC address of the target host's own interface. If I arping the
> actual MAC
> address of the DMZ host (as shown in the arp table of my router),
> I get no
> response.
>
> Am I missing something? I ask because this problem -- how to get
> the MAC
> address of a non-local host -- comes up again and again, and I
> always
> believed there was no solution to it (excluding ones that involve
> running
> some application on the target host). Am I mistaken?
Sorry. My mistake. It cant retrieve the MAC address of a machine on a different subnet.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2004-07-01 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 5:16 Anshuman Singh Rawat [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-30 1:20 opening a port without root permission Anshuman Singh Rawat
2004-06-30 16:39 ` getting MAC addresses (was: Re: opening a port without root permission) Ray Olszewski
2004-06-30 21:17 ` Eric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18716fd18765db.18765db18716fd@homemail.nyu.edu \
--to=asr245@nyu.edu \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox