From: Ed Asp <edasbugs@hotmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] my network card doesnt seemed to be working
Date: Fri, 4 Mar 2022 20:26:39 +0000 [thread overview]
Message-ID: <MWHPR03MB31527E04B4E6C20EC6A8DAF0DF059@MWHPR03MB3152.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CAMah9rvVVH_EQaLBAn4TuwU6zoQQuuJUsFwTkTEHVcbr+RqVdA@mail.gmail.com>
hi, answering your questions:
running debian-10-turnkey-fileserver_16.1-1_amd64.tar.gz
on Prox mox 7.1-7
freshly created CT:
host: testFileserver
created with Network: IPV4-DHCP; IPV6-Static; DNS domain: use host settings; DNS servers: use host settings
after creation logged as root:
pastebin.com, and provide the output of ip addr=> do not know what is this
lspci -v => -bash: lspci: command not found
dmesg -T => dmesg: read kernel buffer failed: Operation not permitted
cat /etc/network/interfaces =>
root@testFileserver ~# cat /etc/network/interfaces
# UNCONFIGURED INTERFACES
# remove the above line if you edit this file
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
allow-hotplug eth1
iface eth1 inet dhcp
ip a =>
root@testFileserver ~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0@if112: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether e2:e0:e4:2a:b3:29 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.0.102/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::e0e0:e4ff:fe2a:b329/64 scope link
valid_lft forever preferred_lft forever
________________________________
From: pve-user <pve-user-bounces@lists.proxmox.com> on behalf of M. Lyakhovsky <markl17@gmail.com>
Sent: Thursday, March 3, 2022 3:11 PM
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] my network card doesnt seemed to be working
here is compilation of all of the commands like cat /etc/network/interfaces
ip a and the rest the last is dmesg
On Thu, Mar 3, 2022 at 11:31 AM Kyle Schmitt <kyleaschmitt@gmail.com> wrote:
> You need to give a lot more information if you want help. Use a
> pastebin service, like pastebin.com, and provide the output of ip
> addr, lspci -v, and dmesg -T. Also dmidecode might help, might not,
> depends on what's really wrong.
>
> On Tue, Mar 1, 2022 at 8:11 PM M. Lyakhovsky <markl17@gmail.com> wrote:
> >
> > --
> > Do have a Blessed Day
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
--
Do have a Blessed Day
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2022-03-04 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 2:10 M. Lyakhovsky
2022-03-03 16:30 ` Kyle Schmitt
2022-03-03 20:11 ` M. Lyakhovsky
2022-03-04 20:26 ` Ed Asp [this message]
2022-03-04 20:31 ` Ed Asp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR03MB31527E04B4E6C20EC6A8DAF0DF059@MWHPR03MB3152.namprd03.prod.outlook.com \
--to=edasbugs@hotmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.