use Human::Brain

Tue, 29 Sep 2009

Bad Robot

Building on the example script in AnyEvent::XMPP I built a small robot which can send messages to either an individual user or a jabber chat room, from either stdin or a fifo. We use this at work to get alerts into a chat room we use for support activities.

Update: a more complex solution is used as the main driver for xmpp-agent.pl in CCNQ2.0

posted: 9/29/2009 03:17:00 AM

permanent link

Mon, 28 Sep 2009

Huawei E160E (Orange 3G+) on Debian Lenny
As seen on the Internet:

# /etc/chatscripts/orange
ABORT BUSY
ABORT "NO CARRIER"
ABORT VOICE
ABORT "NO DIALTONE"
ABORT ERROR
'' ATZ
# Check SIM pin should return ready
OK-AT-OK 'AT+CPIN?'
## OK-AT-OK 'AT+CPIN="...."'
OK-AT-OK 'AT+CGDCONT=?'
OK-AT-OK 'AT+CGATT=?'
OK-AT-OK 'AT+CGREG=?'
# Verify we are connected to a network (will show the network name)
OK-AT-OK 'AT+COPS?'
OK-AT-OK 'AT+CGDCONT=3,"IP","orange.fr"'
OK-AT-OK 'AT&FE0Q0V1'
OK-AT-OK 'ATD*99***3#'
CONNECT ""

and

# /etc/ppp/peers/orange
noauth
connect "/usr/sbin/chat -v -f /etc/chatscripts/orange"
debug
/dev/ttyUSB0
user "orange"
password "orange"
defaultroute
noipdefault
noccp
novj

then:

pon orange

(I'm not 100% sure "noccp" and "novj" are needed, but it works.)

Update: I've since installed Ubuntu "Netbook" on my Asus EeePC; the Huawei key is recognized and proper scripts provided for Orange.fr out of the box.

posted: 9/28/2009 06:15:00 AM

permanent link

Fri, 25 Sep 2009

Changing timezone in Debian

dpkg-reconfigure tzdata

posted: 9/25/2009 03:18:00 AM

permanent link

Mon, 07 Sep 2009

Xen and VLANs

Nothing you can't find elsewhere on the Internet in this post, just taking some notes.

This is for Debian Lenny (Xen 3.3). The idea is to connect eth0 to a switch that supports VLANs. The native VLAN is used, along with other VLANs.

• Install the Debian "vlan" package.
  modprobe 8021q and/or add 8021q to /etc/modules.
• Configure the native VLAN as usual (it's eth0 in /etc/networks/interfaces, later rewritten to peth0 by /etc/xen/scripts/network-bridge, while the "(v)eth0" inside Dom0 is connected back-to-back to vif0.0, which is added to the "eth0" bridge, formerly xenbr0).
• For additional VLANs, here is an example:

  # VLAN 4 (private)
  auto vlan4
  iface vlan4 inet manual
    bridge_fd 0
    bridge_maxwait 0
    bridge_helo 0
    bridge_stp off
    # Connect (p)eth0.4 to the VLAN
    bridge_ports eth0.4
    # Show this system on the VLAN
    up /sbin/ifconfig vlan4 192.168.1.201/24
  

  The up /sbin/ifconfig ... is optional if the VLAN does not need to appear on Dom0.
• Use network-bridge as usual in xend-config.sxp.
  Note that although eth0 is renamed to peth0, the VLAN subinterfaces (eth0.4, etc.) keep their original names (but "ip link" shows them as "eth0.4@peth0", for example, so really they are "peth0.4", etc.). Whatever the name, they remain connected to the bridge, which allows traffic to flow back and forth between the switch and the server.
• Finally, use a specification like this one for the interface(s) on DomU domains:

  vif = [ 'mac=00:23:78:5C:41:A2, ip=192.168.1.202, 
           vifname=server-private, bridge=vlan4' ]
  

  Multiple VIFs can be added; one VIF per VLAN that needs to be connected. This can be used for private or public VLANs alike.

Update: You must have an IP address specified for your eth0 interface. I lost a couple servers during their installation phase that way.

posted: 9/07/2009 06:05:00 AM

permanent link