>> What I really meant with my suggestion was that if fred encounters two >> or >> more, accrording to whatever filtering scheme used, valid IP addresses >> then >> why can't it just have a check to see if one of those addresses are the >> one >> currently in use and in that case continue using it. It is simply a >> matter >> of adding another, possibly very simple, check before making the final >> decision (which very well still might be to use the last encountered >> valid >> IP) of which of the valid addresses to use. > > 0.0.0.0 IS NOT A VALID IP ADDRESS.
Uh, the IP address of that interface was like 5.0.0.4 wasn't it? Which is a valid IP address. It wasn't 0.0.0.0, where did you get that idea from? The point was, Fred picked up a (valid) IP address on the WRONG INTERFACE. It started using a different interface from the one it used previously, simply because the guy plugged in his bluetooth-enabled PDA into a USB socket. What fred needs is a way to specify which INTERFACE to bind to. (Not which IP address to bind to). That would avoid the problem entirely. As for how to actually do this in Fred's architecture... well, that's for the java devs to figure out I suppose. d _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
