[ixpmanager] AS112

[Diarmuid O Briain]

Frank,

Thank you, that is very helpful indeed. I guessed that it would be similar
to the same line in my primary nameserver "*db.netlabsug.tst" *zone file.

"@    IN   SOA    ns1.netlabsug.tst. root.netlabsug.tst. ("

what I am wondering is how these two nameservers are interacting in any way
as a result.

regards,

Diarmuid

--

*Irish by birth, located in Uganda but Munster by the grace of God.*



On 27 February 2018 at 07:34, Frank Habicht <geier at geier.ne.tz> wrote:

> Hi Diarmuid,
>
>
> server.example.net -> primary-auth-ns.uixp.co.ug
> (with left-most part your real hostname)
>
> admin.example.net -> diarmuid.obriain.com
> (DNS admin's email with '@' -> .
> [and any . before that masked with \])
>
>
> the interesting parts of my BIRD config for AS112
>  (not yet on the IXP LAN)
>
>
>
> router id 196.49.5.19;
> listen bgp address 196.49.5.19;
>
> filter allow_as112_prefix {
>         if net = 192.175.48.0/24 then accept;
>         if net = 192.31.196.0/24 then accept;
>         else reject;
> }
>
> protocol kernel {
>         persist;           # Don't remove routes on bird shutdown
>         scan time 20;      # Scan kernel routing table every 20 seconds
>         import none;       # Default is import all
> }
> protocol device {
>         scan time 10;           # Scan interfaces every 10 seconds
> }
> protocol static {
>         route 192.175.48.0/24 blackhole;
>         route 192.31.196.0/24 blackhole;
> }
> protocol bgp {
>         description "AS112";
>         local as 112;
>         neighbor 196.49.5.17 as 327844;
>         source address 196.49.5.19;
>         export filter allow_as112_prefix;
> }
>
>
> Probably a bad example as it's not on the peering LAN and you probably
> want a template and many 'protocol' (neighbors)
>
> I think it's all unrelated to IXPManager, and maybe within the
> IXPManager standard setup there are better ways (scaling AS112?).
>
> Frank
>
>
> On 2/26/2018 11:13 PM, Diarmuid O Briain wrote:
> > Hi,
> >
> > When setting up the "db.hostname.as112.net
> > <http://db.hostname.as112.net>" file in BIND9.
> >
> > regarding this line
> >
> > "@       SOA     server.example.net <http://server.example.net>.
> > admin.example.net <http://admin.example.net>. ("
> >
> > What should I be setting "server.example.net
> > <http://server.example.net>." and "admin.example.net
> > <http://admin.example.net>." ? The DNS of the IXP ? RFC7534 doesn't give
> > away much on this. It simply says "the data should be edited to suit
> > local circumstances". Does this setting have any impact on the servers
> > operation?
> >
> > Secondly, is there a BIRD equivalent configuration for the Quagga
> > configurations in RFC7534 p8,9. I would like to look at it before IXP
> > Manager starts putting its configuration onto the AS112 Server.
> >
> > regards,
> >
> > Diarmuid
> >
> >
> >
> >
> >
> > --
> >
> > */Irish by birth, located in Uganda but Munster by the grace of God./*
> >
> >
> >
> >
> > _______________________________________________
> > INEX IXP Manager mailing list
> > ixpmanager at inex.ie
> > https://www.inex.ie/mailman/listinfo/ixpmanager
> >
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/listinfo/ixpmanager
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20180227/4d4a6e2c/attachment.html>