I've got it working now :-)
David Kempe wrote:
that looks like it works. 220.101.10.1 look slike an unwired dhcp server.
perhaps the data logger can't handle tne public ip.
I thought of that option too and went looking for hosts.deny settings
etc, but then I figured it out :-)
Turns out th
Peter Rundle wrote:
Link Data Logger --> unWired modem (Failure)
13:23:05 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 00:01:c0:00:f9:8e, length: 548
13:23:06 IP 220.101.10.1.bootps > 220.101.12.219.bootpc: BOOTP/DHCP,
Reply, length: 300
that looks like it w
Thanks Martin and Dave for your help.
I've still not got it working but I've got some more information, maybe
you can make sense of it.
I've edited the ifup script on the logger and echo'd out the return code
from the dhcpcd. It's 0 on success and 14 when it fails. I've searched
the dhcpcd s
[EMAIL PROTECTED] wrote:
Does anyone know if the unwired modem is a router or a bridge? I'm assuming it's
a bridge and that the default gateway and the dhcp server is on the other end of
the unWired connection.
Its a bridge I think for all purposes. It probably can do some routing,
but for you
Pete,
Is your datalogger ethernet got fixed speed (10M?) or duplex and is it
possible that the Unwired modem is 100M only? Mii-diag or mii-tool will
tell you what your datalogger is set to. Use ifconfig and look for
packet counts (or tcpdump if iy have it on the logger) to see if it is
actually re
