Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #163174 > unrolled thread
| Started by | Daniel Bareiro <daniel-listas@gmx.net> |
|---|---|
| First post | 2016-01-16 20:30 +0100 |
| Last post | 2016-02-29 14:30 +0100 |
| Articles | 8 — 4 participants |
Back to article view | Back to linux.debian.user
Problem with TP-Link network card Daniel Bareiro <daniel-listas@gmx.net> - 2016-01-16 20:30 +0100
Re: Problem with TP-Link network card John Hasler <jhasler@newsguy.com> - 2016-01-16 21:20 +0100
Re: Problem with TP-Link network card Daniel Bareiro <daniel-listas@gmx.net> - 2016-01-16 21:30 +0100
Re: Problem with TP-Link network card Dan Ritter <dsr@randomstring.org> - 2016-01-17 14:00 +0100
Re: Problem with TP-Link network card Daniel Bareiro <daniel-listas@gmx.net> - 2016-01-17 21:10 +0100
Re: Problem with TP-Link network card Dan Ritter <dsr@randomstring.org> - 2016-01-17 22:40 +0100
Re: Problem with TP-Link network card Daniel Bareiro <daniel-listas@gmx.net> - 2016-02-28 16:50 +0100
Re: Problem with TP-Link network card Luis Eduardo Cortés <luedcortes@gmail.com> - 2016-02-29 14:30 +0100
| From | Daniel Bareiro <daniel-listas@gmx.net> |
|---|---|
| Date | 2016-01-16 20:30 +0100 |
| Subject | Problem with TP-Link network card |
| Message-ID | <qREHU-i0-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi all!
Yesterday I had a power outage in my workplace and when the power was
restored, I noticed I did not have Internet access.
In reviewing the DSL router, I saw the "Ethernet" LED representing the
connection to the computer behind it, a PC firewall with Debian Jessie,
was turned off.
Apparently, the interface on Jessie side had no link. The network
interface is given by a PCI card with Realtek chipset RTL8139D that I'm
using since June 2008 without problems on this computer. It went through
several Debian versions and it was running smoothly with Jessie before
this incident. In fact, in the last update of the kernel that I have
applied (the one published by Salvatore Bonaccorso on December 17), I
restarted the operating system without downside.
I was looking at the syslog and it seems that the link comes and goes:
------------------------------------------------------------------------
(...)
Jan 15 21:47:24 alderamin kernel: [ 249.092973] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:47:24 alderamin kernel: [ 249.114731] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:10 alderamin kernel: [ 295.226378] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:10 alderamin kernel: [ 295.245295] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:14 alderamin kernel: [ 299.105773] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:14 alderamin kernel: [ 299.117529] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:23 alderamin kernel: [ 307.755787] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:23 alderamin kernel: [ 307.759521] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:48:29 alderamin kernel: [ 314.046708] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:29 alderamin kernel: [ 314.055246] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:49:01 alderamin kernel: [ 346.182821] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:49:01 alderamin kernel: [ 346.184420] 8139too 0000:00:09.0
eth1: link down
Jan 15 21:49:36 alderamin kernel: [ 380.625602] 8139too 0000:00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:49:36 alderamin kernel: [ 380.628902] 8139too 0000:00:09.0
eth1: link down
(...)
------------------------------------------------------------------------
To rule out a problem in the DSL router or the network cable, I
unplugged the end connected to the Jessie firewall and plugged it into
my notebook (which also uses Debian Jessie). In this case it is an Intel
network interface:
------------------------------------------------------------------------
$ lspci | grep -i ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
------------------------------------------------------------------------
Here everything runs smoothly. So this leads me to think it's something
on the side of the Jessie firewall.
The strange part is that if I set the card into 10Mbps, the link becomes up:
# mii-tool eth0 -F 10baseT-FD
# rmmod 8139too
# modprobe 8139too
------------------------------------------------------------------------
# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
------------------------------------------------------------------------
# ethtool -s eth1 speed 100
------------------------------------------------------------------------
# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
------------------------------------------------------------------------
# ethtool -s eth1 speed 10
------------------------------------------------------------------------
# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
------------------------------------------------------------------------
In fact, I tested it with a new TP-Link card with the same Realtek
chipset and I have observed the same behavior.
Any idea what could be the problem?
Thank you in advance for your reply
Best regards,
Daniel
[toc] | [next] | [standalone]
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Date | 2016-01-16 21:20 +0100 |
| Message-ID | <qRFui-QT-5@gated-at.bofh.it> |
| In reply to | #163174 |
Daniel Bareiro writes: > Any idea what could be the problem? Hardware. -- John Hasler jhasler@newsguy.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Daniel Bareiro <daniel-listas@gmx.net> |
|---|---|
| Date | 2016-01-16 21:30 +0100 |
| Message-ID | <qRFDY-VC-15@gated-at.bofh.it> |
| In reply to | #163175 |
[Multipart message — attachments visible in raw view] — view raw
Hi, John. Thanks for your reply. On 16/01/16 17:13, John Hasler wrote: >> Any idea what could be the problem? > Hardware. Do you mean to some problem with the motherboard? Best regards, Daniel
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2016-01-17 14:00 +0100 |
| Message-ID | <qRV62-2zR-5@gated-at.bofh.it> |
| In reply to | #163174 |
On Sat, Jan 16, 2016 at 04:24:15PM -0300, Daniel Bareiro wrote: > > In fact, I tested it with a new TP-Link card with the same Realtek > chipset and I have observed the same behavior. > > Any idea what could be the problem? Disable autonegotiation on both sides; set it to full duplex 100. If the behavior persists, replace the cable. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Daniel Bareiro <daniel-listas@gmx.net> |
|---|---|
| Date | 2016-01-17 21:10 +0100 |
| Message-ID | <qS1Ob-7cD-39@gated-at.bofh.it> |
| In reply to | #163201 |
[Multipart message — attachments visible in raw view] — view raw
Hi, Dan.
Thanks for your reply.
On 17/01/16 09:56, Dan Ritter wrote:
>> In fact, I tested it with a new TP-Link card with the same Realtek
>> chipset and I have observed the same behavior.
>>
>> Any idea what could be the problem?
> Disable autonegotiation on both sides; set it to full duplex
> 100.
>
> If the behavior persists, replace the cable.
I was reviewing on the CLI as through the web access if the router
(Zyxel P-660R-T1v3) allows to disable the negotiation of the LAN
interface, but I found nothing. So I tried the other suggestion, that it
was changing the cable, but no change in behavior.
I did some other tests with my notebook:
a) notebook (orion) <---> firewall (alderamin)
b) notebook (orion) <---> router
Case a: notebook (orion) <---> firewall (alderamin)
----------------------------------------------------
root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg on
root@orion:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown (auto)
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:8050 errors:162 dropped:0 overruns:0 frame:105
TX packets:5137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4112009 (3.9 MiB) TX bytes:674943 (659.1 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@orion:~# ip addr add 192.168.1.1 dev eth0
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:8050 errors:162 dropped:0 overruns:0 frame:105
TX packets:5137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4112009 (3.9 MiB) TX bytes:674943 (659.1 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@alderamin:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr c4:e9:84:01:0e:4d
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::c6e9:84ff:fe01:e4d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:359625 errors:151 dropped:0 overruns:48 frame:0
TX packets:326791 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:297907826 (284.1 MiB) TX bytes:45096052 (43.0 MiB)
root@alderamin:~# ethtool -s eth1 speed 100 duplex full autoneg on
root@alderamin:~# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
root@alderamin:~# ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4010ms
It seems that here the connection notebook <---> firewall has not worked
with auto-negotiation on both sides. Now I try to disable the
negotiation on both ends:
root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg off
root@orion:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@alderamin:~# ethtool -s eth1 speed 100 duplex full autoneg off
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@orion:~# ip addr add 192.168.1.1/24 dev eth0
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::3e97:eff:fe57:4a89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10110 errors:162 dropped:0 overruns:0 frame:105
TX packets:5283 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4366052 (4.1 MiB) TX bytes:697362 (681.0 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@alderamin:~# ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.382 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.264 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.396 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.427 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.348 ms
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.264/0.363/0.427/0.058 ms
In this way it seems to work. Again I try enabling the negotiation on
both ends:
root@alderamin:~# ethtool -s eth1 speed 100 duplex full autoneg on
root@alderamin:~# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg on
root@orion:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet6 addr: fe80::3e97:eff:fe57:4a89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10904 errors:162 dropped:0 overruns:0 frame:105
TX packets:5371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4468015 (4.2 MiB) TX bytes:707221 (690.6 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@orion:~# ip addr add 192.168.1.1/24 dev eth0
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::3e97:eff:fe57:4a89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10919 errors:162 dropped:0 overruns:0 frame:105
TX packets:5385 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4469067 (4.2 MiB) TX bytes:709963 (693.3 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@alderamin:~# ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.280 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.319 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.401 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.319 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.439 ms
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 0.280/0.351/0.439/0.062 ms
Now it seems to work. I try again disabling the negotiation:
root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg off
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet6 addr: fe80::3e97:eff:fe57:4a89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11337 errors:162 dropped:0 overruns:0 frame:105
TX packets:5448 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4528130 (4.3 MiB) TX bytes:717866 (701.0 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@orion:~# ip addr add 192.168.1.1/24 dev eth0
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::3e97:eff:fe57:4a89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11359 errors:162 dropped:0 overruns:0 frame:105
TX packets:5460 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4530155 (4.3 MiB) TX bytes:719996 (703.1 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@alderamin:~# ethtool -s eth1 speed 100 duplex full autoneg off
root@alderamin:~# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@alderamin:~# ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.413 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.284 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.315 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.360 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.424 ms
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 0.284/0.359/0.424/0.055 ms
So now it seems to work with and without auto-negotiation.
Case b: notebook (orion) <---> router
--------------------------------------
root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg on
root@orion:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet6 addr: fe80::3e97:eff:fe57:4a89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4998 errors:15 dropped:0 overruns:0 frame:9
TX packets:2331 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:881732 (861.0 KiB) TX bytes:339856 (331.8 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@orion:~# dhclient eth0
Jan 17 15:17:42 orion avahi-daemon[690]: Registering new address record
for 192.168.1.33 on eth0.IPv4.
Jan 17 15:17:43 orion dhclient: bound to 192.168.1.33 -- renewal in
115563 seconds.
root@orion:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=42.8 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=44.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=44.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=44.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=43.0 ms
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 42.842/43.934/44.915/0.920 ms
Now I try notebook <---> router disabling auto-negotiation on the
notebook (the only side that I can change):
root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg off
root@orion:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 3c:97:0e:57:4a:89
inet6 addr: fe80::3e97:eff:fe57:4a89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6873 errors:99 dropped:0 overruns:0 frame:55
TX packets:4038 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3049076 (2.9 MiB) TX bytes:512406 (500.3 KiB)
Interrupt:20 Memory:f2500000-f2520000
root@orion:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@orion:~# dhclient eth0
Jan 17 15:23:14 orion avahi-daemon[690]: Registering new address record
for 192.168.1.33 on eth0.IPv4.
Jan 17 15:23:15 orion dhclient: bound to 192.168.1.33 -- renewal in
125969 seconds.
root@orion:~# ping -c5 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=44.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=43.0 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=42.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=43.9 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=43.9 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 42.981/43.682/44.537/0.598 ms
That is, it seems that the communication notebook <---> router works
well regardless of the type of negotiation on the notebook side.
But when I reconnect the firewall to the router, I lose again the link,
regardless of whether on the firewall is enabled or not the
auto-negotiation.
Best regards,
Daniel
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2016-01-17 22:40 +0100 |
| Message-ID | <qS3df-83t-1@gated-at.bofh.it> |
| In reply to | #163221 |
On Sun, Jan 17, 2016 at 05:07:20PM -0300, Daniel Bareiro wrote: > Hi, Dan. > > Thanks for your reply. ... > That is, it seems that the communication notebook <---> router works > well regardless of the type of negotiation on the notebook side. > > But when I reconnect the firewall to the router, I lose again the link, > regardless of whether on the firewall is enabled or not the > auto-negotiation. I'm afraid at this point my suggestions all involve hardware: - replace the TP-Link nic with something else, preferably with a different chipset. Intel has been very reliable. - put a small ethernet switch (4 and 5 port switches are reasonably cheap) between the router and firewall. - replace the router with something else. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Daniel Bareiro <daniel-listas@gmx.net> |
|---|---|
| Date | 2016-02-28 16:50 +0100 |
| Message-ID | <r7bLz-4E3-11@gated-at.bofh.it> |
| In reply to | #163223 |
[Multipart message — attachments visible in raw view] — view raw
Hi, Dan. On 17/01/16 18:33, Dan Ritter wrote: >> That is, it seems that the communication notebook <---> router works >> well regardless of the type of negotiation on the notebook side. >> >> But when I reconnect the firewall to the router, I lose again the link, >> regardless of whether on the firewall is enabled or not the >> auto-negotiation. > I'm afraid at this point my suggestions all involve hardware: > > - replace the TP-Link nic with something else, preferably with a > different chipset. Intel has been very reliable. > > - put a small ethernet switch (4 and 5 port switches are reasonably > cheap) between the router and firewall. > > - replace the router with something else. Well, after some time, I have returned to this matter. I have done one more test that I think is is conclusive. As I said, this Debian GNU/Linux firewall PC has two network cards: * eth0: RealTek RTL8139 (to the ADSL router) * eth1: VIA Rhine II (to the local network) The problem was with the RTL8139 card connected to the router. This only worked when setting up it to 10 Mbps. The VIA card connected to the switch of the local network never gave problems. So I now exchanged the configuration of the cards. Now the eth0 Realtek card connects to the internal network. It runs smoothly at 100 Mbps, full duplex and auto negotiation. So I think it was not a problem with the Realtek card. In fact, now the VIA card (that previously worked properly connected to the internal network switch) only works against ADSL router when it is set to 10 Mbps. All this makes me think the problem is in the ethernet interface of the ADSL router. I have requested a new router to Telefonica. I hope they send me a good one. This Zyxel router worked smoothly for quite some time. I also hope it have a default password to access the router and make the necessary settings (such as SNMP monitoring). Thanks for your reply. Kind regards, Daniel
[toc] | [prev] | [next] | [standalone]
| From | Luis Eduardo Cortés <luedcortes@gmail.com> |
|---|---|
| Date | 2016-02-29 14:30 +0100 |
| Message-ID | <r7w3F-3yu-25@gated-at.bofh.it> |
| In reply to | #164783 |
[Multipart message — attachments visible in raw view] — view raw
> > Well, after some time, I have returned to this matter. > > I have done one more test that I think is is conclusive. As I said, this > Debian GNU/Linux firewall PC has two network cards: > > * eth0: RealTek RTL8139 (to the ADSL router) > * eth1: VIA Rhine II (to the local network) > > The problem was with the RTL8139 card connected to the router. This only > worked when setting up it to 10 Mbps. The VIA card connected to the > switch of the local network never gave problems. > > So I now exchanged the configuration of the cards. Now the eth0 Realtek > card connects to the internal network. It runs smoothly at 100 Mbps, > full duplex and auto negotiation. So I think it was not a problem with > the Realtek card. In fact, now the VIA card (that previously worked > properly connected to the internal network switch) only works against > ADSL router when it is set to 10 Mbps. > > All this makes me think the problem is in the ethernet interface of the > ADSL router. > > I have requested a new router to Telefonica. I hope they send me a good > one. This Zyxel router worked smoothly for quite some time. I also hope > it have a default password to access the router and make the necessary > settings (such as SNMP monitoring). > > > Thanks for your reply. > > Kind regards, > Daniel > Try installing "firmware-realtek" package to solve the original problem. Regards.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web