Here is the output of ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:A9:47:F0:BC
inet6 addr: fe80::213:a9ff:fe47:f0bc/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:16044 (15.6 Kb)
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:35 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4377 (4.2 Kb) TX bytes:4377 (4.2 Kb)
wlan0 Link encap:Ethernet HWaddr 00:18:DE:0B:37:B6
inet addr:192.168.0.142 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::218:deff:fe0b:37b6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14867 errors:0 dropped:0 overruns:0 frame:0
TX packets:8871 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21295065 (20.3 Mb) TX bytes:967514 (944.8 Kb)
and route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
and here are all the outputs while I tried to connect via the powerline:
/sbin/lspci -s 0a:08.0 -nnk (powerline)
0a:08.0 Ethernet controller [0200]: Intel Corporation PRO/100 VE Network Connection [8086:1092] (rev 02)
Subsystem: Sony Corporation Device [104d:81ef]
Kernel driver in use: e100
cat /etc/resolv.conf (powerline)
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
search site
ip addr (powerline)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:13:a9:47:f0:bc brd ff:ff:ff:ff:ff:ff
inet6 fe80::213:a9ff:fe47:f0bc/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:18:de:0b:37:b6 brd ff:ff:ff:ff:ff:ff
ifconfig (powerline)
eth0 Link encap:Ethernet HWaddr 00:13:A9:47:F0:BC
inet6 addr: fe80::213:a9ff:fe47:f0bc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:33472 (32.6 Kb)
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:35 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4377 (4.2 Kb) TX bytes:4377 (4.2 Kb)
route (powerline)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
"1. Can you you tell us make and model of this powerline network device? "
What do you exactly mean with this?
“2. Do you get a link light when you connect your ethernet cable?”
All the red lights turn green but I think normally one or two should start blinking
“3. Have you tried having both powerline devices connected side by side or in the same room?”
Yes, I'm always in the same room and I tried it side by side.
“4. Have you read the manufacturer documentation concerning connectivity? They usually have fault finding advice or FAQ…”
Yes I have read the docs but they don't talk about linux and because it works with windows xp I think the network is OK
greetz,
Tony