Difference between revisions of "Wireless Antwerp"

From Whitespace (Hackerspace Gent)
Jump to: navigation, search
(No difference)

Revision as of 12:15, 14 October 2011

Initial config

Since the installation of the Wireless Antwerp access-point on the Belgacom tower we now have line of sight to this wireless network.

To make the connection we have a NanoStation M5. This is installed in the far corner of the slightly higher part of the roof of our building. Power is supplied through POE. The POE cable must be connected to the port on the NanoStation labelled main. The NanoStation can be configured through a web-interface.

The link to Wireless Antwerpen on the roof is now live. We have a policy
routing setup where addresses in 10.97.212.0/24 range automatically go out
via the WA link, and everything else via the regular Dommel link. You can
reach machines in the WA internal network from the regular LAN range,
however this still needs a bit of tuning.

Addresses in that new range are not yet given out by the DHCP server, but
they will be as soon as we get this set up. The idea is that we'll put
"known" MAC addresses (see Pamela) in the Dommel range, and visitors get on
the WO link. So we'll also be doing a "guest" WIFI network for this. Of
course, you can give yourself an IP address in this range (.1 is the soekris).

The dn42 link is down. The quagga on the soekris cannot handle BGP in more
than one AS, and both dn42 and WA need us to use specific ASNs. If anyone
still needs dn42, a fix will need to be found.

It's all a bit much for the soekris... we really need to replace it with
something that has 1) more CPU, and 2) more ports. We'll need a minimum of 4
ethernet ports. This will require some investment though.

configuration

Username/Password: ubnt/ubnt
SSID: wirelessgent-bgc5

Setup

  • there is a custom init script at /etc/init.d/extra-networking
do_start()
{
        # extra /30 on the soekris, for management of the AP on the roof
        # remove this, and it won't be able to proxy-arp for the /24
        ip addr add 10.97.255.169/30 dev eth2

        # configure the WA table
        ip route add 0.0.0.0/0 via 10.97.255.173 dev eth2 table wa

        ip addr add 10.97.212.1/24 dev eth0
        ip rule add from 10.97.212.0/24 table wa

        return 0
}

#
# Function that stops the daemon/service
#
do_stop()
{
        ip rule del from 10.97.212.0/24 table wa
        ip addr del 10.97.212.1/24 dev eth0

        ip route del 0.0.0.0/0 via 10.97.255.173 dev eth2 table wa

        ip addr del 10.97.255.169/30 dev eth2

        return 0
}
  • ip (instead of ifconfig) is your friend:
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:00:24:c8:99:cc brd ff:ff:ff:ff:ff:ff
    inet 172.22.32.14/24 brd 172.22.32.255 scope global eth0
    inet 10.97.212.1/24 scope global eth0
    inet6 fe80::200:24ff:fec8:99cc/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:00:24:c8:99:cd brd ff:ff:ff:ff:ff:ff
    inet 83.101.72.80/24 brd 83.101.72.255 scope global eth1
    inet6 fe80::200:24ff:fec8:99cd/64 scope link
       valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:00:24:c8:99:ce brd ff:ff:ff:ff:ff:ff
    inet 10.97.255.174/30 brd 10.97.255.175 scope global eth2
    inet 10.97.255.169/30 scope global eth2
    inet6 fe80::200:24ff:fec8:99ce/64 scope link
       valid_lft forever preferred_lft forever