I responded to Rainer this morning, and GMail (on my phone) sent the
response directly to him instead of the group.
Problem solved. I had run across 'ip link show' while googling, but
didn't know how to interpret it. When I went to check the lights on the
NIC, i see no lights, AND NO CABLE! Apparently, the cable was never
reconnected to the desktop's NIC. (I don't actually know when it got
disconnected. I don't remember doing it. Maybe the tech unplugged
it?) After plugging it in: lights blink, 'ip link show' looks good, and
Firefox connects.
Yay!
I should have known to check that first. I've told other people to
check their connections often enough.
Marc
On 5/14/25 3:48 PM, Ralph Ronnquist via Dng wrote:
> On Wed, May 14, 2025 at 07:54:31AM -0700, Marc Shapiro via Dng wrote:
>> I don't know. It's possible that he connected with something other than
>> DHCP, but it seems unlikely. DHCP is so common. Also, if that's the way
>> the desktop has been connecting to the ISP, the tech would use the same
>> method the clients use. At least, I hope he would.
> The very first thing is to check the cable and physical connectivity.
> THe best is if you have a different cable to test with.
>
> Next you would run tcpdump (or similar) on your desktop to see whether
> or not it picks up any networking traffic at all. The interface need
> to be "up" for that but it doesn't need to have IP level setup.
>
> If there is traffic, then it is likely that your DHCP server in the
> router is broken. If there is no traffic, then it's likely to be
> hardware fault; either at the router end or the desktop end (or the
> cable).
>
> Ralph.
>
>> Marc
>>
>> On Wed, May 14, 2025, 1:48 AM onefang <onefang_devuan@???> wrote:
>>
>>> On 2025-05-13 22:44:39, Marc Shapiro via Dng wrote:
>>>> Yesterday, my internet connection failed. My ISP sent a tech out
>>> today.
>>>> He replaced hardware outside, and eventually was able to connect his
>>>> laptop directly to the ethernet where it comes into the house. It
>>> did not
>>>> work when connected to my eero router. The tech thinks the current
>>>> problem is with the router. I have my doubts, however, since the
>>> desktop
>>>> computer does not get a network connection when plugged into the
>>> router or
>>>> directly into the ethernet port.
>>>> If I do:
>>>> ifdown eth0
>>>> ifup eth0
>>>> I get the following:
>>>> Listening on LPF/eth0/90:2b:34:9d:4d:6b
>>>> Sending on LPF/eth0/90:2b:34:9d:4d:6b
>>>> Sending on Socket/fallback
>>>> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
>>>> .
>>>> .
>>>> 4 more lines like this, each with a different interval
>>>> .
>>>> No DHCPOFFERS received.
>>>> No working leases in persistent database - sleeping.
>>>> Did a config somehow get messed up? Is my network card
>>> malfunctioning?
>>>> What info do you need to help diagnose this pboblem.
>>> Did the tech use DHCP? There's things like PPoE and such that ISPs might
>>> use instead on that part of their network. Think they need a user and
>>> password though, which your ISP should tell you what they are.
>>>
>>> --
>>> A big old stinking pile of genius that no one wants
>>> coz there are too many silver coated monkeys in the world.
>>> _______________________________________________
>>> Dng mailing list
>>> Dng@???
>>> Manage your subscription:
>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>> Archive: https://lists.dyne.org/lurker/list/dng.en.html
>>>
>> _______________________________________________
>> Dng mailing list
>> Dng@???
>> Manage your subscription: https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>> Archive: https://lists.dyne.org/lurker/list/dng.en.html
> _______________________________________________
> Dng mailing list
> Dng@???
> Manage your subscription: https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> Archive: https://lists.dyne.org/lurker/list/dng.en.html
::
Re: [DNG] Ethernet fails to connect…
