<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I would hazard a guess that the school implemented client isolation
(or some variant) to keep wireless clients from being able to
communicate/hack/etc each other. If so there is not much that can
be done with the school wifi.<br>
<br>
The clear way around this is to set up your own Pi wifi access point
- then everyone in your lab can enjoy unimpeded communications. I
have found that an adhoc network is at least as much trouble to set
up as a proper NAT access point. hostap and the create_ap script in
the link you provided below should make it relatively easy. For
icing on the cake, NAT your wifi private network out to the school
network and wait for the wrdsb net admins to descend...<br>
<br>
I'm sure this list will be glad to help out with any questions that
pop up. Start off by understanding the NAT configuration - wifi is
just an extension of that.<br>
<br>
Happy hacking, <br>
Lori<br>
<br>
<div class="moz-cite-prefix">On 01/20/2015 05:38 PM, Keefer Rourke
wrote:<br>
</div>
<blockquote
cite="mid:CAGiaHMd+ZgXwA1782-Pz=x86C1hnG4uo6bec0p6w9NPCe=Mo0g@mail.gmail.com"
type="cite">
<p dir="ltr">Alright, so I'll do an nmap port scan (sorry, wrdsb
net admins) tomorrow when I get to the school, and try various
unblocked ports.</p>
<p dir="ltr">If nothing works, the Pi is equipped with a wireless
dongle that can be configured as an access point, so an ad hoc
network could be set up, probably. Though I've never had any
experience with networking and I'm unsure of how to actually get
one running.</p>
<p dir="ltr">Consulting the Arch Wiki <<a
moz-do-not-send="true"
href="https://wiki.archlinux.org/index.php/Software_access_point">https://wiki.archlinux.org/index.php/Software_access_point</a>>
reveals that there are several methods of creating access
points. I'm not really sure which is easiest, or which is ideal.
Again, I'm just trying to connect two machines, my laptop and
the Pi. As someone new to networking, can anyone offer me any
advice? Thanks!</p>
<p dir="ltr">Cheers,<br>
Keefer</p>
<p dir="ltr">(Sent from my mobile phone)</p>
<div class="gmail_quote">On Jan 20, 2015 10:56 AM,
"CrankyOldBugger" <<a moz-do-not-send="true"
href="mailto:crankyoldbugger@gmail.com">crankyoldbugger@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">If it's just
the laptop and the Pi, then Port Forwarding isn't relevant
here.<br>
<br>
<div>
<div>My guess is that since you have root on the Raspi,
first make a backup copy of the /etc/ssh/sshd_config file,
then in there change the port to an unblocked port (look
for Port 22 then change the 22 to whatever), then do the
ssh ... -p on your laptop as I mentioned earlier.</div>
<div><br>
</div>
<div>On the other hand... I'm not overly familiar with the
Raspi, but would an ad-hoc network be a consideration?</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">On Tue Jan 20 2015 at 10:21:59 AM
Keefer Rourke <<a moz-do-not-send="true"
href="mailto:keefer.rourke@gmail.com" target="_blank">keefer.rourke@gmail.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I'm actually trying to SSH into a Raspberry
Pi that is on the same network as my laptop. The only
time the two machines need to connect is when they are
both at the school, and in the same room, since my
laptop will just be used as a remote control station to
send commands to the pi to make the robot do things
(that was probably poorly explained, but hopefully you
get the gist). Though I'm not very familiar with the
concept, I don't think port forwarding is really an
option?
<div><br>
</div>
<div>If it makes a difference, I have complete root
access to the Raspberry Pi which is running Arch Linux
ARM (for the sole reason that the package manager
actually works on the school network), so I can change
anything on the machine as necessary.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 20 January 2015 at 10:10,
CrankyOldBugger <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:crankyoldbugger@gmail.com"
target="_blank">crankyoldbugger@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I
take it that you're trying to SSH to a computer that
you own? If that's the case you can just set up
Port Forwarding on your router. Then you can pick
some wild port number, up to 65535, I think, and
have your home router redirect that port to port 22
on your home computer.<br>
<div><br>
</div>
<div>I've got all of my home Linux boxes set up this
way, then I use DynDNS to get the names straight.
So if I'm at work (which seem to like blocking the
useful ports for some reason), I can SSH to my
Ubuntu desktop using:</div>
<div><br>
</div>
<div>ssh <a moz-do-not-send="true"
href="mailto:user@ubuntubox.org" target="_blank">user@ubuntubox.org</a>
-p 45678</div>
<div><br>
</div>
<div>So I'm using port 45678 to get out of the
office. Then on my home router, port forwarding
knows that port 45678 should be forwarded to my
Ubuntu box's internal IP (192.168.x.x), using port
22 between the router and the desktop.</div>
<div><br>
</div>
<div>You just need to do some playing around to see
if port "45678" (or any other port over 1024) is
open at the school.</div>
<div><br>
</div>
<div><span style="line-height:1.5">Now if you're
trying to connect to a machine that someone else
owns, well that's a different story... I wonder
if you could set up a proxy server at home that
points back out to the internet?</span><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">
<div>
<div>On Tue Jan 20 2015 at 9:58:10 AM Keefer
Rourke <<a moz-do-not-send="true"
href="mailto:keefer.rourke@gmail.com"
target="_blank">keefer.rourke@gmail.com</a>>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div>
<div>
<div dir="ltr">For some strange reason, I've
found high school institutions to be <i>extremely</i> *NIX-phobic.
And they, or at least my particular
school, seem to be becoming increasingly
so. Previously I had only noticed
firewalls in place which block all traffic
from major Linux package managers like apt
and yum, though this never affected me as
I've never had an issue updating my Arch
Linux installation while on the school
network.
<div><br>
</div>
<div>However, things appear to have
changed as SSH connections are now also
blocked. Before the winter holidays I
could use secure shell at school to my
heart's content, but now that people in
my computer engineering class are
beginning to use it more often so they
can remotely connect to their headless
Raspberry Pis (with which we're supposed
to be controlling robots), the protocol
has conveniently stopped working (I'm
guess the board discovered this
"unusual" traffic and decided to block
it). I now find myself needing a way to
get around this problem, or my summative
project will have come to an effective
halt.</div>
<div><br>
</div>
<div>As a suggested work-around, I tried
changing the default port on the host
(the pi) from 22, to 443, and
establishing a connection to that port
from my laptop, but the connection still
times out after a few minutes. I'm
wondering if, either I'm doing something
wrong with the port configurations
(though the verbose output from SSH
would suggest otherwise), or if there is
another solution to getting around the
WRDSB's apparent hatred of free
technology.</div>
<div><br>
</div>
<div>My teacher suggested that we create a
subnetwork between the two machines,
which I will try today, but if there are
any alternative solutions, I'd love to
know of them. Anyone else run into
problems like this?<br clear="all">
<div><br>
</div>
-- <br>
<div>Cheers,
<div>Keefer</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
kwlug-disc mailing list<br>
<a moz-do-not-send="true"
href="mailto:kwlug-disc@kwlug.org"
target="_blank">kwlug-disc@kwlug.org</a><br>
<a moz-do-not-send="true"
href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org"
target="_blank">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
</blockquote>
</div>
<br>
_______________________________________________<br>
kwlug-disc mailing list<br>
<a moz-do-not-send="true"
href="mailto:kwlug-disc@kwlug.org" target="_blank">kwlug-disc@kwlug.org</a><br>
<a moz-do-not-send="true"
href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org"
target="_blank">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Cheers,
<div>Keefer</div>
</div>
</div>
_______________________________________________<br>
kwlug-disc mailing list<br>
<a moz-do-not-send="true"
href="mailto:kwlug-disc@kwlug.org" target="_blank">kwlug-disc@kwlug.org</a><br>
<a moz-do-not-send="true"
href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org"
target="_blank">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
</blockquote>
</div>
<br>
_______________________________________________<br>
kwlug-disc mailing list<br>
<a moz-do-not-send="true" href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a><br>
<a moz-do-not-send="true"
href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org"
target="_blank">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
kwlug-disc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a>
<a class="moz-txt-link-freetext" href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a>
</pre>
</blockquote>
<br>
</body>
</html>