Setting up your Raspberry Pi (headless)

Raspberry Pi Hardware List


Continue reading

Billion 7800N SNMP OID’s

I’ve decided to graph my small home network, so I thought I would see if I could find the OID’s for my Billion 7800n Router, first I tried the Billion website, I was surprised not to find them there. I managed to find some information on other websites (not a huge lot), but it seems that Billion have changed the format of the information between firmware revision.

Billion 7800n SNMP Page

Billion 7800n SNMP Page

Assuming you’ve set up your router and installed snmp tools on your Linux workstation, this command will give you a list of all the OID’s.

If you can’t be bothered to install SNMP tools then feel free to grab the zip file of the results from the following Software Version 1.06e

[code lang=”bash”]snmpwalk -v1 -c public 192.168.1.254[/code]

As it happens, I’ll only be graphing a few of the salient attributes of the router, using either Cacti or Nagios in a home environment.

ADSL Status.

Upstream Speed (Gauge32): .1.3.6.1.2.1.10.94.1.1.2.1.8.3
Downstream Seed (Gauge32): .1.3.6.1.2.1.10.94.1.1.3.1.8.3

Upstream SNR (Integer): .1.3.6.1.2.1.10.94.1.1.2.1.4.3
Downstream SNR (Integer): .1.3.6.1.2.1.10.94.1.1.3.1.4.3

Upstream Line Attenuation (Gauge32): .1.3.6.1.2.1.10.94.1.1.2.1.5.3
Downstream Line Attenuation (Gauge32): .1.3.6.1.2.1.10.94.1.1.3.1.5.3

System Uptime (Timeticks): .1.3.6.1.2.1.25.1.1.0

Interface Statistics.

Ethernet interface eth0
String: “eth0” .1.3.6.1.2.1.2.2.1.2.6
RX bytes (String): .1.3.6.1.2.1.2.2.1.10.6
TX bytes (String): .1.3.6.1.2.1.2.2.1.16.6

Ethernet interface eth1
String: “eth1” .1.3.6.1.2.1.2.2.1.2.7
RX bytes (String): .1.3.6.1.2.1.2.2.1.10.7
TX bytes (String): .1.3.6.1.2.1.2.2.1.16.7

Ethernet interface eth2
String: “eth2” .1.3.6.1.2.1.2.2.1.2.8
RX bytes (String): .1.3.6.1.2.1.2.2.1.10.8
TX bytes (String): .1.3.6.1.2.1.2.2.1.16.8

Ethernet interface eth3
String: “eth3” .1.3.6.1.2.1.2.2.1.2.9
RX bytes (String): .1.3.6.1.2.1.2.2.1.10.9
TX bytes (String): .1.3.6.1.2.1.2.2.1.16.9

Wireless interface ra0
String: “ra0” .1.3.6.1.2.1.2.2.1.2.8
RX bytes (String): .1.3.6.1.2.1.2.2.1.10.8
TX bytes (String): .1.3.6.1.2.1.2.2.1.16.8

Bridge interface br0
String: “br0” .1.3.6.1.2.1.2.2.1.2.9
RX bytes (String): .1.3.6.1.2.1.2.2.1.10.9
TX bytes (String): .1.3.6.1.2.1.2.2.1.16.9

Enabling IPv6 privacy extension on Ubuntu Desktop 10.04

The IPv6 standards define an algorithm to generate temporary random IPv6 addresses that are less traceable over time. This is documented in RFC 4941 “Privacy Extensions for Stateless Address Autoconfiguration in IPv6”. The following instructions apply to a network card called eth0, if your is different, then change to suit.

To enable the use of Privacy Extension under Ubuntu and other Debian derivatives, you need to edit the following. Continue reading

Setting up IPv6 radvd and dibbler to work together on Ubuntu 10.04

Unfortunately a lot of devices don’t pass on RDNS information from radvd  even though it’s included in the RFC. The best it can do is a default gateway and an IPv6 address. You are supposed to be able to pass RDNS information, but I’ve found that the devices that I’ve tried (Windows 7 and Android Gingerbread, still don’t support that part of the Request for Comment) hence the use of DHCPv6.

Continue reading

Making outgoing IRC DCC work with NAT and XChat

This is basically a reminder to myself in case I need to set this up again, if you want to do this for more than one PC behind a NAT firewall-router, then you will of course have to use a different port range for each PC. I’m using 20 ports per PC so that I can have 20 simultaneous connection.

I’m making the assumption that your router has the ability to create a virtual servers (an inbound port range that can map to an Internal Class C Private address range). I’ve called the Virtual server below “DCC Chat Workstation”, since workstation is the hostname of my main PC (original ehh). I’ve also given it an internal and external port range of 54000 to 54019, to be forwarded to the IP address of my Workstation.

Virtual Servers

On my workstation I start the XChat IRC client, select Settings –> Preferences –>File Transfer and change the First DCC send port to 54000 then change the Last DCC send port to 54019. That will give you 20 ports to play with. Also select (tick) “Get my address from the IRC server”.

XChat - Preferences

All done. 😀

If you happen to run iptables or similar on your linux/unix box, then remember to allow the port range listed above access. If like me, your running ufw on ubuntu then the command is

sudo ufw allow proto tcp from any to any port 54000:54019

Reference:
Making outgoing IRC DCC work with NAT