Pseudo-ethernet, not behaving like ethernet

Hi there,

I’m trying to get rid of most of my NAT as it’s not needed.

My traffic is hitting, which is the VyOS, from EdgeOS side but is not getting routed out of peth0 for whatever reason and if I try to use eth0 as the outgoing one, it will work.

Config for vyOS:

Related routing table:

$ show ip route table 26
Codes: K - kernel route, C - connected, S - static, R - >RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
F - PBR, f - OpenFabric,
-selected route, * - FIB route, q - queued route, r - rejected route
VRF default table 26:
S [1/0] via xxxx.xxxx.64.65, peth0 inactive, 00:33:24

Hi @samip537, this is very strange why this route is inactive. Can you reach some host via peth0? I can’t reproduce this in my LAB with latest rolling version.
PS:/ maybe typo in addresses/mask, but I can’t see this for masking reason.


I don’t know why but for some reason I had to re-create the interface, and mess with routing tables to get it active first. Then I had forgot some PBR rules, after which it started to work like it should have.

P.S It indeed did not work to ping out of the interface.
P.P.S I was unable to change the pseudo-ethernet mode without re-creating it, is that intended behavior?

Current working configuration:

Hi, if you receive a message about it, that yes.

Is this intended?

vyos@<host># set interfaces pseudo-ethernet peth0 mode passthru
vyos@<host># commit
[ interfaces pseudo-ethernet peth0 ]
VyOS had an issue completing a command.

We are sorry that you encountered a problem while using VyOS.
There are a few things you can do to help us (and yourself):
- Make sure you are running the latest version of the code available at
- Consult the forum to see how to handle this issue
- Join our community on slack where our users exchange help and advice

When reporting problems, please include as much information as possible:
- do not obfuscate any data (feel free to contact us privately if your
  business policy requires it)
- and include all the information presented below

Report Time:      2020-06-22 12:27:40
Image Version:    VyOS 1.3-rolling-202006200117
Release Train:    equuleus

Built by:
Built on:         Sat 20 Jun 2020 01:17 UTC
Build UUID:       29ee53d5-c062-4506-abe7-5e1da5c2f304
Build Commit ID:  5fc9c378b67c42

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest

Hardware vendor:  QEMU
Hardware model:   Standard PC (i440FX + PIIX, 1996)
Hardware S/N:
Hardware UUID:    947dfcd3-3192-45e9-bc4e-898ceb9145c0

Traceback (most recent call last):
  File "/usr/libexec/vyos/conf_mode/", line 257, in <module>
  File "/usr/libexec/vyos/conf_mode/", line 227, in apply
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/", line 58, in set_mode
    return self._cmd(cmd)
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/", line 48, in _cmd
    return cmd(command, self.debug)
  File "/usr/lib/python3/dist-packages/vyos/", line 179, in cmd
    raise OSError(code, feedback)
FileNotFoundError: [Errno 2] failed to run command: ip link set dev peth0 type macvlan mode passthru
exit code: 2

cmd 'ip link set dev peth0 type macvlan mode passthru'
returned (out):

returned (err):
RTNETLINK answers: Invalid argument

[[interfaces pseudo-ethernet peth0]] failed
Commit failed

Hi @samip537, exactly no. Please, create a bug report on and describe reproducing steps.

1 Like