> > I cannot log in, but the menu offered by the modem does not show any relevant settings. > > > You might also test a device on wifi and/or login to the router and > > send a test ping from inside the router with a large size. > > WiFi is turned off on the modem, but I might give it a try. > > > What does the network config for 192.168.2.7 look like? And you do > > the pings from the server connected to both? > > $ ifconfig eth1 > eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1456 > inet 192.168.2.7 netmask 255.255.255.0 broadcast 192.168.2.255 > ether 00:1b:21:3a:56:72 txqueuelen 1000 (Ethernet) > RX packets 4009354 bytes 4646140675 (4.3 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 1465729 bytes 195820660 (186.7 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 18 memory 0x515c0000-515e0000 > > I do the pings and tracepath from this server. > > > It could be the reason no one else is seeing this is that they are not > > using the wired network and that is what they screwed up. > > The ISP finally confirmed that other users have issues too. Good news I guess? > That is good news. It means they will talk to whoever their vendor support is. What firmware version is on the device? I think I found what the device is and there were 2 firmware updates recently, and the 2nd one was 3 days after the first and that is usually a sign that something serious was wrong with the first update. -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
