Freerunner corrupts dhcp forwarding of Linksys WRE54G wirelessrange extender

Sargun Dhillon xbmodder+openmoko at
Sat Jan 17 08:27:16 CET 2009

It's not the freerunners fault. Don't blame it. Your forwarding device
is obviously crap...

On Fri, Jan 16, 2009 at 10:49 PM, Joel Newkirk <freerunner at> wrote:
> On Fri, 16 Jan 2009 18:38:08 +0200, Timo Juhani Lindfors
> <timo.lindfors at> wrote:
>> Jan Vlug <jan.public at> writes:
>>> Resetting the WRE54G by unplugging it fixes this problem.
>>> I am surprised by this behavior because in theory, the WRE54G should
>>> only forward network packets...
>> Can you capture the network traffic to file and put it online
>> somewhere? It would be useful to see both the working and non-working
>> case.
> Indeed this is odd.  A traffic cap from the DHCP server would be quite
> helpful, if it's capable of that.  If it's a linux box, then "tshark -i
> eth0 -f 'udp port 67 or udp port 68' -w dhcpsniff.cap" should stuff full
> packets into the designated file - alter the interface designation as
> needed.  The resulting file will be a binary capture that can subsequently
> be opened and analyzed by tshark and wireshark, among other programs.
> It'd be good if you could capture samples of:
> A successful DHCP request from a PC.
> The successful DHCP request from the FreeRunner.
> A failed DHCP request from the same PC once the FR request has processed.
> j
> --
> Joel Newkirk
>      (blog)
> (FR stuff)
> _______________________________________________
> Openmoko community mailing list
> community at

More information about the community mailing list