[arm-allstar] arm-allstar Digest, Vol 12, Issue 50/netctl

[AD2DX]

Ian, I'm so used to using a business class firewall for myself and my clients (IT guy) that I forget that home class firewalls don't have additional ports to use for separate LANs. Separate class C LANs is the easiest way to set up your home if you have additional ports on the firewall to do this. If you don't, then you get into routing issues with two subnet so, meaning, you need a router to route traffic between the two subnets.

Also did you see Doug's email about the eth commands on the Pi2 are different than the BBB?

73
Joe Lauricella - AD2DX
AD2DX at AD2DX dot US
(Sent from my iPhone)

> On May 21, 2015, at 15:31, "gm4upx at gb7jd.co.uk" <gm4upx at gb7jd.co.uk> wrote:
>
>
>> ----------------------------------------------------------------------
>> Message: 1
>> Date: Wed, 20 May 2015 22:21:53 +0100
>> From: gm4upx at gb7jd.co.uk
>> To: arm-allstar at hamvoip.org
>> Subject: [arm-allstar] netctl difficulty
>> Message-ID: <9ea5daed6bc6c00e684fb762546c6ce7 at gb7jd.co.uk>
>> Content-Type: text/plain; charset=US-ASCII; format=flowed
>> Hello,
>> Has anyone experienced this:-
>> I have two BBB and one PI2 and I decided that I would move them to a
>> subnet and used the following cmds.
>> edited /etc/netctl/eth0 on each and added the new ip addresses ( static
>> ) ; I found that I only needed to enter the ipaddress like
>> [192.168.1.1/29] and gateway like [192.168.1.10], this worked OK on the
>> BBB's but the PI2 refuses to take the new addresses and using [netctl
>> stop eth0], then [netctl start eth0] gives me an error that eth0 can't
>> be loaded and I can't connect to anything other than the other two BBB's
>> on the same subnet.  I have also removed the " default " settings with
>> [ip route del 0/0 via 192.168.0.1 dev eth0] and saved the eth0
>> configuration but it still refuses to play ball.
>> It should be simple to do, it works on the BBB's, but not on the PI2 and
>> after hours of trying it just won't work for me.  All suggestions
>> welcome..
>> Regards,
>> IAn..
>> ------------------------------
>> Message: 2
>> Date: Wed, 20 May 2015 22:40:59 +0000
>> From: AD2DX <ad2dx at ad2dx.us>
>> To: ARM Allstar <arm-allstar at hamvoip.org>
>> Subject: Re: [arm-allstar] netctl difficulty
>> Message-ID: <84CFE1DC-3B0C-48F5-9BDA-6A0E70552D9A at ad2dx.us>
>> Content-Type: text/plain; charset="utf-8"
>> Ian,
>> Since you?re using CIDR notation as /29, are you sure you want that? I
>> would think you want /24 or 255.255.255.0. You might want to check the
>> subnet mask that you have specified. Also check the default gateway
>> since they can only talk to each other on the same subnet.
>> Thanks and 73,
>> Joe AD2DX
> Hello Joe,
>
> Thanks for the reply, I'm in the process of learning by doing and seperating my " home " stuff, XYL's PC etc from my " radio " stuff hence the reason for not using /24 and choosing /29; the " home " stuff will be on the next up /29. I did discover that as long as the ipaddresses were within the same [192.168.1.0] range I could connect from one to another regardless of the gateway setting , obviously no connection possible to the outside world from the " wrong " ipaddress.
>
> Regards,
>
> Ian..
>
>> Message: 3
>> Date: Wed, 20 May 2015 20:17:25 -0400
>> From: Doug Crompton <doug at crompton.com>
>> To: ARM Allstar <arm-allstar at hamvoip.org>
>> Subject: Re: [arm-allstar] netctl difficulty
>> Message-ID: <BLU171-W51E8027B159D47F4849E58BAC10 at phx.gbl>
>> Content-Type: text/plain; charset="windows-1252"
>> The Rpi2 uses a completely different network manager (NOT netctl)
>> netctl should not be running on the RPi2. It you started it for some
>> reason make sure you stop and disable it. Having two managers running
>> can cause or sorts of problems.
>> On the RPi2 the manager is networkd and the setup is in
>> /etc/systemd/network/eth0.network
>> Static IP ranges in most networks span the last 8 bits (/24) or 253
>> usable addresses. There is probably no reason to limit it to less than
>> that unless you have an unusual situation. If you are using DHCP you
>> don't even have to worry about the netmask. For static 255.255.255.0
>> or /24 is the usual mask.
>> 73 Doug
>> WA3DSP
>> http://www.crompton.com/hamradio
> Hello Doug,
>
> Thanks for the reply, no wonder I've been getting errors, I'll do as you suggest, maybe I should RTFM more closely in future <smile>, I had noticed that the /29 enters the correct netmask.
> When I first set up the PI2 I used dhcp and everything was OK.
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
This email communication and any files transmitted with it may contain confidential and or proprietary information and is provided for the use of the intended recipient only. Any review, retransmission or dissemination of this information by anyone other than the intended recipient is prohibited. If you receive this email in error, please contact the sender and delete this communication and any copies immediately. Thank you.