@UnicronNL can you add

@UnicronNL or better add this to installer part

Assuming that 1.2 affected in same way,
moving it to 1.2 and suggest work on fix there

@dmbaturin now as we have bugzilla back, can you check this one ?

Moving this to 1.2 than.
Let's fix it there

Will recommend retest with 1.2 nightlies

@EinHander can you confirm same behaviour on 1.2 ?

Please use transition scripts as suggested by @aopdal
Moving this to 1.2 roadmap

Here is patch:
diff --git a/bgpd/bgp_aspath.c b/bgpd/bgp_aspath.c

Comment by @beamerblvd on 2016-01-24:

The above completes the migration of content and all comments for Bugzilla issue 112.

Comment by Daniel Corbe on 2016-01-12:

Comment by Brett Lykins on 2015-09-28:

Comment by Jason Nadeau on 2015-09-27:

Comment by Patrick van Staveren on 2015-09-25:

Comment by Jeremy Church on 2015-08-24:

Comment by Steve Froelich on 2015-08-21:

Comment by Aaron Von Gauss on 2015-05-03:

Comment by @dmbaturin on 2015-05-03:

Comment by @darkdragon-001 on 2015-04-19:

Comment by Aaron Von Gauss on 2015-03-27:

Comment by Kouak on 2015-03-18:

Comment by @beamerblvd on 2015-03-06:

Comment by Kouak on 2015-03-05:

Comment by @beamerblvd on 2015-03-05:

Comment by @beamerblvd on 2015-03-03:

Comment by @dmbaturin on 2014-10-07:

Comment by Ryan Holt posted on 2014-09-02:

waagent log

my azure image works on azure too. the image is here: https://dev.vyos.jp/vyos/dev-images/vyos_azure_image.img
and walinuxagent is running on it. I'm checking walinuxagent status.

https://www.reddit.com/r/networking/comments/75c30y/create_a_static_public_ip_address_for_home_use/

BusyBox is a multi-call binary. A multi-call binary is an executable program that performs the same job as more than one utility program. That means there is just a single BusyBox binary, but that single binary acts like a large number of utilities. This allows BusyBox to be smaller since all the built-in utility programs (we call them applets) can share code for many common operations.

+1 for removal of telnet

Well, I think that if someone has a system with only telnet as a remote access method, it could be anoying to update and realize that you have lost any chance to remote access.
I vote to maintain or add a script that convert telnet to ssh configuration.

+1 for removal

Well, may be we just have to either:

If you have a lab to try - may be you can just copy

As VyOS fully re-uses Debian packages it is not possible to enable any given applet inside Busybox. To get this enabled, VyOS has to maintain a forked version of the Debian busybox packages which makes life only harder.

@UnicronNL please add package
https://packages.debian.org/search?keywords=wakeonlan
This is client tool (to wake up servers/hosts) we will be adding op mode command for it

added jessie one. https://github.com/vyos/dnsmasq
need to test in 1.1.8 rc1

@UnicronNL @dmbaturin
can we just rebuild fresh from wheeze?

@dmbaturin @syncer Where can i find the lithium repo?

Fixed 1, 2, and 3.

Virtualization would work fine. The daemon/server LCDd is just code, and can be configured to run a nCurses "driver". Some other drivers only do parallel port stuff so would do nothing in a virtual environment. Other drivers do serial port and I suppose the data stream could be monitored. The clients (lcdproc, lcdexec, etc) are just programs that push data to LCDd over TCP.

Is there any possibility to test this functionality in some kind of virtualized environment? Or the developer has to own an appliance with lcd screen to check this things?

Hello, is there a way to easy install kernel source/headers for default kernel used by vyos 1.1.x (3.13.11-1-amd64-vyos)?

So it looks like vpp progressing a bit.
https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP

Awesome! Raised https://github.com/vyos/vyatta-cfg-quagga/pull/16

@dmbaturin @pmoust there is a CLI implementation already!

It's great that it landed in quagga! Really looking forward to the CLI implementation for VyOS.

Thank you.
It looks like you have this compiled to much newer kernel, 4.4.15 while current kernel in VyOS 1.1.7 is 3.13.11-1-amd64-vyos.
So it looks like i need to compile it by my own, but thanks anyway for sharing this ;)

Here you are -

Ups, seems I was wrong in last comment. I'll collect all the files from .deb and post them here.

Well, I don't have access to development vm, where I did this stuff today (remind me on monday, please), but I do have kernel module (the only file in .deb, actually) compiled against 4.4.15-amd64-vyos kernel.

Hello,
Is there a chance that ipt_NETFLOW will be included in next release (and if yes, where it is planned to release this version?)
@mickvav Can you share your .deb package please? We need ipt_NETFLOW ASAP. Thanks

In T375#7897, @p10003 wrote:

So one other tiny thing you might try since you have 192.168.0.1/24 (eth0) but different 192.168.192.0/24 (nats).

If all hosts are really in .192. and no other routes or L3 device exists just update that eth0 entry.

Making the next step: Confirm .0. is not typo and draw us the bigger picture, or stick an interface in .192. on the vyos box.

So one other tiny thing you might try since you have 192.168.0.1/24 (eth0) but different 192.168.192.0/24 (nats).

In T375#7874, @p10003 wrote:

Hey Rob,

Might be handy to post:
sh nat
sh system conntrack modules sip

sip
disable/enable-indirect-media/enable-indirect-signalling

Hey Rob,

we actually need clean up grup config a bit
as it have 2 timers for 5 seconds and it's kind of annoying

@syncer @dmbaturin @UnicronNL is there any reason to not implement this? I think this should be doable in less then two hours.