On Sat, 2007-12-08 at 14:37 +0000, John Carr wrote:
> On 12/8/07, Ochal Christophe <[EMAIL PROTECTED]> wrote:

> > Actually, no.
> > What you need is a fixed interface on the linux machine (this is the
> > serial/bluetooth/whatchawantit interface) that listens to connecting
> > devices. This side *HAS* a fixed ip that's different from your other ip
> > address (on the interface facing your network), you *will* need to use
> > iptables for routing if you want your PDA to get to the internet this
> > way, but if not, all you need to do is run a dhcp server on the linux
> > machine that's binding to the fixed ip address of the serial/bluetooth
> > interface.
> 
> Well thats obviously the logical choice. So far we force a device to
> use an IP of our choice, however that breaks for at least the Moto Q.
> This has an IP that seems to change randomly. Odccm has been modded to
> let a user choose an IP, allowing the Moto Q to work.
> 
> Its also worth noting that if you want the PDA to get the internet
> some apps will work with standard routing. Others need DTPT.py to
> supply the Desktop Passthrough Proxy. Joy.
> 
> > No WM device i have seen sofar comes with a dhcp-server, only with a dhcp 
> > client.
> 
> Are you absolutely certain?

Well, i haven't seen one yet :P And like you said, it wouldn't be
logical, however, wouldn't these devices be PDA/Phone combo's by change?

I suppose, if they are phones, that they *might* have a dhcp-server
integrated to allow other devices to connect to them to access the
internet, but even in this situation it would strike me as very odd.

> [EMAIL PROTECTED]:~/Projects/synce/usb-rndis-lite$ sudo ifconfig eth3
> eth3      Link encap:Ethernet  HWaddr 80:00:60:0f:e8:00
>           UP BROADCAST RUNNING MULTICAST  MTU:8050  Metric:1
>           RX packets:7 errors:6 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:340 (340.0 B)  TX bytes:134 (134.0 B)
> 
> [EMAIL PROTECTED]:~/Projects/synce/usb-rndis-lite$ sudo dhclient eth3
> Internet Systems Consortium DHCP Client V3.0.6
> Copyright 2004-2007 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
> 
> Listening on LPF/eth3/80:00:60:0f:e8:00
> Sending on   LPF/eth3/80:00:60:0f:e8:00
> Sending on   Socket/fallback
> DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 5
> DHCPOFFER from 169.254.2.1
> DHCPREQUEST on eth3 to 255.255.255.255 port 67
> DHCPACK from 169.254.2.1
> bound to 169.254.2.2 -- renewal in 1260637 seconds.
> 
> [EMAIL PROTECTED]:~/Projects/synce/usb-rndis-lite$ sudo ifconfig eth3
> eth3      Link encap:Ethernet  HWaddr 80:00:60:0f:e8:00
>           inet addr:169.254.2.2  Bcast:169.254.2.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:8050  Metric:1
>           RX packets:9 errors:8 dropped:0 overruns:0 frame:0
>           TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:944 (944.0 B)  TX bytes:3971 (3.8 KiB)
> 
> eth3 is the WM6 device i just plugged in. It's the same with my WM5
> device. What the hell is responding to the DHCP request???

What you're witnessing is, i'm guessing, zero-configuration, i say that
because of the IP addresses involved (the 169.254/16 range), i did some
quick checking, this is described in RFC3927.

Also note that Avahi implements a plugin for dhclient to support
RFC3927.

I haven't read the specifics yet of both, but here are the links:
RFC3927: http://www.ietf.org/rfc/rfc3927.txt
Avahi: http://avahi.org/wiki/AvahiAutoipd

> One thought I have is that the phone has some kind of fake DHCP thing
> going on so that windows can auto configure the device with an IP when
> you plug it in - the values it returns might come from the registry,
> rather than a traditional DHCP server. (This fits with some keys that
> we have been able to change in the past I think).

It also fits with the zero-configuration system in that the WM device
caches it's last known good ip address.


-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel

Reply via email to