[Commotion-discuss] Accessing resources across the network

[john whelan]

I've editted the /etc/hosts file to add one laptop so I can now ping using
the name hplaptop however although machines on both routers show the
correct ip address only the ones directly connected to the node it is on
give a positive reply to ping.

 I'd thought about adding an application but since that specifically states
you should check that the ip address is reachable that doesn't seem to
cover it.

Any suggestions?

Thanks John

On 16 February 2016 at 10:56, john whelan <jwhelan0112 at gmail.com> wrote:

> I have two 3400 routers one is 100.80.0.171 the other one is
> 100.118.150.64 which form a minimum mesh network.  I'm using three win 10
> laptops, at the moment all hardwired ethernet into the routers.
>
> I have ipconfig /released and renewed each laptop so they should be
> picking up their ip addresses from their respective routers.
>
> The two laptops  10.0.171.151 and 10.0.171.107 on one router can ping each
> other and the two routers but not the other laptops.  The other laptop
> 10.150.64.26 can ping both routers but not the other laptops.
>
> Suggestions please.
>
> Thanks John
>
> On 16 February 2016 at 10:34, Josh King <jking at opentechinstitute.org>
> wrote:
>
>> Hi Nat,
>>
>> You're right, but the ranges are a little off. It would be more
>> accurate to say that the nodes generate all of their addresses from the
>> same base, which is a hash of the mac address. So a node that has a
>> mesh address of 100.64.47.9 might give out addresses in the 10.47.9.X
>> range (it would necessarily be that clear because 100.64.0.0 is a /10
>> network, but you get the idea).
>>
>> This obviously isn't perfect, so a future version of Commotion will
>> generate IPv6 addresses generated from a hash of their crypto key, with
>> collision avoidance, and will NAT any IPv4 networks.
>>
>> On Tue, 2016-02-16 at 10:04 -0500, Nat Meysenburg wrote:
>> > john whelan <jwhelan0112 at gmail.com> writes:
>> >
>> > > For some reason I was thinking the IP address was leased from the
>> > > router
>> > > and not fixed.
>> > >
>> >
>> > The client address is assigned from the router.
>> >
>> > However, by default, the way the IP addressing is set up in
>> > Commotion,
>> > the nodes get IPs for the mesh in the 100.64.0.0/10 range (which
>> > according to the specs is reserved for carrier grade NAT). The nodes
>> > hand
>> > out DHCP addresses to clients in the 10.x.x.x (standard private
>> > network)
>> > range. I don't recall the actual default subnets offhand.
>> >
>> > Anyway, if I remember correctly (and it is indeed possible that I
>> > have
>> > this all wrong), the range in which a node hands out DHCP leases is
>> > based off of its 100.64.x address.
>> >
>> > The end result *should* be (again if I'm not totally mis-
>> > remembering),
>> > that client devices have addresses that that should be routable to
>> > each
>> > other, and the nodes should be able to handle the routing.
>> >
>> > So for example, node A is handing out leases in 10.64.8.x, and node B
>> > is
>> > handing them out in 10.64.7.x; client A is on node A with an IP of
>> > 10.64.8.14, and client B is on node B with an IP  of 10.64.7.151.
>> > They
>> > should be able to ping each other.
>> >
>> > Someone please correct me if I'm way off base here.
>> >
>> > ~~Nat
>> >
>> >
>> > _______________________________________________
>> > Commotion-discuss mailing list
>> > Commotion-discuss at lists.chambana.net
>> > https://lists.chambana.net/mailman/listinfo/commotion-discuss
>> --
>> Josh King
>> Lead Technologist
>> The Open Technology Institute
>> http://opentechinstitute.org
>> PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20160216/98349d77/attachment.html>