On 10/29/20 7:02 AM, D'Arcy Cain wrote:
Turns out it has nothing to do with virtualization. It never occurred to me
to test that the host could access the Internet since I had no problem
connecting and logging in. However, everything I described for the VM
applies to the host as well. Here i
On 10/29/20 10:52 AM, D'Arcy Cain wrote:
I will try upgrading.
Nice try, D'Arcy. how do you plan to do that without networking? :-(
--
D'Arcy J.M. Cain | Democracy is three wolves
http://www.druid.net/darcy/| and a sheep voting on
+1 416 788 2246 (DoD#0082)
On 10/29/20 7:41 AM, sth...@nethelp.no wrote:
Here is a ProLiant DL360 Gen9 server with the same type of Ethernet
card:
Yes, same server as I have. It's the only Gen9 that I have so far.
% grep 'HP Ethernet' /var/run/dmesg.boot
bge0: mem
0x92b9-0x92b9,0x92ba-0x92ba,0x92bb00
> Here is eth0 which started out as bge0:
> bge0: mem
> 0x92b9-0x92b9,0x92ba-0x92ba,0x92bb-0x92bb
> at device 0.0 numa-domain 0 on pci15
> bge0: APE FW version: NCSI v1.3.7.0
> bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E
...
> Surprisingly, although I
NOTE: Was "Bridge woes"
On 10/25/20 1:32 PM, D'Arcy Cain wrote:
I have been trying to solve this problem for a week now. I have been
emailing the virtualization list (Re: When is a switch not a switch?)
because it had to do with vm-bhyve but now I am wondering if it is something
else. Maybe
