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 <darren.dob...@noaa.gov>wrote:

> 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 (the
> VLAN), and wlan0 (my wi-fi card).  The second machine is a virtual F19 with
> localhost, p7p1 (the VLAN), and p2p1 (a NAT interface).  I've disabled
> firewalls on both machines and I'm running Wireshark on the Ubuntu host.
>
> On the Ubuntu host, I ran NettyUDPAsyncTest using three URIs:
>
>                 "netty:udp://localhost:{{port}}?sync=false"
>
> "netty://udp://
> 224.1.1.1:1201?sync=false&broadcast=true&networkInterface=wlan0"
>
> "netty://udp://
> 224.1.1.1:1201?sync=false&broadcast=true&networkInterface=vboxnet0"
>
> Using localhost, the test passes and Wireshark shows UDP packets on
> 127.0.0.1.  Using wlan0, the test passes and Wireshark shows UDP packets on
> 192.168.1.7=wlan0.  However, using vboxnet0, the test fails but Wireshark
> shows UDP packets on 192.168.1.7=wlan0, not 192.168.56.1=vboxnet0 !  It
> looks like camel-netty is using wlan0 even when I specify vboxnet0.
>
> On the F19 virt, I tried:
>
>                 "netty:udp://localhost:{{port}}?sync=false"
>
> "netty:udp://
> 224.1.1.1:1201?sync=false&networkInterface=p2p1&broadcast=true"
>
> "netty:udp://
> 224.1.1.1:1201?sync=false&networkInterface=p7p1&broadcast=true"
>
> On localhost and p2p1, the test passes.  Wireshark sees nothing, which I
> suppose is expected since the Ubuntu host is not connected to these
> interfaces.  On p7p1 (which is the goal of this exercise) the test fails
> and, again, nothing shows on Wireshark.  Given what is happening on the
> Ubuntu host, I suspect that when I specify p7p1 on the F19 virt,
> camel-netty
> is mistakenly sending on p2p1 and then trying to receive on p7p1.
>
> I'm going to try debugging down through camel-netty, but if you have any
> suggestions in the meantime, please advise.
>
> -- Darren
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/using-Camel-Netty-to-multicast-UDP-beyond-localhost-tp5741490p5741601.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

Reply via email to