<div dir="ltr"><a href="https://www.raspberrypi.org/documentation/troubleshooting/hardware/networking/ip-address.md">https://www.raspberrypi.org/documentation/troubleshooting/hardware/networking/ip-address.md</a><div><br></div><div>do you have another linux device? If so, you can use nmap to discover the connections on the network - one of which is hopefully your pi.</div><div><br></div><div>I'm not sure what too you could use for windows, but there has to be one: arp -a maybe?</div><div><br></div><div>I had SEVERE problems with my pi working on a network -- because the cat5 cable I had was a POS. Once I swapped it out, all of the problems I had with the pi disappeared.</div><div><br></div><div>don't kick puppies. :)</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 6, 2015 at 11:05 AM, david <span dir="ltr"><<a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
I can't get into the RPi 2. Bah. Just downloaded a new image to an
SD card and I cannot ssh. <br>
Can't login direct because I can't find the stupid small HDMI-normal
HDMI cable now. Keyboard and mouse are connected via USB hub but I
can't see the output. Grrrr.<br>
<br>
I don't know if this new image uses a static IP for itself but I
think so. It *should* be at 192.186.10.1 on wireless but can't find
out it's address on wired. <br>
<br>
Think I'll go out and kick some puppies.<span class="HOEnZb"><font color="#888888"><br>
<br>
David</font></span><div><div class="h5"><br>
<br>
<br>
<br>
<br>
<div>On 10/06/2015 08:28 AM, Michael Patton
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'm late to the game but are you still having
problems?
<div><br>
</div>
<div>I had issues with my rpi last year and dhcp not working
blah blah.</div>
<div><br>
</div>
<div>What does your: <span style="color:black;font-family:monospace,Courier;font-size:14px;line-height:1.3em;background-color:rgb(249,249,249)">sudo
cat /etc/network/interfaces say?</span></div>
<div><span style="color:black;font-family:monospace,Courier;font-size:14px;line-height:1.3em;background-color:rgb(249,249,249)"><br>
</span></div>
<div><span style="color:black;font-family:monospace,Courier;font-size:14px;line-height:1.3em;background-color:rgb(249,249,249)">Have
you set up the static IP in there?</span></div>
<div><span style="color:black;font-family:monospace,Courier;font-size:14px;line-height:1.3em;background-color:rgb(249,249,249)"><br>
Sorry if you answered this already and I'm assuming you have
-- I need more coffee.</span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Oct 5, 2015 at 11:10 PM, david
<span dir="ltr"><<a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> I got the router
setup. It's the PC's (Linux and one Winblows) that I now
need to also configure.<br>
Strange that .7.2 would work already, but not .10.1.<span><font color="#888888"><br>
<br>
David</font></span>
<div>
<div><br>
<br>
<br>
<br>
<div>On 10/05/2015 10:59 PM, James Fluhler wrote:<br>
</div>
<blockquote type="cite">
<div>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.### </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>Just a few thoughts maybe someone has better
suggestions<br>
<br>
James F.</div>
<div><br>
On Oct 5, 2015, at 10:37 PM, david <<a href="mailto:ainut@knology.net" target="_blank"></a><a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div> 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...<br>
<br>
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.)<br>
<br>
Thanks,<br>
David<br>
<br>
<br>
<br>
<div>On 10/05/2015 10:32 PM, Hunter Fuller
wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">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.</p>
<p dir="ltr">Routers are capable of breaking
this boundary, but of course your router can
only know about <a href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a> so that
won't help you. </p>
<p dir="ltr">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. </p>
<div class="gmail_quote">On Oct 5, 2015 10:22
PM, "david" <<a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Seems like
lately I've forgotten everything I've ever
known. <sigh><br>
<br>
I need to be able to access subnets at
home; everything is behind a firewall to
the Internet.<br>
<br>
My PC's are all dhcp in the 192.168.1.x
address space.<br>
<br>
I'd like to be able to talk to other
addresses from these PC's.<br>
<br>
Specifically:<br>
192.168.7.2 -- Beaglebone Black default IP
Address works just fine.<br>
<br>
but<br>
<br>
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?<br>
<br>
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.<br>
<br>
Help, please.<br>
<br>
Thanks,<br>
David Merchant<br>
<br>
<br>
_______________________________________________<br>
General mailing list - <a href="mailto:General@lists.makerslocal.org" target="_blank"></a><a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
A service of Makers Local 256 - <a href="https://256.makerslocal.org/" target="_blank"></a><a href="https://256.makerslocal.org/" target="_blank">https://256.makerslocal.org/</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" rel="noreferrer" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a></blockquote>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
General mailing list - <a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a>
A service of Makers Local 256 - <a href="https://256.makerslocal.org/" target="_blank">https://256.makerslocal.org/</a>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>General mailing list - <a href="mailto:General@lists.makerslocal.org" target="_blank"></a><a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a></span><br>
<span>A service of Makers Local 256 - <a href="https://256.makerslocal.org/" target="_blank"></a><a href="https://256.makerslocal.org/" target="_blank">https://256.makerslocal.org/</a></span><br>
<span><a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a></span></div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
General mailing list - <a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a>
A service of Makers Local 256 - <a href="https://256.makerslocal.org/" target="_blank">https://256.makerslocal.org/</a>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General mailing list - <a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
A service of Makers Local 256 - <a href="https://256.makerslocal.org/" rel="noreferrer" target="_blank">https://256.makerslocal.org/</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" rel="noreferrer" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
General mailing list - <a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a>
A service of Makers Local 256 - <a href="https://256.makerslocal.org/" target="_blank">https://256.makerslocal.org/</a>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
General mailing list - <a href="mailto:General@lists.makerslocal.org">General@lists.makerslocal.org</a><br>
A service of Makers Local 256 - <a href="https://256.makerslocal.org/" rel="noreferrer" target="_blank">https://256.makerslocal.org/</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" rel="noreferrer" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br></blockquote></div><br></div>