inet | INET Framework for the OMNeT++ discrete event simulator

244.244.244.1 is not a valid multicast address.

Multicast address are in the range of 224.0.0.1 - 239.255.255.255. The address you're sending to is not in that range. So the outgoing MAC address is not a multicast MAC.

Change the destination IP to be in the range of multicast IP addresses and you'll see a proper multicast MAC address.

In your call to inet_ntop:

It looks like this might be the root cause:

https://c-ares.org/mail/c-ares-archive-2017-08/0002.shtml

Although you indicated your Dockerfile is derived from a Tomcat 9 base image:

I pulled down you code and it seems to work just fine. You need to run it with iex -S mix phx.server or mix phx.server thought instead.

A couple of things:

1. iex is not a mix task it's the interactive elixir shell you can run your program with an interactive shell by calling iex with -S the script tag followed by you mix command.

2. You app is as most phoenix app are, to boot the endpoint when you call mix phx.server otherwise the app will start without spinning up the endpoint that allows it to respond to web requests. Elixir-Desktop launches with the endpoint.

I'm not familiar with Quarkus, but my "go to answer" for localhost forwarding not working in WSL is to try a wsl --shutdown and, if that works, disable Windows Fast Startup.

But in this case, you also aren't able to access it on the WSL2 instance's eth0 address, so something more might be going on. That could also be explained if the Quarkus boilerplate config is just binding to localhost or 127.0.0.1. You'd need it to bind to 0.0.0.0 in order for both to work.

Update for others looking at this answer in the future: Quarkus automatically binding to 127.0.0.1 or localhost did turn out to be the problem in this case. From @markvgti's research in the comments, the setting for this is to add quarkus.http.host=0.0.0.0 to the application.properties.

I have tried running different permutations and combinations of your /sbin/ifconfig command but its giving me also same error. But I have read the telegraf manual and come up with following approach/steps.

I have tested this in Linux with Telegraf's 1.19.3 version and it worked fine for me.

Steps:

• First thing first, don't waste your time(until someone posts an answer here), when we can create a script from your used commands in inputs.exec module of telegraf.
• So in spite of running direct command in telegraf conf file create a script(eg: script.bash in my tested case) and place your command there like as follows:

Since CIDRs are contiguous, you could add two columns: the minimum and maximum IP addresses in range, and create indexes on those. I wrote a gist here if you want to see the whole thing and play with it.

Basically:

Since the observed total packet length is way greater than that of a typical jumbo frame (MTU 9k), it's apparent that the receiver side employs either Large Receive Offload (LRO) or Generic Receive Offload (GRO) thus reassembling smaller packets into larger ones on the network interface driver level. This might explain why the packet socket in question sees already reassembled (large) packets.

In this specific case, ethtool -k output indicates clearly that LRO is always disabled whilst GRO is indeed active and can be adjusted. As per the discussion in comments, disabling GRO indeed bears fruit.