netdev - Network device autoconfiguration

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <bd8484914903fecf95d193d4ac9f9295@chewa.net>
Date:	Mon, 31 Aug 2009 15:19:54 +0200
From:	Rémi Denis-Courmont <remi@...lab.net>
To:	netdev@...r.kernel.org
Subject: Network device autoconfiguration

   Hello,

The kernel will automatically configure the loopback device, especially,
add 127.0.0.1 and ::1 address. This is detected with the IFF_LOOPBACK flag.
In *some* cases, it would be statically determine the Phonet address of a
device, but I wonder how to pass the information from the net_device driver
to the stack... Would a device ioctl() be appropriate? Or is the whole
thing just a bad idea? Or something else?

-- 
Rémi Denis-Courmont

--
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