This page carries on from MetaNetInstallation, and indirectly from MetaNet. You might want to read those first.

zebra and bgpd

WanDaemon, at low level, provides you with 192.168 addresses. What you want is 10.x.x.x connectivity - so you need to run zebra.

Configuration information is in ZebraConfig. Note: this page may have a slight Debian tint!

Read MetaNetBGPNotes for information describing BGP on the !MetaNet.

At this point you should be able to ping 10.66.10.1, Hydrogen's !MetaNet address.

Routing

Add to your boot scripts somewhere (/etc/network/interfaces is a good place for Debian. Can you tell we love Debian here?)

route add -net 10.0.0.0 netmask 255.0.0.0 reject route add -net 192.168.0.0 netmask 255.255.0.0 metric 1000 reject

This will give you "Destination host unreachable errors", without sending random packets out your default gateway.

DNS

After you have zebra working correctly, and you can ping 10.66.10.1, then you may want to setup DNS (Debian: apt-get install bind). In your name server, you need to make sure you don't have any forwarders1?, and that you have blocks that look much like this

zone "10.in-addr.arpa" {

type stub; masters { 10.66.10.1; }; file "/var/cache/bind/stubs/10.x";

};

zone "tla" {

type stub; masters { 10.66.10.1; }; file "/var/cache/bind/stubs/tla";

};

For future use, and resolving metanet routers, also add

zone "168.192.in-addr.arpa" {

type stub; masters { 10.66.10.1; }; file "/var/cache/bind/stubs/192.168.x";

};

zone "metaix.tla" {

type stub; masters { 10.66.10.1; }; file "/var/cache/bind/stubs/metaix.tla";

};

as well.

Note: You may wish to change the paths based on your distribution. Debian Woody prefers "/var/cache/bind/stubs", but doesn't create it by default. Make sure the directory you have named in the config file exists on the filesystem!

You should then be able to restart named(8) (debian: /etc/init.d/bind restart, or reload if it's already running) and then ping "www.tla".

You are now properly on the !MetaNet. You should now be able to visit http://www.tla/

Other clients on your network

Make sure any clients on your network that you want to resolve !MetaNet addresses have the address of your nameserver as the first nameserver in /etc/resolv.conf, or their native DNS configuration. You can put your ISP's nameserver after it as a precaution, if you like.

Firewalling

see FirewallNotes and PerrysFirewallingScript. Although you should be able to mostly trust other people on the metanet, you should at the very least do some basic firewalling.

For example, samba/nmbd does broadcasts that will go across the metanet. You can either block traffic to and from the metanet on ports 137, 138 and 139 (both TCP and UDP) or you can add the following in smb.conf's global section

bind interfaces only = yes interfaces = 10.x.y.0/24

Root CA

The !MetaNet has a CertificateAuthority? that it uses for signing SSL websites and potentially other cool stuff. To add this "root CA" to your browser, visit http://www.meta.net.nz/install-cert.html

Now, go to MetaNetResources to see what you can do with your new internetwork.

1? The reason is if you use a forwarder, then all queries get forwarded to the other server and it won't be able to resolve metanet names and addresses.