Page MenuHomeVyOS Platform

static-host-mapping writing in one line
Closed, ResolvedPublicBUG

Description

All host mapping is writing in one line.

set interfaces dummy dum100 address '10.0.10.100/32'
set interfaces dummy dum100 address '10.0.10.101/32'
set interfaces dummy dum100 address '10.0.10.103/32'
set system static-host-mapping host-name test1 inet '10.0.10.100'
set system static-host-mapping host-name test2 inet '10.0.10.101'
set system static-host-mapping host-name test3 inet '10.0.10.103'

File hosts

vyos@r12:~$ cat /etc/hosts
### Autogenerated by VyOS ###
### Do not edit, your changes will get overwritten ###

# Local host
127.0.0.1       localhost
127.0.1.1       r12
# The following lines are desirable for IPv6 capable hosts
::1             localhost ip6-localhost ip6-loopback
fe00::0         ip6-localnet
ff00::0         ip6-mcastprefix
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

# From 'system static-host-mapping' and DHCP server
# system
10.0.10.100	test110.0.10.101	test210.0.10.103	test3vyos@r12:~$

Incorrect record And test3 host mapping wrong

vyos@r12:~$ ping test1
ping: Unknown host: test1
vyos@r12:~$ 
vyos@r12:~$ ping test2
ping: Unknown host: test2
vyos@r12:~$ 
vyos@r12:~$ ping test3
PING test110.0.10.101 (10.0.10.100) 56(84) bytes of data.
64 bytes from test110.0.10.101 (10.0.10.100): icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from test110.0.10.101 (10.0.10.100): icmp_seq=2 ttl=64 time=0.038 ms

Details

Difficulty level
Easy (less than an hour)
Version
VyOS 1.3-rolling-202012010217
Why the issue appeared?
Implementation mistake
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Event Timeline

maybe it happened after that commit https://github.com/vyos/vyos-1x/commit/c87ad948999c28c3c9449f98d60b545481ea29d5
because it was work in VyOS 1.3-rolling-202011250217

c-po changed the task status from Open to Needs testing.Dec 3 2020, 6:59 AM
c-po triaged this task as High priority.
c-po changed Difficulty level from Unknown (require assessment) to Easy (less than an hour).
c-po changed Why the issue appeared? from Will be filled on close to Implementation mistake.
c-po changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
erkin set Issue type to Bug (incorrect behavior).Aug 29 2021, 12:08 PM
erkin removed a subscriber: Active contributors.