A lot of changes were committed recently to the gluster-wireshark repository. A lot of effort was put into the details (click on the image to enlarge): UUIDs and GFIDs are now displayed as 4-2-2-2-6 bytesflags for OPEN, CREATE etc are now shown in detailmode/umask permissions are now shown in detaildictionaries are displayed more user friendlyMost of the work was done so that the dissector files get in shape for (requesting) inclusion in upstream.
[From an email to the gluster-devel mailinglist] today I have merged support for GlusterFS 3.2 and 3.3 into one Wireshark 'dissector'. The packages with date 20120516 in the version support both the current stable 3.2.x version, and the latest 3.3.0qa41. Older 3.3.0 versions will likely have issues due to some changes in the RPC-AUTH protocol used. Updating to the latest qa41 release (or newer) is recommended anyway. I do not expect that we'll add support for earlier 3.
My Fedora 17 Beefy Miracle alpha1 ARM system does not any contents in /var/log/messages. This is very impractical for troubleshooting. The command systemd-journalctl --no-tail shows that rsyslog.service fails to start correctly. Bummer! Starting the daemon by hand, does not give any issues, so at least rsyslogd does not have an issue itself. Checking the configuration, there are two unit files that may be used to start rsyslogd: /etc/systemd/system/syslog.service /etc/systemd/system/multi-user.target.wants/rsyslog.service Both of these are symlinks to the unit file (/usr/lib/systemd/system/rsyslog.
It seems that configuring a WLAN connection in NetworkManager on Fedora (tested on F17 alpha on ARM) is pretty straight forward. Unfortunately I was not able to find documentation about the steps, so I just note them down here: I must confess, that I cheated a little, as the configuration was initially created with nm-connection-editor by selecting the 'Available to all users' option. Copying the configuration files to the Fedora 17 rootfs image made my wireless work immediately.
Slow but steadily I am improving the packet dissector for Gluster. Once it is in a more complete state, it'll be submitted for inclusion in Wireshark. Until that time (which will likely take some more months), updated versions of Wireshark for RHEL6 and F16 will occur on the Fedora People Repository at http://repos.fedorapeople.org/repos/devos/wireshark-gluster/. The current packages can not only detect most of the Gluster traffic as explained in a previous post, but also display some of the more complex XDR structures used.
As part of my job, I am doing some tests with the Red Hat Storage Software Appliance. The current version of RHSSA is based on Gluster 3.2.5. After some experiments, it seem that Gluster is pretty cool and surprisingly easy to setup. In order to see what is going happening on the network, I captured some tcpdumps. Reading the files in Wireshark, does not show any Gluster specifics. It seems that Wireshark does not know how to decode (or rather dissect) the Gluster traffic.
With the current standard of mobiles and photo cameras that can be used to film things, it would be fun to create a little video. It seems that Brasero is a standard tool for the GNOME desktop, which should work without issues in my preferred XFCE as well. Brasero (and seemingly all of its dependencies) is even included in the Red Hat Enterprise Linux 6.2 Workstation repository/channel. Unfortunately, after creating a video project in Brasero, a little warning gets displayed:
So, this week I received my Pogoplug, and it is currently running Fedora 13 for ARM (Beta-2). The Pogoplug has an ARM/Kirkwood board inside, just like a Sheevaplug and other Plug* computers. Below are some notes on how to get Fedora installed on an external USB-drive (and keeping most of the original Pogoplug software on it, but disabled). The Fedora ARM Project provides a Beta root-disk for Fedora 13. Downloading the .
After some experimenting, I have a kernel .config based on the kernel from the Angstrom BeagleBoard Demo. The original provided kernel with gether did not boot on my (loaned) BeagleBoard Rev B5. Only after disabling USB completely (kernel parameter nousb). As gether is the part I am most interested in, booting without USB is pretty pointless. Fortunately the kernel provides /proc/config.gz. Using this configuration, some little tuning (i.e. turning off the staging-modules because they do not compile), a kernel and suitable modules could be built.
The only (for now) package I maintain, archivemount is now available in EPEL6 too. It has been in Fedora 14 for a while now, EPEL5 is following when libarchive is ready. For those who have no idea what archivemount is: Archivemount is a piece of glue code between libarchive and FUSE. It can be used to mount a (possibly compressed) archive (as in .tar.gz or .tar.bz2) and use it like an ordinary filesystem.