Merged in october.

Can't move this forward, since don't have idea what is needed
if there are candidates, you can pickup thisk task

Can't move this forward, since don't have idea what is needed
if there are candidates, you can pickup thisk task

Well, than it seems to me that the reasonable starting idea is to start with the following configuration:

1. make tree-like control pane topology on some stupid switch, for example.
2. make "basic" configuration for every device, where only control pane interfaces are up and running
3. make your jenkins or some other automated tool able to upload configuration into all these devices.
4. make full-graph cabling between existing devices with some reasonable background logic

(e.g. "port 1 of any device always goes to hp,
port 2 of any device always goes to srx240
port 3 of any device always goes to ASA
port 4 always goes to Mikrotik)

If you can do a cocktail napkin sketch, I'd be happy to put it into Visio.

@mickvav i don't
we talked with @dmbaturin several times how to organize it,
but actually not came across any exact decision yet
We have
1 hp switch
1 srx240
1 ASA
1 Mikrotik

@syncer , do you have any drawing on network topology, that you are going to implement? If you do and it's not a secret, please share.

Hello Guys!
Today we finally installed fiber optics to the office where lab will reside.
I will start connecting devices with @dmbaturin this days,
so if you have any ideas, advises, comments, etc
Please tell!

@UnicronNL here is some photos

Hey guys,
@AG will send us some more devices
2x SRX210 HE
1x EX4200-24T
Here is how it looks now
https://www.icloud.com/sharedalbum/#B0aGzFCC1GnDn11

@kostiantyn can we setup CSR 1000v for our lab?
I also working to get NSX up and running, apart from that i will get some virtual ASA and MikroTik
not sure if we should take other Linux based solutions like untangle, and of course pfSense

Hello,
@cycloptivity your postage arrived a week ago!
So we now finished with preparation of physical location

Ok,
so i bought a rack and already prepared place
should get the connection in upcoming days
we with @dmbaturin investigating how to get some Xena Networks appliance for testing purposes, this should be very useful
devices from @cycloptivity also on the way.
@UnicronNL i will connect this three clearfogs there too for testing(i hope they will do som with network offload in future)
I have also old workstations which should boot Citrix XenServer just fine

Would be great - with some make target for this it's possible to arrange nightly builds with these images.

For kernel 4.4 yes,

Hm, looks like it has 1gbe port working, am I right?
Do you have your .img creating procedure described or scripted somewhere?

Here i have put the info for the clearfog.

@mickvav kind of
@UnicronNL share current state please!

You mean, I can order a board, take sd, put some image onto it and get working vyos on this board?

@mickvav is more then idea now thanks to @UnicronNL :)

Well, you was discussing hardware here, and I know that mikrotiks used to be bootable into debian, so I've concluded that you are planing to port vyos on mikrotik's hardware. But clearfrog is also interesting idea.

@mickvav there is no mikrotik port, sorry for confusing you.
or you mean clearfog port?

Is there some place, where you track current work on mikrotik port? May I help it somehow?

@UnicronNL not sure if it will be hard adapt boot from MMC instead of sd

Sounds like things are coming together. I haven't sent the kit yet but if there is an existing switch it might be cheaper to just send over the SRX110 and Cisco 877 rather than a 24 port switch too?

@syncer How can i help with the clearfog?

Looks like this simple patch is ready for production. Backing idea - quagga has route-map to filter routes, going to be installed from ospf into kernel table, but we had no way to install it in vyos config. This patch creates 'router ospf route-map NAME' vyos configuration command, which maps into 'ip protocol ospf route-map NAME' quagga configuration mode command. The development was discussed under Q26.