netdev - Re: Unable to TX data on VSC8531

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b2e5bbf6-de38-47e5-9b93-6811979cf180@lunn.ch>
Date:   Mon, 1 May 2023 22:12:29 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Ron Eggler <ron.eggler@...tywest.com>
Cc:     netdev@...r.kernel.org
Subject: Re: Unable to TX data on VSC8531

> After a fresh rebootI executed:
> 
> # ping 192.168.1.222 -c 1
> 
> and see the following:
> 
> # ifconfig
> eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500  metric 1
>         inet 192.168.1.123  netmask 255.255.255.0  broadcast 192.168.1.255
>         ether be:a8:27:1f:63:6e  txqueuelen 1000  (Ethernet)
>         RX packets 469  bytes 103447 (101.0 KiB)
>         RX errors 0  dropped 203  overruns 0  frame 0
>         TX packets 0  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>         device interrupt 170
> 
> eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500  metric 1
>         ether fe:92:66:6c:4e:24  txqueuelen 1000  (Ethernet)
>         RX packets 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 0  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>         device interrupt 173
> 
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536  metric 1
>         inet 127.0.0.1  netmask 255.0.0.0
>         loop  txqueuelen 1000  (Local Loopback)
>         RX packets 1  bytes 112 (112.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 1  bytes 112 (112.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> it appears like the ping got sent to the loopback device instead of the
> eth0, is this possible?

It is unlikely. Loopback is used for lots of things. Rather than -c 1,
leave it running. There should be an arp sent around once a
second. See if the statistics for lo go up at that rate.

> I got the following:
> 
> # mii-tool -vv eth0
> Using SIOCGMIIPHY=0x8947
> eth0: negotiated 100baseTx-FD, link ok
>   registers for MII PHY 0:
>     1040 796d 0007 0572 01e1 45e1 0007 2801
>     0000 0300 4000 0000 0000 0000 0000 3000
>     9000 0000 0008 0000 0000 0000 3201 1000
>     0000 a020 a000 0000 802d 0021 0400 0000
>   product info: vendor 00:01:c1, model 23 rev 2
>   basic mode:   autonegotiation enabled
>   basic status: autonegotiation complete, link ok
>   capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD
> 10baseT-FD 10baseT-HD
>   advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>   link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD
> 10baseT-FD 10baseT-HD flow-control

So you have the register values to answer Horatiu question.

   Andrew