15: eth1.100@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000
link/ether 00:0d:b9:53:07:ed brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 scope global eth1.100
valid_lft forever preferred_lft forever- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Apr 11 2020
Apr 10 2020
on-demand dialing and VRFs are now mutually exlcusive. As VRF is a new feature of 1.3 this won't break existing 1.2 LTS devices.
Moved to vif-c
Apr 9 2020
What you mean by "bindable"?
the Problem comes with the connect-on-demand option. As the default route setup was changed some days ago by me to support PPPoE for VRFs this introduced a regression (T2219).
Apr 8 2020
I can't reproduce it with the code in the rolling image that will be available by tomorrow.
Can you please share your configuration on the pppoe interface with us?
Re-assigning to @Dmitry after checking with him as he's more experienced here.
Where do I get the local address from? Can you share your complete config? Maybe we need source-address or something similar in CLI.
Yes - there are some parts which make use of this bad practice (mostly introduced by me), cleanup required.
Apr 7 2020
Apr 6 2020
@Dmitry maybe you have an idea why?