- #Portforward network utilities key 2.0.5 software#
- #Portforward network utilities key 2.0.5 download#
Oct 5 19:01:01 quasar sshd: debug1: rexec start in 4 out 4 newsock 4 pipe 6 sock 7 Oct 5 18:58:18 quasar sshd: debug1: PAM: initializing for "gb119" Oct 5 18:58:18 quasar sshd: debug2: monitor_read: 7 used once, disabling now Oct 5 18:58:18 quasar sshd: debug2: monitor_read: 5 used once, disabling now Oct 5 18:58:18 quasar sshd: debug2: monitor_read: 0 used once, disabling now Oct 5 18:58:18 quasar sshd: debug2: Network child is on pid 8914 Oct 5 18:58:18 quasar sshd: debug2: fd 3 setting O_NONBLOCK Oct 5 18:58:18 quasar sshd: debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-9etch2ex2 Oct 5 18:58:18 quasar sshd: debug1: Enabling compatibility mode for protocol 2.0 Oct 5 18:58:18 quasar sshd: debug1: match: OpenSSH_4.6 pat OpenSSH*
#Portforward network utilities key 2.0.5 software#
Oct 5 18:58:18 quasar sshd: debug1: Client protocol version 2.0 client software version OpenSSH_4.6 Oct 5 18:58:18 quasar sshd: debug1: inetd sockets after dupping: 3, 3 Oct 5 18:58:17 quasar sshd: debug1: Forked child 8913. Oct 5 18:58:17 quasar sshd: debug1: rexec start in 4 out 4 newsock 4 pipe 6 sock 7 Oct 5 18:57:59 quasar sshd: debug1: PAM: cleanup Oct 5 18:57:59 quasar sshd: (pam_unix) session closed for user gb119 Going to quasar - the bubba2 machine I get: With port forwarding on my router to nova - the Ubunut dekstop - both connect normally. Going the other way, the only thing I've got open is the ssh port, so with sshd on the bubba2 logging in debug2 and connecting from two remote ssh clients (.uk is in the same machine room as but isn't actually the same machine, .uk is in a different University: So only nova - the Ubunut desktop - gets the data from but the bubba2 server connects but no data.
#Portforward network utilities key 2.0.5 download#
So both machines get to ok and download wget -18:13:49. Ok quasar is my bubba2, nova is my Ubuntu wget Īny thoughts of where I should be looking ?Įek wrote:I you have an ssh connection on the B2Īre you using wget/ping/telnet to check connectivity?
That leaves me suspecting something in the bubba's kernel that isn't liking some aspect of that incoming packets following the initial connection but I'm an experimental physicist and not a kernel hacker. I'd suspect the router was doing something stupid, except that it works for some hosts and everything works on the desktop. I've not been able to figure out a rule for which extneral machines work and which don't, but it might be related to some level of firewalls at the far end (physically the 'bad' machines are all on the same network segment which unfortunately happens to be my lab ) but regardless of this I'm suspecting the bubba2 since my Ubuntu desktop does everything as expected. I'm using wget to check for http data reception on both machines. I've tried stopping the WAN port from being configured (not entirely sure why I thought that might help). thanks for making sure the power button does a clean shutdown ). I've tried deleting the iptables firewall (after a certain amount of LARTting myself by not changing the policy on the INPUT chain before flushing it. Looking at the sshd logs, again the problematic hosts are opening a connection but no data gets through. I can connect from the bubba2 (by first ssh'ing into it from the desktop) to all things that I can connect from the desktop but from some of them I get a hang without receiving any data and likewise, if I set a suitable inbound rule on the router can log into it from some but not all internet machines that I have access to. If I set a suitable port forward rule I can connect inbound from the internet to the desktops ssh server. I can connect from the desktop machine to all external websites and ssh servers and anything else that I expect to be able to reach. Both machines are configured to be on a subnet of the 10.x.x.x private address space as is the inward side of the router. I have my bubba 2 connected via it's LAN port to a separate ADSL modem/router/wireless AP. I've been trying to track down a problem I've been having with logging in via ssh to my bubba2 and have now gotten something really weird.