Also, does Fred check for reserved address ranges? It seems this would
be able to rule out most publicly inaccessible interfaces.
Scott
On Tue, May 27, 2003 at 10:32:25PM +0200, Niklas Bergh wrote:
> This is from the fascinating world of Microsoft..
>
> I was very surprised to notice that after the last restart fred was bound to
> this to me previously unknown interface on my computer:
>
> Ethernet adapter Local Area Connection 3:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Microsoft TV/Video Connection
> Physical Address. . . . . . . . . : 00-00-00-00-00-00
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Autoconfiguration IP Address. . . : 5.0.1.0
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
>
> Some research uncovered that this strange new interface would be the camera
> in my new Sony Ericsson T610 phone connected to my computer via bluetooth...
> Luckily enough it would seem that many nodes around the network already had
> a valid noderef for my node so they just kept the requests coming :)
>
> Would it be too much to ask that fred, when it scans through all of the
> computers available interfaces, at least tries to stay with the interface
> that can be found in the 'node' file if it still is present in the system
> (even if a new interface or two have appeared).
>
> /N
>
>
>
> _______________________________________________
> devl mailing list
> devl at freenetproject.org
> http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
>
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20030527/658315ea/attachment.pgp>
