politas has quit [Ping timeout: 190 seconds]
politas has joined #spacedock
Technicalfool has joined #spacedock
HebaruSan has joined #spacedock
<HebaruSan> Hello SpaceDockers (testing my IRC client...)
<VITAS> hi
<VITAS> Micha is all over the Timezones so you and him can talk when hes aliv :)
<VITAS> have you tried logging into the servers?
<HebaruSan> Did you create me an account? I didn't know what user name to use
<HebaruSan> I tried a few possibilities, but all prompted me for my ssh password, so I assumed the key wasn't there
<VITAS> HebaruSan
<HebaruSan> Is the -BackEnd / OpenDock stuff live? Or is it the old codebase
<VITAS> Opendock was i think something Thomas and some others wanted to do
<VITAS> and never finished
<HebaruSan> d'oh, I was trying to ssh into the web host, trying again with the ssh host...
<VITAS> once you get into sd2 you can check whats used
<VITAS> ive one public ipv4 thats why the strange port and split
<HebaruSan> Ah the joy of networks, this just hangs:
<HebaruSan> $ ssh -v -v 'ssh://HebaruSan@sd2.srv.52k.de:20146'
<HebaruSan> OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b 26 Feb 2019
<HebaruSan> debug1: Reading configuration data /home/paul/.ssh/config
<HebaruSan> debug1: Reading configuration data /etc/ssh/ssh_config
<HebaruSan> debug1: /etc/ssh/ssh_config line 19: Applying options for *
<HebaruSan> debug2: resolving "sd2.srv.52k.de" port 20146
<HebaruSan> debug2: ssh_connect_direct
<HebaruSan> debug1: Connecting to sd2.srv.52k.de [88.99.249.174] port 20146.
<HebaruSan> OK that was the wrong port
<HebaruSan> $ ssh -v -v -v 'ssh://HebaruSan@sd2.srv.52k.de:21046'
<HebaruSan> OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b 26 Feb 2019
<HebaruSan> debug1: Reading configuration data /home/paul/.ssh/config
<HebaruSan> debug1: Reading configuration data /etc/ssh/ssh_config
<HebaruSan> debug1: /etc/ssh/ssh_config line 19: Applying options for *
<HebaruSan> debug2: resolving "sd2.srv.52k.de" port 21046
<HebaruSan> debug2: ssh_connect_direct
<HebaruSan> debug1: Connecting to sd2.srv.52k.de [88.99.249.174] port 21046.
<HebaruSan> debug1: connect to address 88.99.249.174 port 21046: Connection refused
<HebaruSan> debug1: Connecting to sd2.srv.52k.de [2a01:4f8:10b:751::9601:46] port 21046.
<HebaruSan> debug1: connect to address 2a01:4f8:10b:751::9601:46 port 21046: Network is unreachable
<HebaruSan> ssh: connect to host sd2.srv.52k.de port 21046: Network is unreachable
<HebaruSan> Do you need to whitelist my IP?
<VITAS> no
<VITAS> let me check
<VITAS> sd2.srv.52k.de 21046 worked for me :/
<VITAS> the only thing i could have done wrong is adding your key
<HebaruSan> I don't think that would cause "Connection refused", it would be a later error in the authentication
<VITAS> yes
<HebaruSan> This is something at the network level
<VITAS> i just connected via the same port and host
<VITAS> and i dont have any blacklist
<VITAS> can you ping the host?
<HebaruSan> Yes, both sd2 and sd6 ping just fine
<VITAS> tcp 0 0 0.0.0.0:21046 0.0.0.0:* LISTEN 15304/sshd off (0.00/0/0)
<VITAS> ive no idea what the problem could be
<VITAS> its strange that both ipv4 and 6 dont work
<VITAS> if i wouldnt be able to connect i would say its firewall related but that works so dont know :/
<VITAS> so still no luck?
<HebaruSan> Yeah, same
<HebaruSan> Do my connection attempts show up in the sshd logging (if that's a thing)?\
<VITAS> lets see if Micha has the same problem
<VITAS> sec
<VITAS> please try again
<HebaruSan> Same
<VITAS> nothing
<VITAS> but i have some tries by Micha
<VITAS> connection closed by authenticating user Micha [preauth]
<VITAS> very strange
<VITAS> can you ping the ipv6?
<VITAS> because theres a difference between revused and unreachable
<VITAS> -v +f
<HebaruSan> ping and ping6 say "Network is unreachable" but I have low confidence in my ipv6 knowledge
<VITAS> can you ping google ipv6?
<HebaruSan> What would that command be?
<HebaruSan> I guess it's possible that my system isn't set up for ipv6 at the moment. Interesting.
<VITAS> ping6 or ping -6 depending on your version of ping
<VITAS> ping6 google.com
<HebaruSan> connect: Network is unreachable
<HebaruSan> So I'll look into that...
<HebaruSan> ifconfig lists an inet6 address for my network card
<HebaruSan> But I suppose that's just between my router and me. OH, my router is old. Hmm.
<HebaruSan> Yeah, assume for the moment that my router doesn't do ipv6. Its status page doesn't have a slot for it.
<VITAS> depends on the ip
<VITAS> fe80 or 2something?
<HebaruSan> fe80::62a4:4cff:feb1:9abb
<VITAS> ive an idea: ill messed up ipv4 and dotn know it because i use ipv6?
<VITAS> yes thats lan only
<VITAS> fe80 is the 192.168 of ipv6
<HebaruSan> I should replace this router anyway
<VITAS> ill test something sec
<VITAS> i can at least now replicate your problem
<VITAS> found the problem and solution now to find a good implementation
<HebaruSan> Nice! And I have confirmed that my ISP claims to support ipv6 and am now router-shopping
<VITAS> win for both of us :D
<VITAS> im a big fan of avm fritz! boxes
<VITAS> i dont know whats wrong with my bash script
<VITAS> ive a temp workarround
<VITAS> try 213xx instead of 210xx
<VITAS> what i know: im running a foreach loop to nat every container from its external port to 22 and that does cause problems if i later want to directly map a container not to 22 but 210xx
<VITAS> (external port=210xx)
<VITAS> ive made an array and and an if case where it applies 1:1 port mappings for those hsots where i changed the default ssh port but its still not working
<VITAS> i wish i had free ip subnets :/
<VITAS> (ipv4)
<HebaruSan> Port 21346 works!!
<VITAS> yes
<VITAS> that confusing description basicly says: i need to make an exception for the sd2&6 hosts but i fail to do so
<VITAS> so ill just take a compleatly other port :D
<VITAS> (for the moment)
<VITAS> Micha and the others need to be informed
<HebaruSan> And I'm also getting some cat7 cables, maybe there'll be a speed boost in this router upgrade
<VITAS> hmm there should be something like dns for ports like "ssh" instead of 22. and if you map ssh to whatever the user doesnt have to know because his computer gets told
<VITAS> cat7? why?
<VITAS> i only use cat6 in projects because its motly gigiabit
<VITAS> everything above (i use) uses fibre
<HebaruSan> We are on cat5, I'll see if cat6 is cheaper...
<VITAS> the only two areas (enduser) routers can make a difference are mdoem and cpu speed (nat& fw performance)
<VITAS> 1gbit demands cat5b
<VITAS> so 6 is plenty
<VITAS> and i guess you dont have 1gbit/s inet con?
<HebaruSan> Hmm, the one cable I checked said cat5e, so maybe that's fine
<VITAS> yes e
<VITAS> not b
<VITAS> my experience is that the speed is mostly determined by the ISP willingness to not throttle it, the cable between their end and yours and their DSLAM (their end)
<VITAS> if its cable inet you have other problems too
<VITAS> like inet usage of your neibours
<HebaruSan> Yup, I'm not expecting to maximize throughput, just don't want the bottleneck to be on my side and maybe a bit of futureproofing
<VITAS> ipv6 would be nice :D
<VITAS> btw hardly any workplace ive been to has it deployed
<HebaruSan> lol why is there a copy of NetKAN checked out in /var/.../htdocs ? :)
<VITAS> htdocs is legecy has nothing to do with "root of webserver"
<VITAS> but yes cleanup as i said :D
<HebaruSan> I just wasn't expecting to see NetKAN there ;)
<VITAS> i mostly dont even know what things do (just (re) learning now)
<HebaruSan> scp'ing the prod code to my local system now...
<VITAS> you can also setup hooks so that the code on the respective systems get autoupdated
<VITAS> (sd2&6)
<VITAS> btw reson i hard coded the domain in places is that the code insists on adding the local hostname (sd1.52k) in front and not the external domain (spacedock.info)
<VITAS> if you can find a solution to that i will be very happy :)
<HebaruSan> scp command finally completed. I probably should have transferred a tar.gz, but oh well, it's done now.
<HebaruSan> I was expecting there to be uncommitted changes, but it's clean, with two commits that aren't on GitHub. So is our task to clean up those two commits so they can be pushed?