Hey again!

As far as good =) The problem with your cable modem is just because you haven't set a default gateway.
Bot now we know that it's nothing "big".

I'll have a look for the path to fix the dhcp problem.


Regards

Bernhard Wörndl-Aichriedler


Am 17.05.2010 22:01, schrieb vwyodapink:
I tried what you suggested and it gave me the IP4 address  and I am able to
ping the router. The router itself has no security on it right now what so
ever. Trying to ping my cable modem I get network unreachable. So its not
leaving my router now. I double checked to make sure that there is nothing
on the routers end that could block it, just to be sure and still with the
onboard nand image and the latest desktop image give me the same results of
getting to ping the router but not being able to leave the router. Thanks
for the help so far. 

Here are the results:
overo login: root
root@overo:~# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2328 (2.2 KiB)  TX bytes:2328 (2.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:50:43:02:FE:01  
          inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)

root@overo:~# ifconfig wlan0 192.168.3.5
root@overo:~# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:50:43:02:FE:01  
          inet addr:192.168.3.5  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:4231 (4.1 KiB)

root@overo:~# ping 192.168.3.1
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.
64 bytes from 192.168.3.1: icmp_seq=1 ttl=64 time=8.85 ms
64 bytes from 192.168.3.1: icmp_seq=2 ttl=64 time=3.14 ms
64 bytes from 192.168.3.1: icmp_seq=3 ttl=64 time=2.41 ms
64 bytes from 192.168.3.1: icmp_seq=4 ttl=64 time=2.71 ms
^C
--- 192.168.3.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.411/4.280/8.850/2.651 ms
root@overo:~# ping 192.168.0.1
connect: Network is unreachable
root@overo:~# 



Bernhard Wörndl-Aichriedler wrote:
  
Hey =)

If says -

No lease, failing

no correct IP has been obtained, you can try to set the IP manually - 
ifconfig wlan0 192.168.x.x

There actually was a discussion about the DHCP failing in the lastest 
versions.
You might be connected, and just not get a correct IP to work with.


Regards

*Bernhard Wörndl-Aichriedler*