Added additional check before cycle.

I agree. Users should be able to change the port independently from the address.

Fix for the problem:
https://github.com/vyos/vyos-1x/pull/160
https://github.com/vyos/vyos-replace/pull/4

Due to some internal logic in net-snmp this can not be done so easy.

PR for CLI https://github.com/vyos/vyos-1x/pull/159

pending review: https://github.com/vyos/vyos-build-kernel/pull/1

If someone can confirm I'm linking to the correct github repo (there are two cloud init ones under vyos), I could submit a pull request for this. @syncer, @Unicron?

PR #158 https://github.com/vyos/vyos-1x/pull/158

Complete

To fix this inconsistancy the output of show int ethernet | json should be:

{
       "eth0": {
            "address": "10.10.10.10/24"
        }
}

PR #26 https://github.com/vyos/vyatta-cfg-vpn/pull/26

PR: https://github.com/vyos/vyos-1x/pull/156

PR #38

@xrobau WOW! What a bisection and research on that problem! Thanks a lot!

On the old image, the macs are set correctly

OH. MY. GLOB. I just figured it out.

This appears to be a bug in that intel driver - there's people reporting the same issues here: https://sourceforge.net/p/e1000/bugs/649/

This is getting more and more crazy the more time I spend on it, as this is a niggly issue that shouldn't be this hard to figure out.

Oh, just to emphasize that it's a startup-config issue, if I disable and re-enable the ethernet port in the switch, it is still broken. The only way to get it working is to delete the member, commit, and re-add the member inside vyos.

While it was booting, it responded to three pings, and then nothing

It looks like the problem occurs when both interfaces are present when the machine boots. I can remove either one, reboot the machine, and it works.

Working 1.2.0-rolling config (with the different bonding syntax)

1.2.0 complete bond0 output

Whats happening here is that the non-commit-able session is saved to disk. because of this BGP will fail on reload because of illegal configuration on the peer. What needs to be done here is to disallow the save command when there are non-commited work in the session.. or at least give a clear warning about this with a [y/N] answer. is this possible to incorporate into vbash? @dmbaturin

Looks like there is a missing priority statement in the VIF implementation.

PR: https://github.com/vyos/vyos-1x/pull/149

Pull request raised for review with effective fix proposed.
https://github.com/vyos/vyos-1x/pull/147

Agree with you, thank you. We need fixed these moments.

Unfortunately it doesn't work without gw-ip-address also in [chap-secrets]. In my early trials I've tried that, and the clients received IP's from the pool instead the static values.

I think better calculate gw-ip-address automatically. outside-nexthop excluded from required for migration reasons.
Not necessary define gw-ip-address in [chap-secrets] section, it works without any issue if defined it in [ip-pool] only.

@Dmitry Thanks for pointing that out, I've looked on the wiki (https://wiki.vyos.net/) and searched for a description for outside-nexthop, and failed to find it, and the in-line help while configuring doesn't help much.

You can set outside-nexthop which fixed this. Also I think we can calculate first ip for gw-ip-address if outside-nexthop is not defined by cli.