Re: NSE suggestion

[kx <kxmail () gmail com>]

David,
  Could this patch please get added to the trunk?

http://seclists.org/nmap-dev/2009/q2/att-196/nexthop.patch
http://seclists.org/nmap-dev/2009/q2/810

Would documentation like this work?

  <varlistentry>
            <term><option>host.mac_next_hop</option>
              </term>
            <listitem>
              <para>The next hop MAC address, which was used to route to the host.
              </para>
            </listitem>
          </varlistentry>

On Fri, Apr 24, 2009 at 9:09 PM, Michael Pattrick
<mpattrick () rhinovirus org> wrote:
> Indeed, attached is a patch that creates a new member variable named
> mac_next_hop. I had considered setting mac_addr as the next hop
> instead of nil, but thought better then that as it goes against the
> documentations.
>
> -Michael
>
> On Fri, Apr 24, 2009 at 8:47 PM, Fyodor <fyodor () insecure org> wrote:
> > On Thu, Apr 23, 2009 at 11:57:48AM -0400, Michael Pattrick wrote:
> > > Hello list,
> > >
> > > I find it kind of odd that NSE offers functions to send raw ethernet
> > > frames but no good way to get the next hop mac address; or am I
> > > missing something? I suggest that another LUA variable is added under
> > > the 'nmap' class which reveals the next hop MAC address for the
> > > current host.
> >
> > Good idea!  Do you want to write a patch?  Unless someone suggests a
> > better way, it sounds like it is worth applying.  I would like to see
> > the raw packet sending and sniffing NSE functionality used more, as a
> > lot of fun can be had with that!
> >
> > Cheers,
> > -F
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/