Thanks, Jon. I've forwarded your information request to the site. We did get
things working over UDP (using the same interfaces), so we know IP is working
and the netid configuration is ok. I still suspect that the VMware virtual
network configuration is squashing non-IP traffic, so I'm focusing on that
angle.
Gary Duzan
________________________________
From: Jon Maloy <jma...@redhat.com>
Sent: Monday, January 4, 2021 8:01 PM
To: Duzan, Gary D <gary.du...@fisglobal.com>;
tipc-discussion@lists.sourceforge.net <tipc-discussion@lists.sourceforge.net>
Subject: EXTERNAL: Re: [tipc-discussion] Discovery between VMs
CAUTION: This email originated from outside of the company. Do not click links
or open attachments unless you recognize the sender and know the content is
safe.
Hi Gary,
There are no known problems with connecting between VMs. As a matter of
fact, that is the way we run almost all the time.
Have you tried just to ping between the two VMs, using the same
interfaces? If that works they should definitely find each other.
If you can ping and they still don't discover each other, check the
cluster id (aka network id) by doing 'tipc node get netid' on both sides.
If the interfaces don't have IP addresses you could assign those
temporarily, just to check.
What do the commands 'tipc link list' and 'tipc bearer list' show you?
BR
Jon Maloy
On 1/4/21 4:22 PM, Duzan, Gary D via tipc-discussion wrote:
> I'm new here, and I have trouble getting to SourceForge through the
> corporate proxy, so forgive me if this is an FAQ. I'm trying to get TIPC
> working at a remote site between two VMs running Ubuntu 18.04 which at least
> appear to be on the same IP subnet. The node address is set to distinct
> values on both hosts (as 18.04 had other TIPC which required the manual
> config), and the broadcast bearer is there, but they don't appear to be
> discovering each other as the client gets a Host Unreachable trying to do a
> sendto(). I believe the VMs are running under VMware, but getting visibility
> on that could be tricky. The TIPC code works fine between physical hosts
> locally.
>
> Are there known problems getting the ethernet broadcast between VMs
> working? I believe I have the proper incantation to use a UDP bearer for use
> as a fallback, but I'd rather not use it if I don't have to.
>
> Thanks.
>
> Gary Duzan
>
> The information contained in this message is proprietary and/or confidential.
> If you are not the intended recipient, please: (i) delete the message and all
> copies; (ii) do not disclose, distribute or use the message in any manner;
> and (iii) notify the sender immediately. In addition, please be aware that
> any message addressed to our domain is subject to archiving and review by
> persons other than the intended recipient. Thank you.
>
> _______________________________________________
> tipc-discussion mailing list
> tipc-discussion@lists.sourceforge.net
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Ftipc-discussion&data=04%7C01%7Cgary.duzan%40fisglobal.com%7C9ba4ec9a0b2647532b7d08d8b11569ba%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C637454052818711634%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wwrG5EjpLCNRDSis9XdZYSGbclFp8BA19M6z4MCU5SI%3D&reserved=0
>
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
