we're planning to have a mcast-ix.dn42 somewhere in the cloud at #dn42 for years now…
now we have a pull req with cosmetical issues only: https://git.dn42.dev/dn42/registry/pulls/2572
the whole idea is to consider the following hypervisor configuration:
how to participate:
all you have to do is prepare a qcow2 or vmdk image and upload it to somewhere and ping nop-mnt (mc36 @ irc) with the url… i'll wget it once then boot up your vm connected to the switchport… you'll have raw dn42 reachability there and pat-ed clearnet to continue your installation or upgrades or to connect to the rest of your infra…
only one thing to look for twice, the "console=ttyS0,115200n8" be present as a kernel parameter as there won't be vnc console… maybe i can lift that later….
always save your configs! there will be a daily recurring power cut sheduled to 21:00pm +-1minutes to have the infrastructure auto-upgraded
dn42ix#show startup-config vdc
vdc definition vm-bri
connect ethernet2825 vm-switch
cpu host
image /rtr/ix/bri.img
memory 1024
nic virtio-net-pci
mac cafe.beef.b00b
exit
vdc definition vm-clearnet
local ethernet66602
local ethernet66603
connect ethernet66601 vm-switch
exit
vdc definition vm-jlu5
connect ethernet1080 vm-switch
cpu host
image /rtr/ix/jlu5.img
cdrom /rtr/ix/jlu5.iso
memory 1024
exit
vdc definition vm-lare
connect ethernet3035 vm-switch
cpu host
image /rtr/ix/lare.img
memory 1024
exit
vdc definition vm-nop
connect ethernet1955 vm-switch
exit
vdc definition vm-routeserver
exit
vdc definition vm-switch
connect ethernet1080 vm-jlu5
connect ethernet1955 vm-nop
connect ethernet2825 vm-bri
connect ethernet3035 vm-lare
connect ethernet66601 vm-clearnet
exit
dn42ix# now you can have drop-in replacement vm-s to experiment with like whats it looks a like if the ix is provisioned on a juniper vsrx3 shitload or a cisco nxosv or plain freerouter in software mode or in p4dpdk mode….
then publishing a small report on r/networking on behalf of #dn42 measurements
and probably doing even more crazyer projects/experiment if we settle to have a proper dn42 ix finally with low latency shared vlan between the vms…
like a real ix…
static addressing plan, there is a randomized dhcp and slaac on the subnet but consider picking up a static ip and pere with that:
| nick/mnter | asn* | your-ipv4-fixed-ip | your-ipv6-fixed-ip | your-ipv6-linklocal | public lg |
|---|---|---|---|---|---|
| rtr1-badcorp | 1952? | 172.23.124.97/27 | fde0:93fa:7a0:c1ca::666/64 | fe80::260:54ff:fe33:2178 | TBD: SOON |
| rs1-mcastix | 1951? | 172.23.124.126/27 | fde0:93fa:7a0:c1ca::179/64 | TBD: SOON | TBD: SOON |
| rtr1-nopmnt | 1955 | 172.23.124.122/27 | fde0:93fa:7a0:c1ca::1955/64 | TBD: SOON | TBD: SOON |
| rtr1-catgirls | 1411 | 172.23.124.101/27 | TBD | fe80::1411:5 | TBD: SOON |
| rtr1-laremnt | 3035 | 172.23.124.115/27 | fde0:93fa:7a0:c1ca:21f:45ff:fe11:7356 | fe80::21f:45ff:fe11:7356 | clearnet: https://lg.lare.cc/ dn42: https://lg.lare.dn42/ |
TBD: add yourself please here while keeping some ordering
*: so your as number xxxx shortened here, the rigthmost part after the 424242xxxx…. this also will be your ethernetXXXX and so on so just remember this by heart XD
| function | console |
|---|---|
| switch | telnet ix.nop.dn42 20001 |
| route server 1 | telnet ix.nop.dn42 20002 |
| bad-corp-rtr1 | telnet ix.nop.dn42 20003 |
public config archive of the infra http://ix.nop.dn42/ here
it'll be shitload in the beginning but hopefully it could improve the common knowledge….