[Rack] mchawking ip address still broken
embeddedlinuxguy at gmail.com
Sun Feb 26 22:30:56 PST 2012
A public IP for mchawkins seems like a good solution. I also tried
port forwarding for the video through pony using socat. Unfortunately
while port forwarding works fine on the internal network, I couldn't
connect using pony's public IP:
jesse at pony:~$ MCHAWKING=172.30.0.50:8081
jesse at pony:~$ socat TCP-LISTEN:1111,fork TCP:$MCHAWKING
vlc http://pony.noise:1111/ works but
http://pony.noisebridge.net:1111/ does not.
jesse at barony:~$ nmap -p 1111 pony.noisebridge.net
Nmap scan report for pony.noisebridge.net (184.108.40.206)
1111/tcp closed unknown
jesse at barony:~$ nmap -p 1111 pony.noise
Nmap scan report for pony.noise (172.30.0.30)
rDNS record for 172.30.0.30: pony
1111/tcp open unknown
On Fri, Feb 24, 2012 at 7:31 AM, Jake <jake at spaz.org> wrote:
> So a while ago (last year) the robot, MCHawking, used to have a public IP
> address. It was really handy because I and others were able to work on the
> robot and do whatever we wanted to it from anywhere.
> Something happened to the network, which I know nothing about, and the
> public IP address hasn't worked since. I have asked a couple of people to
> try to fix it and it hasn't happened yet.
> another person has taken interest in the robot, but he is not here often. I
> want him to be able to interact with it from his "work" which is far away.
> That means i want to get the public IP working again.
> Can anyone help get the public IP address working again for the robot,
> mchawking? I certainly can't. The only thing i know how to do with a
> router is reset it when it stops working.
> thank you
> On Tue, 20 Dec 2011, Jonathan Lassoff wrote:
>> On Mon, Dec 19, 2011 at 7:36 PM, Jake <jake at spaz.org> wrote:
>> So the public IP for mchawking is down.. ben was working on it
>> but maybe he's stuck. Do you know what i could do to get it to
>> work again?
>> I feel ya. He might be, I'm not sure.
>> Frankly, I'm annoyed that he decided to take down and replace the
>> fine OpenBSD router/firewall I had setup and documented, but didn't
>> read and convert everything.
>> Mail him and say that it was working fine with r00ter, and that you're
>> to try to switch back to it.
>> That'll get him to fix it. :p
>> I'm only half-joking. If you're really blocking on this, let me know and I
>> can start to dig around and bit and see if I can get ya going.
> Rack mailing list
> Rack at lists.noisebridge.net
More information about the Rack