1 |
On Tuesday 14 Jun 2011 15:42:52 Cahn Roger wrote: |
2 |
> Hi Mick, |
3 |
> |
4 |
> > What does the router log show? |
5 |
> |
6 |
> Euh, how can I get it??? |
7 |
|
8 |
It depends on your router. Usually routers have at least a GUI control panel |
9 |
access and one of the pages shows recent attempts to connect and authenticate. |
10 |
|
11 |
Are your running some sort of an access control list on the router and have |
12 |
not included your MAC address? |
13 |
|
14 |
|
15 |
> > Can you please share: |
16 |
> > ifconfig eth0 |
17 |
> |
18 |
> ifconfig eth0 |
19 |
> eth0 Lien encap:Ethernet HWaddr 00:1e:8c:4a:44:db |
20 |
> inet adr:169.254.79.43 Bcast:169.254.255.255 |
21 |
> Masque:255.255.0.0 adr inet6: fe80::21e:8cff:fe4a:44db/64 Scope:Lien |
22 |
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
23 |
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
24 |
> TX packets:110 errors:0 dropped:0 overruns:0 carrier:0 |
25 |
> collisions:0 lg file transmission:1000 |
26 |
> RX bytes:0 (0.0 B) TX bytes:20708 (20.2 KiB) |
27 |
> Interruption:17 |
28 |
|
29 |
The Rx bytes is zero - your router does not seem to respond. |
30 |
|
31 |
Does this also stay zero if you set up a static address and route on the PC |
32 |
and try to ping the router? |
33 |
|
34 |
> /etc/conf.d/net |
35 |
> |
36 |
> # This blank configuration will automatically use DHCP for any net.* |
37 |
> # scripts in /etc/init.d. To create a more complete configuration, |
38 |
> # please review /etc/conf.d/net.example and save your configuration |
39 |
> # in /etc/conf.d/net (this file :]!). |
40 |
> |
41 |
> config_eth0="dhcp" |
42 |
> |
43 |
> In the box I stopped the option fixed adresses, |
44 |
> but the problem remains the same :-( |
45 |
|
46 |
Try setting an address manually: |
47 |
|
48 |
ifconfig eth0 192.168.1.20 broadcast 192.168.1.255 netmask 255.255.255.0 |
49 |
|
50 |
route add default gw 192.168.1.1 (assuming that this is your router) |
51 |
|
52 |
and then try to ping it: |
53 |
|
54 |
ping -c 3 192.168.1.1 |
55 |
|
56 |
If you can ping it and get a response then the problem is probably with the |
57 |
router. |
58 |
-- |
59 |
Regards, |
60 |
Mick |