Language:
switch to room list switch to menu My folders
Go to page: First ... 43 44 45 46 [47] 48 49 50 51 ... Last
[#] Sun Mar 28 2010 21:52:04 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I don't remember now. But that's what I use and I'm happy with it. :-)

[#] Sun Mar 28 2010 21:52:19 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

maybe that the 'p' reminds me of putty. :-)

[#] Thu Apr 01 2010 10:19:25 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


So, I spent a couple of hours this morning, trying to figure out how to make it possible for me to connect to my linux machine at home. It seems straightforward enough; forward port 22 from my hardware firewall to the linux machine, and make sure the port is open and accepting connections from anywhere on the linux machine.

But, apparently, I don't quite get how that works. I can easily connect to port 22 on the darned machine from within my own network, but if it comes from outside, it won't connect. I don't see anything in the configuration file to suggest a solution, either.

So, I gave up, and tried doing what I needed to do from home. That's when I found out that my version of Ubuntu is apparently too old for the software I'm trying to cross-compile (I have the latest cross-compiler environment available for my version of Ubuntu, but it isn't current enough for the software I want to compile).

Grrr...

So, I lost about an hour or two on this nonsense.

I love open-source, when I have plenty of time to futz with it.

[#] Thu Apr 01 2010 12:22:16 EDT from dothebart @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

try ssh'ing back from uncensored when you're at home, and watch tcpdump.

thats usualy what brings the solution on forwarding/gatewaying problems.



[#] Thu Apr 01 2010 15:21:00 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


I'll give that a look-see when I get home.

[#] Fri Apr 02 2010 00:20:46 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

It *should* be that simple. I wonder if you didn't quite get the firewall configuration correct.

[#] Fri Apr 02 2010 08:36:17 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


How hard is it to forward a port? I forward port 80 to the same box. You would think forwarding port 22 isn't that different.

[#] Sat Apr 03 2010 01:28:34 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Yes, it's different. It's 58 different, in fact.

[#] Sun Apr 04 2010 20:12:14 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


How hard is it to forward a port? I forward port 80 to the same box.


unless your ISP is blocking port 22.
try running on port 25 or 110

[#] Sun Apr 04 2010 21:21:41 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Hmm... I know that I can SMTP to the machine, and my ISP has no reason to block ports (it's DSL).  But it would be interesting to find out, no?



[#] Mon Apr 05 2010 22:19:30 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

what's your ip, we can try it from elsewhere.

[#] Tue Apr 06 2010 06:55:43 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

It's at fleeb.net (you can ping it).



[#] Tue Apr 06 2010 14:21:20 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Can't ping it. Port 80 does appear to be open, though. Port 22 is not.

[#] Tue Apr 06 2010 16:01:26 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


Port 22 probably would not be. However, port 23 should be.

I forgot that pings won't work... but, yeah, port 80 should be good (I never did get Citadel running properly again).

[#] Tue Apr 06 2010 20:07:10 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

 

Tue Apr 06 2010 16:01:26 EDT from fleeb @ Uncensored

Port 22 probably would not be. However, port 23 should be.

I forgot that pings won't work... but, yeah, port 80 should be good (I never did get Citadel running properly again).

Bah, I'm an idiot.. it *is* port 22.  And the firewall is indeed forwarding it, just as it does port 80.

So something else is going on.  I can access the box from port 22 within my LAN at home, so I know that the machine is listening on port 22.  And my settings on the hardware firewall are identical to the settings I have for port 80.

That leaves something else on the Linux box that's preventing incoming connections from working on that port for some reason.



[#] Tue Apr 06 2010 22:29:25 EDT from ycm @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

 

Tue Apr 06 2010 08:07:10 PM EDT from fleeb @ Uncensored

So something else is going on.  I can access the box from port 22 within my LAN at home, so I know that the machine is listening on port 22.  And my settings on the hardware firewall are identical to the settings I have for port 80.

Actually, you might want to check if you have host checking, and you might also want to check what sshd is listening for.




[#] Tue Apr 06 2010 22:52:55 EDT from ycm @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]



[#] Wed Apr 07 2010 08:40:53 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


The sshd.conf file didn't seem very illuminating that way.

[#] Wed Apr 07 2010 13:29:48 EDT from ycm @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Check the following in your conf :

ListenAddress

That directive tells sshd what addresses to listen on. It might be badly set.



[#] Wed Apr 07 2010 17:57:06 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


I'll give that a look-see at home.

Go to page: First ... 43 44 45 46 [47] 48 49 50 51 ... Last