adamant-kite-43734
03/25/2023, 2:51 AMrefined-analyst-8898
03/25/2023, 2:52 AMrefined-analyst-8898
03/25/2023, 3:02 AMagreeable-oil-87482
03/25/2023, 8:46 AMrefined-analyst-8898
03/25/2023, 2:13 PMagreeable-oil-87482
03/25/2023, 2:15 PMagreeable-oil-87482
03/25/2023, 2:16 PMagreeable-oil-87482
03/25/2023, 2:17 PMrefined-analyst-8898
03/25/2023, 2:18 PMrefined-analyst-8898
03/25/2023, 2:19 PMrefined-analyst-8898
03/25/2023, 2:37 PMeth0
does not receive an IP lease. I made a second VM to test supplying the network-data on first boot, but the result was the same as follows.
version: 1
config:
- type: physical
name: eth0 # name is varies upon OS image
subnets:
- type: dhcp
I used eth0
because it is shown in the console, so I surmise that is the correct adapter name for Tumbleweed.
The DHCP server shows no leases given for the Ethernet addresses reported for these guests in Harvester.refined-analyst-8898
03/25/2023, 2:39 PMrefined-analyst-8898
03/26/2023, 2:26 PMe1000
NIC on the VLAN showed a source IP of the cluster mgmt
network bridge, i.e. the Harvester node's external IPrefined-analyst-8898
03/26/2023, 4:19 PMvirtio
on Ubuntu and LEAP. Using an Ubuntu VM as a router, the LAN client's packet is somehow mutated to have the source IP of the Harvester node's external interface. The router will forward the packet, and the response is received, but can not be routed to the LAN client because the destination of the response is incorrectly the node IP.
🤷refined-analyst-8898
03/26/2023, 4:21 PMbumpy-portugal-40754
03/27/2023, 11:03 PMrefined-analyst-8898
03/27/2023, 11:03 PMbumpy-portugal-40754
03/27/2023, 11:05 PMrefined-analyst-8898
03/28/2023, 3:18 AMbumpy-portugal-40754
03/28/2023, 8:42 AM