Showing results for 
Search instead for 
Did you mean: 

linkloop & RHEL5

Go to solution
New Member

linkloop & RHEL5


I'm trying to implement linkloop in a RHEL5.4 box.
I have GLIBC 2.5, but in the README it says only support up to 2.4, is there any option to make it run properly.
When I executed, I got this:

# uname -a
Linux phpnag01.inf.sta 2.6.18-164.el5PAE #1 SMP Tue Aug 18 15:59:11 EDT 2009 i686 i686 i386 GNU/Linux
# linkloop -i bond0 00:23:7D:D8:ED:CC
Link connectivity to LAN station: 00:23:7D:D8:ED:CC (HW addr 0x00237DD8EDCC)
*** buffer overflow detected ***: linkloop terminated
======= Backtrace: =========
======= Memory map: ========
004e3000-004ee000 r-xp 00000000 fd:00 296569 /lib/
004ee000-004ef000 rwxp 0000a000 fd:00 296569 /lib/
00578000-00592000 r-xp 00000000 fd:00 296562 /lib/
00592000-00593000 r-xp 00019000 fd:00 296562 /lib/
00593000-00594000 rwxp 0001a000 fd:00 296562 /lib/
00596000-006d5000 r-xp 00000000 fd:00 296563 /lib/
006d5000-006d6000 --xp 0013f000 fd:00 296563 /lib/
006d6000-006d8000 r-xp 0013f000 fd:00 296563 /lib/
006d8000-006d9000 rwxp 00141000 fd:00 296563 /lib/
006d9000-006dc000 rwxp 006d9000 00:00 0
00a3b000-00a3c000 r-xp 00a3b000 00:00 0 [vdso]
08048000-0804a000 r-xp 00000000 fd:00 1400509 /usr/bin/linkloop
0804a000-0804b000 rw-p 00001000 fd:00 1400509 /usr/bin/linkloop
0863e000-0865f000 rw-p 0863e000 00:00 0 [heap]
b7f18000-b7f19000 rw-p b7f18000 00:00 0
b7f22000-b7f24000 rw-p b7f22000 00:00 0
bf892000-bf8a7000 rw-p bffea000 00:00 0 [stack]

# ll /lib/
lrwxrwxrwx 1 root root 11 May 9 2009 /lib/ ->

Honored Contributor

Re: linkloop & RHEL5

I'd guess you have found an old linkloop binary RPM and installed it.

Get the source code from Sourceforge:

Recompile it on RHEL 5.4 (gcc, binutils and glibc-devel packages required to compile successfully):

$ tar zxvf linkloop-1.0.1-hp.tar.gz
$ ./configure
$ make

Once you recompile it, it will be linked against GLIBC 2.5 of RHEL 5.x, so it will work again.

You may install the linkloop binaries to /usr/local/bin by running "make install" as root, but then they won't be managed by the RPM package management system. A better way would be to create your own RPM package: it's more work, but it allows you to easily distribute the package to multiple systems, and to easily upgrade/remove it if/when necessary.

New Member

Re: linkloop & RHEL5