Yes, I am using Camel 2.12, and I am using the networkInterface option. My
problem is that when I specify "networkInterface=vboxnet0", I see packets
instead sent to wlan0.
I've debugged down into
SingleUDPNettyServerBootstrapFactory.startServerBootstrap(), where it does
look like the correct inte
Darren,
Since Camel 2.12, you can use this option to specify the interface to be
used : networkInterface
Regards,
On Tue, Oct 15, 2013 at 3:35 PM, Darren Dobkin wrote:
> Yes, and I have a lot more information now. The bottom line is that I
> suspect the wrong interface is being selected in c
Yes, and I have a lot more information now. The bottom line is that I
suspect the wrong interface is being selected in camel-netty. Here are the
details:
I'm now testing a total of six interfaces on two machines. My VirtualBox
host is my Ubuntu laptop with three interfaces: localhost, vboxnet0
Can you sniff the UDP packets to check what is send by the camel netty
producer component and and if the netty consumer receives the packets ?
On Mon, Oct 14, 2013 at 3:17 AM, Darren Dobkin wrote:
> I'm running the NettyUDPAsyncTest in a Fedora 19 virtual machine inside
> VirtualBox. As the tes
