LAN Ethernet not working after fixing Wi-Fi IP

Max2Play Home Forums Max2Play on Raspberry PI LAN Ethernet not working after fixing Wi-Fi IP

Viewing 2 posts - 1 through 2 (of 2 total)
  • 8. Juni 2024 at 9:51 #53203

    Hi, I have been using Max2Play for many years without problems using a LAN cable. Recently I had to use Wi-Fi, so I enabled Wi-Fi and fixed the IP. It worked okay but I now want to revert to LAN, but it is not recognised. I have tried turning off the Wi-Fi interface and I lost all connection to the Pi. I also turned off fixed IP and the issue did not resolve. If I SSH command “ sudo ip link set eth0 up”, it works, but when I reboot it reverts to the problem condition.

    Please can you help me resolve. Thanks.

    Debug info:
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    ether b8:27:eb:59:b2:0f txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 24 bytes 8400 (8.2 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    loop txqueuelen 1000 (Local Loopback)
    RX packets 1799 bytes 145656 (142.2 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1799 bytes 145656 (142.2 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.0.195 netmask 255.255.255.0 broadcast 192.168.0.255
    ether b8:27:eb:0c:e7:5a txqueuelen 1000 (Ethernet)
    RX packets 828 bytes 245390 (239.6 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 546 bytes 163935 (160.0 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    ### WLAN ###
    wlan0 IEEE 802.11 ESSID:“VM7155994″
    Mode:Managed Frequency:2.462 GHz Access Point: 34:5D:9E:AE:8E:39
    Bit Rate=72.2 Mb/s Tx-Power=31 dBm
    Retry short limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=52/70 Signal level=-58 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    8. Juni 2024 at 17:12 #53204

    Somehow, the problem fixed itself.

    Resolved.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Register here