Dummy interfaces and IP addresses not synced
See original GitHub issueI have some VyOS VM’s that uses the dummy
linux type of interfaces. These VMs uses Debian Buster as base OS.
The IP’s are exposed on vmware tools, but doing some debugging, I see that they don’t have a Device
nor a NetworkName
property.
I want these IP’s to be synced to netbox, as they are used globally.
When I do a netbox-sync
I don’t see the IP’s are ever listed in the debug output.
I included a second interface that does work as intended for comparison.
Using PowerCLI tools:
PS> $myVm = Get-VM -name myDummyRouterVM
PS> $myVm.Guest.Nics | select -Property *
...
Connected : True
Device :
IPAddress : {xxx.xxx.222.248, xxx.xxx.222.249, xxx.xxx.222.250, xxx.xxx.222.251...}
MacAddress : 76:3e:00:c9:3c:d9
NetworkName :
Connected : True
Device : Network adapter 3
IPAddress : {172.23.252.1, fe80::250:56ff:febc:5ec}
MacAddress : 00:50:56:bc:05:ec
NetworkName : dvportgroup-510922
And on the VM, the IP addresses are shown like this
user@myDummyRouter:~$ ip addr show dev dum0 | strip-private
5: dum0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 76:3e:00:c9:3c:d9 brd ff:ff:ff:ff:ff:ff
inet xxx.xxx.222.248/32 scope global dum0
valid_lft forever preferred_lft forever
inet xxx.xxx.222.249/32 scope global dum0
valid_lft forever preferred_lft forever
inet xxx.xxx.222.250/32 scope global dum0
valid_lft forever preferred_lft forever
inet xxx.xxx.222.251/32 scope global dum0
valid_lft forever preferred_lft forever
inet6 fe80::743e:ff:fec9:3cd9/64 scope link
valid_lft forever preferred_lft forever
user@myDummyRouter:~$ ip addr show eth2
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:bc:05:ec brd ff:ff:ff:ff:ff:ff
inet 172.23.252.1/24 brd 172.23.252.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:febc:5ec/64 scope link
valid_lft forever preferred_lft forever
Lastly, this is the output from netbox-sync -l DEBUG3
, with what I think might be the relevant info.
(vim.vm.GuestInfo.NicInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
network = <unset>,
ipAddress = (str) [
'xxx.xxx.222.248',
'xxx.xxx.222.249',
'xxx.xxx.222.250',
'xxx.xxx.222.251',
'fe80::743e:ff:fec9:3cd9'
],
macAddress = '76:3e:00:c9:3c:d9',
connected = true,
deviceConfigId = -1,
dnsConfig = <unset>,
ipConfig = (vim.net.IpConfigInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = (vim.net.IpConfigInfo.IpAddress) [
(vim.net.IpConfigInfo.IpAddress) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = 'xxx.xxx.222.248',
prefixLength = 32,
origin = <unset>,
state = 'preferred',
lifetime = <unset>
},
(vim.net.IpConfigInfo.IpAddress) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = 'xxx.xxx.222.249',
prefixLength = 32,
origin = <unset>,
state = 'preferred',
lifetime = <unset>
},
(vim.net.IpConfigInfo.IpAddress) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = 'xxx.xxx.222.250',
prefixLength = 32,
origin = <unset>,
state = 'preferred',
lifetime = <unset>
},
(vim.net.IpConfigInfo.IpAddress) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = 'xxx.xxx.222.251',
prefixLength = 32,
origin = <unset>,
state = 'preferred',
lifetime = <unset>
},
(vim.net.IpConfigInfo.IpAddress) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = 'fe80::743e:ff:fec9:3cd9',
prefixLength = 64,
origin = <unset>,
state = 'unknown',
lifetime = <unset>
}
],
dhcp = <unset>,
autoConfigurationEnabled = <unset>
},
netBIOSConfig = <unset>
},
(vim.vm.GuestInfo.NicInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
network = '12345-CUST',
ipAddress = (str) [
'172.23.252.1',
'fe80::250:56ff:febc:5ec'
],
macAddress = '00:50:56:bc:05:ec',
connected = true,
deviceConfigId = 4002,
dnsConfig = <unset>,
ipConfig = (vim.net.IpConfigInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = (vim.net.IpConfigInfo.IpAddress) [
(vim.net.IpConfigInfo.IpAddress) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = '172.23.252.1',
prefixLength = 24,
origin = <unset>,
state = 'preferred',
lifetime = <unset>
},
(vim.net.IpConfigInfo.IpAddress) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
ipAddress = 'fe80::250:56ff:febc:5ec',
prefixLength = 64,
origin = <unset>,
state = 'unknown',
lifetime = <unset>
}
],
dhcp = <unset>,
autoConfigurationEnabled = <unset>
},
netBIOSConfig = <unset>
}
],
Issue Analytics
- State:
- Created a year ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Network assignment to dummy interface lost after vdsm restart
1. Install vdsm hook /usr/libexec/vdsm/hooks/before_vdsm_start/network.sh ip link add dummy0 type dummy 2>/dev/null /usr/sbin/ifconfig dummy0 hw ...
Read more >Node local DNS creates dummy interface without IP address
Hello, I've just started experimenting with the new node local DNS cache. For reasons I haven't yet determined the NetIfManager manages to ...
Read more >Interface Configuration for IP - Linux Network Administrator's ...
IP Alias allows you to configure multiple IP addresses onto a physical device. In the simplest case, you could replicate the function of...
Read more >IP address not being applied to Sync interfaces and not ...
The MAC address of Sync interface is not being updated because there is no IP address defined on this interface.
Read more >Dummy IP, internal only for LB VS use for netscaler only ...
Getting duplicate IP address messages from other Netscalers, ... But this internal only VIP and SNIP etc. does not have an interface, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi,
Good point. Maybe the missing network is the issue here. Will check if I can add these interfaces as well.
Yes - it seems to work as expected.