Add iPerf to FoG

[Gilou]

You can always add anything you want in the iPXE menu, to boot your DSL or any other linux from the network

[ch3i]

[quote=“Gilou, post: 39230, member: 3221”]You can always add anything you want in the iPXE menu, to boot your DSL or any other linux from the network ;)[/quote]

I know, but I think that a full integration in FoG is very usefull. The multicast speed depends of the slowest computer, identify the computer(s) wich is(are) slowest is very important

[ch3i]

[quote=“Gilou, post: 39230, member: 3221”]You can always add anything you want in the iPXE menu, to boot your DSL or any other linux from the network ;)[/quote]

Hi,

I’ll try to add iperf on the init wich the wiki explanation :

• Adding iperf to the /sbin directory

[CODE]
cd /tftpboot/fog/images
unxz init.xz
mkdir initmountdir
mount -o loop init initmountdir
cp /root/iperf /tftpboot/fog/images/initmountdir/sbin
[/CODE]

[CODE]
umount initmountdir
rmdir initmountdir
xz init
[/CODE]

I get a kernel panic when I try to enter in debug mode

Regards,
Ch3i.

[Tom Elliott]

when recompressing the init try:

[code]xz -C crc32 init[/code]

[ch3i]

[quote=“Tom Elliott, post: 39736, member: 7271”]when recompressing the init try:

[code]xz -C crc32 init[/code][/quote]

It’s good, thank’s a lot !

[ch3i]

Hi,

I create a script in the /bin of the init.xz (fog.iperfu).

[CODE]#!/bin/sh
iperf -c ip.of.server.fog[/CODE]

How can I launch this script ? I create a entry in the iPXE menu, but don’t know how to configure it…

[IMG]http://img4.hostingpics.net/pics/757277iperfu.png[/IMG]

Regards,
Ch3i.

[Tom Elliott]

Did you modify the S99fog script so the params called will enable the starting of this script?

/etc/init.d/S99fog is the filename. The way the boot menu works:

Menu Item: (Label and function caller, in your case, fog.iperfu would become the Menu item you select and there will be a menu entry created for this item.

Description just makes a label for your menu item so it won’t display as fog.iperfu, but rather: “Iperf in unicast” on the menu system.

Parameters are ipxe parameters to follow, such as login and such:

Example:
[code]login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param keyreg 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme[/code]

So any ipxe params can be specified and setup here. The login part is still needing some work (maybe some hooks to help implement direction as well) but should work if you have no params, or very basic parameters needed.

The place you’re probably needing things is Boot options. This is where you specify kernel arguments or variable callers for the init to process.

Example:

[code]mode=iperfu[/code]

This (if you setup your S99fog script to do something with the mode) e.g.:
/etc/init.d/S99fog
[code]elif [ “$mode” == “iperfu” ]; then
run=“/bin/fog.iperfu”;
after=$afterActionTerm;[/code]

Hopefully this helps make sense of it all.

It’s by far a “perfect” solution, but it’s better than what we did have. And seeing as you all want to do custom entries, I think it’s okay that it’s somewhat limited by design, and will allow you all the chance to learn how to operate these things fairly smoothly.

[ch3i]

Thank’s a lot, it’s OK !!!

I will close properly, and post a summary after

[Wayne Workman]

@Tom-Elliott has integrated iPerf and iPerf3 into the current FOG inits.

[Wayne Workman]

@Tom-Elliott is iPerf still in the $PATH variable in the inits, and available?