CEPTCL: Doesn't RX multicast, has anyone seen it work before?

Anyone,
I've asked this before, but I figured I'd try one more time before
giving up on the CEP package. I've spent ws trying to get the
CEPTCL package to work on my Linux. It took about 10 min for me to get
it to TX multicast but I cannot get it to receive multicast. I'd use
another package if I could but this is the only one I've seen that
supports all of the things I need. Like I said, it sends fine but my
RX handler is never called. I know that there are packets to 224.0.0.2
(from a router) on that interface because I see them with the ethereal
application. Someone sugested to use fconfigure to join the 224.0.0.2
group - good idea, still doesn't receive.

Why isn't the handler called? I don't know. I'm using wish 8.4.

QUESTION: Has anyone ever seen this package receive multicast?

Thanks,
- Daniel

wm withdraw .
set cepLibDir "/lib"

## Package Index file:
package ifneeded ceptcl 0.3 \
[list load [file join $cepLibDir libceptcl0.3.so]]


## Initialization:
package require ceptcl

proc udpEventHandler { sock interface } {
global testerIp localIf
puts "DEBUG: RX Handler called!"
set pkt [read $sock]
binary scan $pkt "H*" datapacket
set peer [fconfigure $sock -peer]
puts "RX $peer: [string length $datapacket] {$datapacket}"
decodePdu $datapacket RX $interface
return
}

proc createUdpCep { localIp } {
puts "DEBUG: Creating CEP on interface: $localIp ..."
set cepHandle [cep -type datagram -protocol 17 -myaddr \
$localIp -myport 646 -noresolve 224.0.0.2 646]
return $cepHandle
}

proc udpStart { interface } {
global srv testerIp
set srv($interface) [createUdpCep $interface]   ;# CEPTCL
Package
fconfigure $srv($interface) -maddr $interface -buffering none -
translation {auto auto} -blocking 0
fileevent $srv($interface) readable [list udpEventHandler
$srv($interface) $interface]
fconfigure $srv($interface) -join 224.0.0.2
puts "Listening on udp port: [fconfigure $srv($interface) -
maddr]"
puts "Interface: $interface \($srv($interface)\) set up for
Transmit and Receive of UDP"
return $srv($interface)
}

proc sendUdpCep { cepHandle datapacket } {
set formattedDatapacket [binary format H* $datapacket]
puts "TX: Sending UDP packet \"$datapacket\" ..."
#      decodePdu $datapacket TX
sendto $cepHandle 224.0.0.2 646 "$formattedDatapacket"
}

On Aug 22, 11:17 pm, dkushne...@yahoo.com wrote:
> Anyone,
>
> Someone sugested to use fconfigure to join the 224.0.0.2
> group - good idea, still doesn't receive.

Could you please try the other suggestions:
- strace to see if something happens at the syscall level or not
- 224.0.0.1 because it is automatically registered (joined to)

-Alex

On Aug 22, 2:46 pm, Alexandre Ferrieux <alexandre.ferri...@gmail.com>
wrote:
> On Aug 22, 11:17 pm, dkushne...@yahoo.com wrote:
> 
> 
>
> Could you please try the other suggestions:
>    - strace to see if something happens at the syscall level or not
>    - 224.0.0.1 because it is automatically registered (joined to)
>
> -Alex

Hi Alex,
I did not know what strace is. I did "yum install strace" and I got
it, installed it. I have to figure out how to use it. I'm reading the
man page (http://linux.die.net/man/1/strace). How do I use it?

I ran a quick test with 224.0.0.1 (more tests to follow):
I changed the script TX to 224.0.0.1 and it is sent onto the wire but
I do not get it received. The CEP man page says that to keep from
receiving what is sent (looping back) to use the -loop option. I
didn't use that option purposely just to see if the RX handler would
be called and it wasn't called - still no RX! I don't t hink that test
is fair. I'll try to find another device to send multicast 224.0.0.1
onto the wire so that I'm not using the same script that I'm trying to
test.

- Daniel

On Aug 22, 2:46 pm, Alexandre Ferrieux <alexandre.ferri...@gmail.com>
wrote:
> On Aug 22, 11:17 pm, dkushne...@yahoo.com wrote:
> 
> 
>
> Could you please try the other suggestions:
>    - strace to see if something happens at the syscall level or not
>    - 224.0.0.1 because it is automatically registered (joined to)
>
> -Alex

Alex,
Is this what you want. I'm at5tached to the process for the script. I
see everything except RX. There is a router sending to 224.0.0.2 on
the wire. I see the packets with my sniffer on the same interface but
the script RX handler is still not called.
- Daniel

[root@castlerock dkushner]# ps -ef | grep wish
root     22524 19845  0 15:21 pts/5    00:00:00 /opt/ajuba/TclPro1.4/
linux-ix86/bin/prowish83.bin
root     22533 22457  0 15:22 pts/7    00:00:00 grep wish
[root@castlerock dkushner]# strace -p 22524
Process 22524 attached - interrupt to quit
select(7, [0 3 4 5 6], [], [], {4, 200000}) = 0 (Timeout)
gettimeofday({1187821347, 105840}, {420, 0}) = 0
gettimeofday({1187821347, 105966}, {420, 0}) = 0
gettimeofday({1187821347, 106181}, {420, 0}) = 0
write(1, "INFO 0:0:30:087  ::ldpSimTool::l"..., 79) = 79
write(1, "TX: Sending UDP packet \"0001001e"..., 98) = 98
sendto(5,
" \0\1\0\36\32\0\0\2\0\0\1\0\0\24\0\0\0\1\
4\0\0\4\0\0\0\0\4\1\0\4\32\0"...,
34, 0, {sa_family=AF_INET, sin_port=htons(646),
sin_addr=inet_addr("224.0.0.2")}, 16) = 34
gettimeofday({1187821347, 107644}, {420, 0}) = 0
gettimeofday({1187821347, 107822}, {420, 0}) = 0
gettimeofday({1187821347, 107953}, {420, 0}) = 0
gettimeofday({1187821347, 108075}, {420, 0}) = 0
select(7, [0 3 4 5 6], [], [], {4, 999569}) = 0 (Timeout)
gettimeofday({1187821352, 107848}, {420, 0}) = 0
gettimeofday({1187821352, 107974}, {420, 0}) = 0
gettimeofday({1187821352, 108237}, {420, 0}) = 0
write(1, "INFO 0:0:35:089  ::ldpSimTool::l"..., 79) = 79
write(1, "TX: Sending UDP packet \"0001001e"..., 98) = 98
sendto(5,
" \0\1\0\36\32\0\0\2\0\0\1\0\0\24\0\0\0\1\
4\0\0\4\0\0\0\0\4\1\0\4\32\0"...,
34, 0, {sa_family=AF_INET, sin_port=htons(646),
sin_addr=inet_addr("224.0.0.2")}, 16) = 34
gettimeofday({1187821352, 109716}, {420, 0}) = 0
gettimeofday({1187821352, 109832}, {420, 0}) = 0
gettimeofday({1187821352, 109961}, {420, 0}) = 0
gettimeofday({1187821352, 110082}, {420, 0}) = 0
select(7, [0 3 4 5 6], [], [], {4, 999634}) = 0 (Timeout)
gettimeofday({1187821357, 109838}, {420, 0}) = 0
gettimeofday({1187821357, 109967}, {420, 0}) = 0
gettimeofday({1187821357, 110180}, {420, 0}) = 0
write(1, "INFO 0:0:40:091  ::ldpSimTool::l"..., 79) = 79
write(1, "TX: Sending UDP packet \"0001001e"..., 98) = 98
sendto(5,
" \0\1\0\36\32\0\0\2\0\0\1\0\0\24\0\0\0\1\
4\0\0\4\0\0\0\0\4\1\0\4\32\0"...,
34, 0, {sa_family=AF_INET, sin_port=htons(646),
sin_addr=inet_addr("224.0.0.2")}, 16) = 34
gettimeofday({1187821357, 111677}, {420, 0}) = 0
gettimeofday({1187821357, 111795}, {420, 0}) = 0
gettimeofday({1187821357, 111929}, {420, 0}) = 0
gettimeofday({1187821357, 112053}, {420, 0}) = 0
select(7, [0 3 4 5 6], [], [], {4, 999624}) = 0 (Timeout)
gettimeofday({1187821362, 111832}, {420, 0}) = 0
gettimeofday({1187821362, 111960}, {420, 0}) = 0
gettimeofday({1187821362, 112172}, {420, 0}) = 0
write(1, "INFO 0:0:45:093  ::ldpSimTool::l"..., 79) = 79
write(1, "TX: Sending UDP packet \"0001001e"..., 98) = 98
sendto(5,
" \0\1\0\36\32\0\0\2\0\0\1\0\0\24\0\0\0\1\
4\0\0\4\0\0\0\0\4\1\0\4\32\0"...,
34, 0, {sa_family=AF_INET, sin_port=htons(646),
sin_addr=inet_addr("224.0.0.2")}, 16) = 34
gettimeofday({1187821362, 113629}, {420, 0}) = 0
gettimeofday({1187821362, 113754}, {420, 0}) = 0
gettimeofday({1187821362, 113886}, {420, 0}) = 0
gettimeofday({1187821362, 114010}, {420, 0}) = 0
select(7, [0 3 4 5 6], [], [], {4, 999619}) = 0 (Timeout)
gettimeofday({1187821367, 113882}, {420, 0}) = 0
gettimeofday({1187821367, 114010}, {420, 0}) = 0
gettimeofday({1187821367, 114219}, {420, 0}) = 0
write(1, "INFO 0:0:50:095  ::ldpSimTool::l"..., 79) = 79
write(1, "TX: Sending UDP packet \"0001001e"..., 98) = 98
sendto(5,
" \0\1\0\36\32\0\0\2\0\0\1\0\0\24\0\0\0\1\
4\0\0\4\0\0\0\0\4\1\0\4\32\0"...,
34, 0, {sa_family=AF_INET, sin_port=htons(646),
sin_addr=inet_addr("224.0.0.2")}, 16) = 34
gettimeofday({1187821367, 115625}, {420, 0}) = 0
gettimeofday({1187821367, 115747}, {420, 0}) = 0
gettimeofday({1187821367, 115876}, {420, 0}) = 0
gettimeofday({1187821367, 115997}, {420, 0}) = 0
select(7, [0 3 4 5 6], [], [], {4, 999628}) = 0 (Timeout)
gettimeofday({1187821372, 115842}, {420, 0}) = 0
gettimeofday({1187821372, 115967}, {420, 0}) = 0
gettimeofday({1187821372, 116177}, {420, 0}) = 0
write(1, "INFO 0:0:55:097  ::ldpSimTool::l"..., 79) = 79
write(1, "TX: Sending UDP packet \"0001001e"..., 98) = 98
sendto(5,
" \0\1\0\36\32\0\0\2\0\0\1\0\0\24\0\0\0\1\
4\0\0\4\0\0\0\0\4\1\0\4\32\0"...,
34, 0, {sa_family=AF_INET, sin_port=htons(646),
sin_addr=inet_addr("224.0.0.2")}, 16) = 34
gettimeofday({1187821372, 117641}, {420, 0}) = 0
gettimeofday({1187821372, 117763}, {420, 0}) = 0
gettimeofday({1187821372, 117892}, {420, 0}) = 0
gettimeofday({1187821372, 118012}, {420, 0}) = 0
select(7, [0 3 4 5 6], [], [], {4, 999629} <unfinished ...>
Process 22524 detached
[root@castlerock dkushner]#

dkushner99@yahoo.com wrote:
> I did not know what strace is. I did "yum install strace" and I got
> it, installed it. I have to figure out how to use it. I'm reading the
> man page (http://linux.die.net/man/1/strace). How do I use it?

strace is a program that traces what system calls a program makes. You
use it by putting 'strace' as a separate word at the start of the
command line that invokes program you want to trace. It produces *lots*
of output IIRC; you'll definitely want to save it in a file so you can
search through it at your leisure.

When searching the trace file for relevant stuff, look especially for
the bind() syscall as that's responsible for giving a socket an address.
That'll tell you which file descriptor to follow. (And yes, following
syscall traces does take a bit of detective work.)

Also be aware that some routers don't support multicast well. :-(

Donal.

On Aug 23, 12:34 am, dkushne...@yahoo.com wrote:
>
> Alex,
> Is this what you want. I'm at5tached to the process for the script. I
> see everything except RX. There is a router sending to 224.0.0.2 on
> the wire. I see the packets with my sniffer on the same interface but
> the script RX handler is still not called.

Yes !

> select(7, [0 3 4 5 6], [], [], {4, 999569}) = 0 (Timeout)

This one shows you that despite handlers on the five descriptors (one
of which is no doubt the proper UDP socket), the select() is only
unlocked by its 5-second timeout (your [after 5000]).

This means that it is definitely a join issue. Can you please post the
code with the join, and also the strace output when it is doing the
join ?

-Alex

You can use bash localy for testing.

First:
echo "teststring" >/dev/udp/<this_host_ip>/<my_app_port>

This should trigger your receive handler.

then:
echo "teststring" >/dev/udp/<my_mcast_group>/<my_app_port>

This then should do the same.

apropos:
What does your routing look like?

and does ifconfig for the used interface
show "multicast" in the options?
Like:
robert:~ # ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:0E:A6:B0:BB:6B
inet addr:172.33.99.1  Bcast:172.33.99.255  Mask:255.255.255.0
inet6 addr: fe80::20e:a6ff:feb0:bb6b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-------------------------------^^^^^^^^^
RX packets:13438274 errors:0 dropped:0 overruns:0 frame:0
TX packets:8824671 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2198898107 (2097.0 Mb)  TX bytes:3936442011 (3754.0 Mb)
Interrupt:185 Base address:0x6000


uwe

On Aug 24, 5:19 am, Uwe Klein <uwe_klein_habertw...@t-online.de>
wrote:
> You can use bash localy for testing.
>
> First:
> echo "teststring" >/dev/udp/<this_host_ip>/<my_app_port>
>
> This should trigger your receive handler.
>
> then:
> echo "teststring" >/dev/udp/<my_mcast_group>/<my_app_port>
>
> This then should do the same.
>
> apropos:
> What does your routing look like?
>
> and does ifconfig for the used interface
> show "multicast" in the options?
> Like:
> robert:~ # ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:0E:A6:B0:BB:6B
>            inet addr:172.33.99.1  Bcast:172.33.99.255  Mask:255.255.255.0
>            inet6 addr: fe80::20e:a6ff:feb0:bb6b/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> -------------------------------^^^^^^^^^
>            RX packets:13438274 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:8824671 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:2198898107 (2097.0 Mb)  TX bytes:3936442011 (3754.0 Mb
)
>            Interrupt:185 Base address:0x6000
>
> uwe

Hi,
Thanks for the help!
1) ifconfig shows multicast. Actually the udptcl package DOES work
with multicast TX and RX on this Linux just fine but ceptcl does not
RX multicast. I need the options that ceptcl has though. udptcl only
works on one interface and ceptcl can utilize any interface (or
alias). That's what I need.

2) I ran my script using tcludp and tried the commands you sugested.
It received the packets and called the handler.

3) I ran my script using ceptcl and tried the commands you sugested.
It DIDN'T receive the packets and called the handler WAS NOT called.

Right now I'm using eth0 for my script (because tcludp only works on
that interface), but if I can get ceptcl to work I'll utilize other
interfaces. I shouldn't run protocol tests on my network interface
that connects to the corp net. I need to use the other interfaces
(like ceptcl supports if it worked).


[root@castlerock dkushner]# /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:11:0D:14:6E
inet addr:172.24.217.91  Bcast:172.24.217.255  Mask:
255.255.255.0
inet6 addr: fe80::211:11ff:fe0d:146e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:1694175 errors:0 dropped:0 overruns:0 frame:0
TX packets:2152843 errors:0 dropped:0 overruns:0 carrier:0
collisions:268893 txqueuelen:100
RX bytes:265462251 (253.1 MiB)  TX bytes:1389346959 (1.2
GiB)
Base address:0xddc0 Memory:fcee0000-fcf00000

eth0:1    Link encap:Ethernet  HWaddr 00:11:11:0D:14:6E
inet addr:26.0.0.2  Bcast:26.255.255.255  Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
Base address:0xddc0 Memory:fcee0000-fcf00000

eth1      Link encap:Ethernet  HWaddr 00:14:C1:35:BF:06
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
Interrupt:21 Base address:0x4f00

lo        Link encap:Local Loopback
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:5936 errors:0 dropped:0 overruns:0 frame:0
TX packets:5936 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12413742 (11.8 MiB)  TX bytes:12413742 (11.8 MiB)

[root@castlerock dkushner]#
[root@castlerock dkushner]# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window
irtt Ifac
172.24.217.0    *               255.255.255.0   U         0 0
0 eth0
169.254.0.0     *               255.255.0.0     U         0 0
0 eth0
26.0.0.0        *               255.0.0.0       U         0 0
0 eth0
default         router-172-24-2 0.0.0.0         UG        0 0
0 eth0
[root@castlerock dkushner]#
- Daniel

On Aug 23, 1:16 am, dkushne...@yahoo.com wrote:
> Here's a quick dump. I can see some calls to set up multicast.
> Let me know what yopu think.

> setsockopt(5, SOL_IP, IP_ADD_MEMBERSHIP, "\340\0\0\2\0\0\0\0", 8) = 0

OK. Now please do the same with tcludp, trying to stick to the same
interface, ports and addresses.
The delta between two complex behaviors is often easier to analyze...

-Alex

Alex, My peer is 26.0.0.1, I am 26.0.0.2. This means that the RX
handler is being called. tcludp works but ceptcl does not.

Kinda long trace ... NOTICE:

## FROM TRACE ##########
RX 26.0.0.1 646: 68
 {0001001e1900000100000100001400006059040
00004000f00000401000419000001}
INFO 0:0:5:707   ::ldpSimTool::ldp-A1: Sending UDP-HELLO, Hello-time:
5000 ...
TX: Sending UDP packet
" 0001001e1a000002000001000014000000010400
000400000000040100041a000002" ...
DEBUG: RX Handler called!
RX 26.0.0.1 646: 0 {}


## WHOLE TRACE (tclUDP (eth0)) ######################
Loading: CLI-LDP-instance-delete.tcl ...
Loading: ldp-simtool-hello-pdu-tlvs.tcl ...
Loading: ldp-simtool-logging.tcl ...
Loading: ldp-simTool-decode-tlv.tcl ...
Loading: ldp-simtool-modify-message.tcl ...
Loading: ldp-simtool-help-tlv.tcl ...
Loading: ldp-simtool-cept-if.tcl ...
INFO 0:0:0:0     Adding interface to list of available interfaces:
eth0
172.24.217.91
INFO 0:0:0:1     Adding interface to list of available interfaces:
eth0:1 26.0.0.2
DEBUG: Creating UDP on interface: 26.0.0.2 ...
Listening on port: 646
INFO 0:0:0:413   Adding interface to list of available interfaces:
eth0:2 26.0.0.3
INFO 0:0:0:413   Attempting to create LDP Instance name: "ldp-A1".
DEBUG:
INFO 0:0:0:414   Initializing PDUs for LDP instance name:
::ldpSimTool::ldp-A1 ...
INFO 0:0:0:458   Configuring UDP-HELLO PDU, TLV type:
common-hello-params to: "include".
INFO 0:0:0:459   Configuring UDP-HELLO PDU, TLV type:
common-hello-params field values to: "default".
INFO 0:0:0:460   Configuring UDP-HELLO PDU, TLV type:
ipv4-transport-address to: "include".
INFO 0:0:0:465   Configuring UDP-HELLO PDU, TLV type: fec to:
"exclude".
INFO 0:0:0:466   Configuring UDP-HELLO PDU, TLV type: address-list
field values to: "default".
INFO 0:0:0:466   Configuring UDP-HELLO PDU, TLV type: address-list to:
"exclude".
INFO 0:0:0:469   Configuring UDP-HELLO PDU, TLV type: address-list
field values to: "default".
INFO 0:0:0:470   Configuring UDP-HELLO PDU, TLV type: hop-count to:
"exclude".
INFO 0:0:0:473   Configuring UDP-HELLO PDU, TLV type: hop-count field
values to: "default".
INFO 0:0:0:474   Configuring UDP-HELLO PDU, TLV type: path-vector to:
"exclude".
INFO 0:0:0:474   Configuring UDP-HELLO PDU, TLV type: Hop-Count field
values to: "default".
INFO 0:0:0:479   Configuring UDP-HELLO PDU, TLV type: generic-label
to:
"exclude".
INFO 0:0:0:483   Configuring UDP-HELLO PDU, TLV type: Hop-Count field
values to: "default".
INFO 0:0:0:484   Configuring UDP-HELLO PDU, TLV type: atm-label to:
"exclude".
INFO 0:0:0:484   Configuring UDP-HELLO PDU, TLV type: Hop-Count field
values to: "default".
INFO 0:0:0:488   Configuring UDP-HELLO PDU, TLV type: frame-relay-
label
to: "exclude".
INFO 0:0:0:489   Configuring UDP-HELLO PDU, TLV type: Hop-Count field
values to: "default".
INFO 0:0:0:489   Configuring UDP-HELLO PDU, TLV type: ft-protection
to:
"exclude".
INFO 0:0:0:490   Configuring UDP-HELLO PDU, TLV type: Hop-Count field
values to: "default".
INFO 0:0:0:495   Configuring UDP-HELLO PDU, TLV type: status to:
"exclude".
INFO 0:0:0:502   Configuring UDP-HELLO PDU, TLV type: Hop-Count field
values to: "default".
INFO 0:0:0:503   Configuring UDP-HELLO PDU, TLV type: extended-status
to: "exclude".
INFO 0:0:0:504   Configuring UDP-HELLO PDU, TLV type: Hop-Count field
values to: "default".
INFO 0:0:0:507   Configuring UDP-HELLO PDU, TLV type: returned-pdu to:
"exclude".
INFO 0:0:0:508   Configuring UDP-HELLO PDU, TLV type: Returned-PDU
field values to: "default".
INFO 0:0:0:509   Configuring UDP-HELLO PDU, TLV type:
configuration-sequence-number to: "exclude".
INFO 0:0:0:512   Configuring UDP-HELLO PDU, TLV type:
ipv6-transport-address to: "exclude".
INFO 0:0:0:518   Configuring UDP-HELLO PDU, TLV type:
common-session-params to: "exclude".
INFO 0:0:0:519   Configuring UDP-HELLO PDU, TLV type:
atm-session-params to: "exclude".
INFO 0:0:0:520   Configuring UDP-HELLO PDU, TLV type:
frame-relay-session-params to: "exclude".
INFO 0:0:0:520   Configuring UDP-HELLO PDU, TLV type: ft-session-tlv
to: "exclude".
INFO 0:0:0:524   Configuring UDP-HELLO PDU, TLV type: ft-ack-tlv to:
"exclude".
INFO 0:0:0:525   Configuring UDP-HELLO PDU, TLV type: ft-cork-tlv to:
"exclude".
INFO 0:0:0:526   Configuring UDP-HELLO PDU, TLV type:
label-req-message-id to: "exclude".
INFO 0:0:0:690   Configuring UDP-HELLO PDU, TLV type: mtu to:
"exclude".
INFO 0:0:0:690   Initializing LDP Instance: ldp-A1 LSR-ID:
26.0.0.2 ...
INFO 0:0:0:691   Adding Interface: 26.0.0.2 to LDP instance name:
::ldpSimTool::ldp-A1 ...
INFO 0:0:0:693   Starting UDP Hello timer for Instance:
::ldpSimTool::ldp-A1 interface: eth0:1 26.0.0.2 ...
DEBUG 0:0:0:697   DEBUG: Init-Instance - INCLUDING Common-Hello-Params
TLV ...
DEBUG 0:0:0:700   DEBUG: COMMON-HELLO-PARAMS TLV U-bit, F-bit, Type:
04
00
DEBUG 0:0:0:700   DEBUG: COMMON-HELLO-PARAMS TLV Length: 00 04
DEBUG 0:0:0:700   DEBUG: COMMON-HELLO-PARAMS TLV Hold-Time: 00 00
DEBUG 0:0:0:701   DEBUG: COMMON-HELLO-PARAMS TLV T-bit, R-bit, Rsvd:
00
00
DEBUG 0:0:0:701   DEBUG: Init-Instance - INCLUDING
IPv4-Transport-Address TLV ...
DEBUG 0:0:0:701   DEBUG: IPv4-Transport-Address TLV U-bit, F-bit,
Type:
04 01
DEBUG 0:0:0:701   DEBUG: IPv4-Transport-Address TLV Length: 00 04
DEBUG 0:0:0:702   DEBUG: IPv4-Transport-Address TLV IPv4-Addr:
26.0.0.2 (Dec: 1a 00 00 02)
DEBUG 0:0:0:705   Length: 00 1e (Decimal: 30)
DEBUG 0:0:0:705   Version: 00 01
DEBUG 0:0:0:705   LDP-ID: 1a 00 00 020000
INFO 0:0:0:706   ::ldpSimTool::ldp-A1: Sending UDP-HELLO, Hello-time:
5000 ...
TX: Sending UDP packet

" 0001001e1a000002000001000014000000010400
000400000000040100041a000002" ...
DEBUG: RX Handler called!
DEBUG: RX from myself - Throwing it away!
DEBUG: RX Handler called!
DEBUG: RX from myself - Throwing it away!
DEBUG: RX Handler called!
RX 26.0.0.1 646: 68

 {0001001e1900000100000100001400006059040
00004000f00000401000419000001}
INFO 0:0:5:707   ::ldpSimTool::ldp-A1: Sending UDP-HELLO, Hello-time:
5000 ...
TX: Sending UDP packet

" 0001001e1a000002000001000014000000010400
000400000000040100041a000002" ...
DEBUG: RX Handler called!
RX 26.0.0.1 646: 0 {}
DEBUG: RX Handler called!
DEBUG: RX from myself - Throwing it away!
DEBUG: RX Handler called!
DEBUG: RX from myself - Throwing it away!
DEBUG: RX Handler called!
RX 26.0.0.1 646: 68

 {0001001e190000010000010000140000605a040
00004000f00000401000419000001}
INFO 0:0:10:709  ::ldpSimTool::ldp-A1: Sending UDP-HELLO, Hello-time:
5000 ...
TX: Sending UDP packet

" 0001001e1a000002000001000014000000010400
000400000000040100041a000002" ...
DEBUG: RX Handler called!
RX 26.0.0.1 646: 0 {}
DEBUG: RX Handler called!
DEBUG: RX from myself - Throwing it away!
DEBUG: RX Handler called!
DEBUG: RX from myself - Throwing it away!
DEBUG: RX Handler called!
RX 26.0.0.1 646: 68

 {0001001e190000010000010000140000605b040
00004000f00000401000419000001}
INFO 0:0:15:711  ::ldpSimTool::ldp-A1: Sending UDP-HELLO, Hello-time:
5000 ...
TX: Sending UDP packet

" 0001001e1a000002000001000014000000010400
000400000000040100041a000002" ...
DEBUG: RX Handler called!
RX 26.0.0.1 646: 0 {}
DEBUG: RX Handler called!
DEBUG: RX from myself - Throwing it away!