[ML-General] linux networking questions

Michael Patton pattoma at gmail.com
Tue Oct 6 08:28:52 CDT 2015


I'm late to the game but are you still having problems?

I had issues with my rpi last year and dhcp not working blah blah.

What does your: sudo cat /etc/network/interfaces say?

Have you set up the static IP in there?

Sorry if you answered this already and I'm assuming you have --  I need
more coffee.

On Mon, Oct 5, 2015 at 11:10 PM, david <ainut at knology.net> wrote:

> I got the router setup.  It's the PC's (Linux and one Winblows) that I now
> need to also configure.
> Strange that .7.2 would work already, but not .10.1.
>
> David
>
>
>
>
> On 10/05/2015 10:59 PM, James Fluhler wrote:
>
> I can turn on my rpi in the morning and tell your for certain; and maybe I
> completely mis understood your question. I will also be the first to admit
> my knowledge of advanced networking is nil. But I always thought that
> basically you need everything in IP addresses to be identical minus the
> last 3 numbers after the So AAA.BBB.CCC.###
>
> Now if the issue is that stock the IP address of the beagle bone or rpi is
> not taking an address from your router; I think you can use ifconfig to set
> the ip and subnet address.
>
> The only way I could think you could get say your pc at 192.168.1.xxx to
> talk to 192.168.2.xxx is to have some device with two network interfaces
> connected to both networks that will also share network data between the
> net works. Eg you could connect a router to a router thus combining
> networks with different IPs and different SSIDs.
>
> You could probably use your rpi to do this setting up say the wireless to
> serve dhcp and act as an access point and the wired connected to your of
> network, or even two wireless adapters on the rpi.
>
> Idk like is said im not an advanced networking person, I have messed a
> little with virtual networks and I believe it's possible you could connect
> to say 192.168.2.30 from a computer with the address 192.168.1.xxx via a
> virtual lan. But I can't say I know exactly how to do this on Linux or PC
> well enough to explain in an email. But I use a virtual lan for connecting
> to the configuration IP address of a wireless back haul I setup between two
> office buildings at work. That said the back haul is connected to the same
> network I am on its just its configuration server is on a virtual lan.
>
> Just a few thoughts maybe someone has better suggestions
>
> James F.
>
> On Oct 5, 2015, at 10:37 PM, david <ainut at knology.net> wrote:
>
> Appreciate the help, Hunter.  Is it not easy to have everything in the
> 192.168.x.x address range?  (Mask 255.255.0.0?)  I can't remember any of
> this but bits and pieces...
>
> My router and firewall to the outside world are set not to pass
> 192.168.x.x out to the world (as such) but I'm using all bridges internally
> (but there may still be one brouter in the mix; not sure.)
>
> Thanks,
> David
>
>
>
> On 10/05/2015 10:32 PM, Hunter Fuller wrote:
>
> The long and the short of it is subnet masking. Basically, in home
> networking, your subnet mask is almost always 255.255.255.0 also known as a
> /24 (slash 24). What this means is that the first three octets of the IPs
> of two devices have to be the same before they can talk.
>
> Routers are capable of breaking this boundary, but of course your router
> can only know about 192.168.1.0/24 so that won't help you.
>
> If the raspberry pi is handing out addresses in a different range then you
> need to put your laptop in that range temporarily, log into the pi, and
> reconfigure it to not do that. Unless you intend for it to create its own
> separate network that is.
> On Oct 5, 2015 10:22 PM, "david" <ainut at knology.net> wrote:
>
>> Seems like lately I've forgotten everything I've ever known. <sigh>
>>
>> I need to be able to access subnets at home; everything is behind a
>> firewall to the Internet.
>>
>> My PC's are all dhcp in the 192.168.1.x address space.
>>
>> I'd like to be able to talk to other addresses from these PC's.
>>
>> Specifically:
>> 192.168.7.2 -- Beaglebone Black default IP Address works just fine.
>>
>> but
>>
>> 192.168.10.1 -- particular RPi 2 address from downloaded image does not.
>> Of course, that Pi is a wireless one, while if I turn off the wireless and
>> connect a house cable, it gets assigned 192.168.1.56 (for example) and that
>> works fine.  BUT, the wifi address is still not accessible unless I make
>> the wifi laptop get on the RPi 2 as it's dhcp server and then the laptop
>> gets assigned 192.168.10.x. <sigh>  (Same for the Android tablet.)  How do
>> I get everything to play nice with each other?
>>
>> Bought a NAS server and set it's address to 192.168.200.1 -- and
>> *nothing* in the house could see it until I changed it's address to a
>> 192.168.1.x.
>>
>> Help, please.
>>
>> Thanks,
>> David Merchant
>>
>>
>> _______________________________________________
>> General mailing list - General at lists.makerslocal.org
>> A service of Makers Local 256 - <https://256.makerslocal.org/>
>> https://256.makerslocal.org/
>> http://lists.makerslocal.org/mailman/listinfo/general
>
>
>
> _______________________________________________
> General mailing list - General at lists.makerslocal.org
> A service of Makers Local 256 - https://256.makerslocal.org/http://lists.makerslocal.org/mailman/listinfo/general
>
>
> _______________________________________________
> General mailing list - General at lists.makerslocal.org
> A service of Makers Local 256 - <https://256.makerslocal.org/>
> https://256.makerslocal.org/
> http://lists.makerslocal.org/mailman/listinfo/general
>
>
>
> _______________________________________________
> General mailing list - General at lists.makerslocal.org
> A service of Makers Local 256 - https://256.makerslocal.org/http://lists.makerslocal.org/mailman/listinfo/general
>
>
>
> _______________________________________________
> General mailing list - General at lists.makerslocal.org
> A service of Makers Local 256 - https://256.makerslocal.org/
> http://lists.makerslocal.org/mailman/listinfo/general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.makerslocal.org/pipermail/general/attachments/20151006/4dd1f43f/attachment.html>


More information about the General mailing list