Testing on crux
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Sep 26 2020
That’s how it is now and it doesn’t work.
vyos@r2-roll# set interfaces ethernet eth0 vif 15 ip proxy-arp-pvlan [edit] vyos@r2-roll# commit
Cant we run dhcpd as dhcp user which is also a member of hostsd group?
@kroy could you be so kind and write a smoketest for it, too?
This is a problem again.
Sep 25 2020
PR should correct this
cpo@LR1.wue3# commit [ interfaces ethernet eth1 ] Interface MTU too high, maximum supported MTU is 9000!
Yes that's correct. And there is already some sort of check implemented for the node traffic-policy, so it does not fail when the pppoe interface does not exist yet. It just shows a warning: https://github.com/vyos/vyatta-cfg-qos/blob/bbf2b2f06b7a0f883f7134df5e2b3e089015738e/scripts/vyatta-qos.pl#L198
I think I know what's happening here.
I would also like to add that wouldn't it make more sense to set the protocol mode under host aswell rather behind "facility".
Sep 24 2020
I saw that the new build was online, so I added the image, rebooted and tried to issue the command again.
Everything seems to work, no error when committing and the route is added.
After the fix an error is reported on the CLI:
Also come back to this question?
In linux kernel version 5.8 and above, you can start symmetric translation of ipv6 address prefix by changing snat to to snat prefix to in the policy (without changing the interface identifier), but this function cannot be used before vyos upgrade 5.9 , This patch is not a back-portable patch, so this feature cannot be used in 4.19. There are now 3 solutions:
Sep 23 2020
So I was super lucky to pick the wrong characters!
The problem with that expression
https://github.com/vyos/vyatta-cfg-system/blob/current/scripts/install/install-image-existing#L271
Additionally, it only happens after a system image upgrade - it doesn't seem to happen if you reboot again after that.
For testing