netdev - how to determine IP address within network device driver?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <e14fe6280704262335l754fcc56s115e43a220ed35c4@mail.gmail.com>
Date:	Fri, 27 Apr 2007 08:35:08 +0200
From:	"Nic Gyrovague" <nic.gyrovague@...il.com>
To:	netdev@...r.kernel.org
Subject: how to determine IP address within network device driver?

(apologies for the repost, I thought people may have missed this
question since it was not phrased as such)

I have a hw network device that can benefit from knowing what its
associated IP addresses (if any) are... Is there a "correct" way to
determine the IP address(es) from within the driver code?

Its obviously possible to snoop into ARP
and IP traffic to try to "guess", but this is not always 100% reliable
(e.g. with bridging) and also only gives you the IP address once packets
have started flowing...

In other words, if userspace sets/changes or adds (e.g. IP alias) an
IP address to the device (e.g. "ifconfig eth0  192.168.1.5"), I'd like
to somehow be informed of that within my driver, or failing that, be
able to somehow poll a kernel structure or API to determine said
information...

-- 
gyrovague
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html