GOOSE observer doesn't work without tcpdump on ubuntu

[IvanLipetsk]

Hi!
I use libiec release ver. 1.5.1 on ubuntu 22.10.
I have faced with a problem that goose observer example doesn't discovery any goose events until I start tcpdump (or wireshark). When I stop tcpdump, observer again stops watching goose events either.
Goose publisher works as it suppose to work.
Is it normal goose listener behavior for linux or I did something wrong?
Thanks in advance

[selvam1993]

Hi IvanLipetsk

I am having an issue with the GOOSE subscriber example code. I have run the tcpdump command in Ubuntu 20.04 (Focal Fossa) on the same system where I ran the goose_server_example and goose_observer files.

I can see that GOOSE messages are being simulated and transmitted when I use the tcpdump command, but the goose_observer is not receiving them. I am not sure if it is listening or not, as it is not displaying any messages or errors.

but I have not been able to resolve the issue. I used the same version of libiec61850 V1.5.1

as per the server_example_goose simulation
set the MAC address as 00:00:00:00:00:00 and AppID as 1000 in goose_observer

Could you please help me identify the problem and find a solution?

[IvanLipetsk]

Hi IvanLipetsk

I am having an issue with the GOOSE subscriber example code. I have run the tcpdump command in Ubuntu 20.04 (Focal Fossa) on the same system where I ran the goose_server_example and goose_observer files.

I can see that GOOSE messages are being simulated and transmitted when I use the tcpdump command, but the goose_observer is not receiving them. I am not sure if it is listening or not, as it is not displaying any messages or errors.

but I have not been able to resolve the issue. I used the same version of libiec61850 V1.5.1

as per the server_example_goose simulation set the MAC address as 00:00:00:00:00:00 and AppID as 1000 in goose_observer

Could you please help me identify the problem and find a solution?

Hi selvam1993!

The issue you have faced is a feature of linux systems. You can not use the same network interface (on linux) for publishing and subscribing goose messages.
My suggestion is either use windows machine or 2 linux machines, first for publisher and second for subscriber merged by the same network.
Please, also see this issue #61 for suggestions