[PLUG] Network troubleshooting help (urgent)

[Ben Koenig]

While troubleshooting, you may want to adjust your ifconfig command to the
following:
$ ifconfig -a

This might vary on certain systems, but my understanding is that ifconfig
defaults to only showing interfaces that are UP. If your thunderbolt
interface is detected, but not initialized then it will be DOWN. In this
scenario, the -a option to ifconfig will be required to see that it exists.

This is an important piece of information. By running ifconfig -a you can
start to isolate the failing component.

On Tue, Dec 17, 2019 at 3:21 PM John Jason Jordan <johnxj at gmx.com> wrote:

> On Tue, 17 Dec 2019 16:54:39 -0600
> David Bridges <dbridges at austin.rr.com> dijo:
>
> >I would check to see if you have the bolt package installed and it not
> >install it and enable it.
>
> I did not have it installed, so I did so, then started it. The 'enable'
> command gave me an error, thatI didn't understand much of:
>
>         The unit files have no installation config (WantedBy,
>         RequiredBy, Also, Alias settings in the [Install] section, and
>         DefaultInstance for template units). This means they are not
>         meant to be enabled using systemctl. Possible reasons for
>         having this kind of units are: 1) A unit may be statically
>         enabled by being symlinked from another unit's .wants/
>         or .requires/ directory. 2) A unit's purpose may be to act as a
>         helper for some other unit which has a requirement dependency
>         on it. 3) A unit may be started when needed via activation
>         (socket, path, timer, D-Bus, udev, scripted systemctl
>         call, ...). 4) In case of template units, the unit is meant to
>         be enabled with some instance name specified.
>
> Finally, I moved the cable from the compute to the dock, then rebooted.
> When the system came back up there was no network at all - no ethernet,
> no wifi. I moved the cable from the dock back to the computer and
> ethernet came up.
>
> So two problems:
>
>         1) The ethernet port in the dock is not communicating with the
>         computer.
>         2) The wifi has never worked, and does not even appear with the
>         ifconfig command.
>
> I'm off to see if my duck-duck internet friends can shed any light on
> these issues.
> _______________________________________________
> PLUG mailing list
> PLUG at pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>