On 8/15/23 20:34, Tim via users wrote:
On Tue, 2023-08-15 at 22:02 +0100, Barry wrote:
Better these days to replace ifconfig with:
ip addr
I'm not so sure I agree with that, there's some useful info provided by
ifconf that ip addr doesn't supply. For example:
RX packets 24927
On Wed, 16 Aug 2023 13:04:07 +0930 Tim via users wrote:
> On Tue, 2023-08-15 at 22:02 +0100, Barry wrote:
>> Better these days to replace ifconfig with:
>> ip addr
> I'm not so sure I agree with that, there's some useful info provided by
> ifconf that ip addr doesn't supply. For example:
On Tue, 2023-08-15 at 22:02 +0100, Barry wrote:
> Better these days to replace ifconfig with:
>
> ip addr
I'm not so sure I agree with that, there's some useful info provided by
ifconf that ip addr doesn't supply. For example:
RX packets 24927062 bytes 16569920396 (15.4 GiB)
> On 15 Aug 2023, at 09:21, Tim via users wrote:
>
> If you type ifconfig into the command line, does your ethernet port
> have a valid IP (not 127.0.0.1 nor an IP starting 169.254)? If it has
> one of them, it won't be able to do anything. Likewise if it has none.
>
> Does your PC have a na
On Tue, 2023-08-15 at 17:50 +0930, Tim via users wrote:
> Does your PC have a nameserver configured in the settings?
>
> e.g. grep nameserver /etc/resolv.conf
And, I just noticed that my resolv.conf file suggests this command:
resolvectl status
--
uname -rsvp
Linux 3.10.0-1160.92.1.el7.x86_
On Mon, 2023-08-14 at 22:34 -0700, Mike Wright wrote:
> 2 f38 hosts. 1 dnf install xxx works fine. Very fast. 2) spins
> forever: dnf.log shows
>
> Error during transfer: Curl error (28): Timeout was reached for
> https://mirrors.fedo...
>
> Web searches show this to be common. It also showe
> On 15 Aug 2023, at 06:34, Mike Wright wrote:
>
> Hi all,
>
> 2 f38 hosts. 1 dnf install xxx works fine. Very fast. 2) spins forever:
> dnf.log shows
>
> Error during transfer: Curl error (28): Timeout was reached for
> https://mirrors.fedo...
>
> Web searches show this to be common.
