Hi Marcel,

On Thu, Jul 28, 2011 at 02:06:19PM +0200, Marcel Holtmann wrote:
> > I have been running this patch on my meego netbook and it has been very 
> > useful. Now I get the same IP address back almost always which makes it 
> > easy to ssh to the device and I do not have to constantly check my IP 
> > address in netbook (of course this is perhaps a useful use case for me 
> > only). The DHCP REQUESTED IP address option is just a hint to the server 
> > anyway.
> 
> while this might be nice an useful, it is not something that I am
> shooting for actually. You would have Zeroconf/Avahi for finding the IP
> address of your SSH server.
> 
> If we leave one network, then I do not expect to get back with the same
> address. 
Jukka's patch saves the last DHCP address per service, so when you switch
between services you will not send your previous service DHCP address to a
different network.

> Especially since we are not even taken the lease time into
> account, I consider this a security issue. 
When leaving a network, we usually send a DHCP release in which case the
lease time becomes irrelevant.

> We are sending our previous
> IP in clear text over a WiFi network. Not really a good idea from my
> point of view.
Why would it be in clear text ?


> > > When you leave the current network to switch to a different one or when
> > > you shutdown your laptop, why bother with trying to keep the same
> > > address. I rather not actually.
> > 
> > Hmm, I would rather do actually :)
> > 
> > There is some more discussion here
> > https://bugs.meego.com/show_bug.cgi?id=21068
> 
> Switching between networks can not be solved this way anyway. If the
> network is different, we must assume a new IP. 
As I said, when switching between services, Jukka's patch will not send the
previous service last DHCP address. It will send the last one we got for that
specific service, as a hint.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman

Reply via email to