As this kind of important topic is in the backlog since quite some time, I would like to ask if one of us "non-devs" could help somehow to get the feature implemented?

I have had a chance to look at this again and believe we can get what we want from /var/log/Vyatta/ppp_pppoe0.log

Netplugd seems to be the thing we want

I don't think That I use netplugd for now. I have just a check in the script how an address had been setup on the system, if it's been dhcp then I send a release (suspend doesn't do that) and a new dhcp request. I have to chat with @c-po about T894 first.
If netplugd is being introduced to the OS, I can simply remove an else clause.

Will you then use the netplugd way mentioned in T894 or also issue a dhcp renew in the resume vmware script? I prefer the netplug way as this also fixes issues when you switch network. I can imagine we want to avoid double renewing.

I will add the dhcp functionality too. The problem is that the network config is very different from the approach within the OS and additional software is written the way to work with whatever has the OS, it doesn't know about vyos and it's cli etc.
Thanks for testing, I will integrate the dhcp functionality asap and see that I can quickly get it into the rolling branch.

@hagbard I tested the script, it works perfect for interfaces with static addresses. However interfaces with "dhcp" remain without an ip address after resuming. This is caused by the following issue I reported: T894

In addition, when trying to delete these entries from the configuration

The problem is still present.

Bug confirmed, I can reproduce it. I can't tell you how long it takes to fix it, it's all old code base.

Hey @yun, could you test it under vmware, I just used the scripts to trigger resume and suspend.

I can test on Saturdays when our maintenance window is open btw.

Could you please do it via: 'show config command'. thx.

below is a crude paste with IP's changed. If you want the original config then I will share it privately. just can't have it out in the open. tx

Ok, so I think I know how to attack that. either we use the tools then from debian directly and add an extra package with the user scripts, ot we do it directly in the tools package which is forked anyway. I would personally lean torwards option 2, since debian would take care of patching.

@Barrysdca Can you please share your config? At least the tunnel parts.

you can test it in the rolling release of Dec 7th. or manually install http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-vpn/vyatta-cfg-vpn_0.12.105+vyos2+current4_all.deb. Please let me know if it works like expected.

We got a little bit similar situation with Ubnt ERLite and VyOS 1.1.7, sometimes it loose all routes...
Reboot of both routers solve it... (but it tookes much more then 30 min)

Just to confirm, still a problem with RC10

when trying to run the commands in rc10 the following error occurs

Update for everyone - I built out an exact replica of my lab on a single Hyper-V host with a single internal vSwitch connecting all interfaces (similar, in principle at least).