Is it me, or is there a bug in "show interfaces pppoe" latest rolling

Bugs
1

Hi All,

Not sure if it’s something I’ve done wrong, it’s my first step into rolling after using 1.1.8 as my home router for quite a while.

vyos@vyos# run show system image
The system currently has the following image(s) installed:

1: 1.3-rolling-202004221717 (default boot)

[edit]
vyos@vyos# run show interfaces pppoe pppoe0
usage: show_interfaces.py [–intf INTF] [–intf-type INTF_TYPE]
[–action ACTION] [–vif] [–vrrp] [–help]
show_interfaces.py: error: unrecognized arguments: pppoe
[edit]
vyos@vyos# show interfaces pppoe pppoe0
authentication {
password xxxxxxxx
user xxxx@xxxx
}
default-route auto
firewall {
in {
name OUTSIDE-IN
}
local {
name OUTSIDE-LOCAL
}
}
mtu 1492
source-interface eth0
[edit]

Can anyone point me in the right direction, please.

I’m presuming it’s whatever is calling show_interfaces.py that needs attention.

Cheers,
Keith.

3

You hit a bug following a change I performed. Do you want to share your configuration so I can reproduce ?
In the meanwhile I will try to see if I can find what happened.

4

Hi Thomas,

Would you like the whole config, or just the PPPOE Bit?

I shared the pppoe fragment in my original post, but I guess you could need more :slight_smile:

Here are the commands I used to setup pppoe.

set interfaces pppoe pppoe0 mtu 1492
set interfaces pppoe pppoe0 authentication user ‘mr@fred’
set interfaces pppoe pppoe0 authentication password ‘bloggs’
set interfaces pppoe pppoe0 source-interface ‘eth0’
set interfaces pppoe pppoe0 firewall in name OUTSIDE-IN
set interfaces pppoe pppoe0 firewall local name OUTSIDE-LOCAL

If you need the whole config I’ll have to spend some time making sure I’m not sharing anything that I shouldn’t, security wise.

Cheers,
Keith.

5

ok. I have a patch pending for this:
pppoe: T2223: report the state of pppoe intf by thomas-mangin · Pull Request #373 · vyos/vyos-1x · GitHub once merged you should be able to fetch a new image with the fix.

6

Many thanks Thomas,

Really appreciate the super quick fix. :slight_smile:

Excuse my ignorance, I’m new to modern development and code control, but how long before an image with the fix is available?
Would it be in tonight’s build or does it have to wait for a merge activity first.

Cheers,
Keith.
Must look at setting up a build environment!

7

The image name has YYYYMMDDD as a prefix … Anything after today’s date will have it. Not sure when the next image build will be. You can check tomorrow :slight_smile:

8

Many thanks Thomas, latest build installed and working fine.
The pppoe0 interface has come up and I can see the status.

I’m slightly puzzled that nothing is logged, even though the interface has just come up, but there again, I’ve never checked the log option before.

vyos@vyos:~$ show interfaces pppoe pppoe0
pppoe0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN group default qlen 3
link/ppp
inet 1.2.3.4 peer 1.2.3.5/32 scope global pppoe0
valid_lft forever preferred_lft forever

RX:   bytes  packets  errors  dropped  overrun       mcast
     140128     3161       0        0        0           0
TX:   bytes  packets  errors  dropped  carrier  collisions
        206        5       0        0        0           0

vyos@vyos:~$ show interfaces pppoe pppoe0 log

vyos@vyos:~$ ls -al /var/log/vyatta/ppp_pppoe0.log
-rw-r–r-- 1 root root 0 Apr 24 2020 /var/log/vyatta/ppp_pppoe0.log

I’m used to version 1.1.8, so maybe I need to turn this logging on, I’ll check.

Cheers,
Keith.