[X] My Assistant

So for a change no fail on my side (IMG:[invalid] style_emoticons/default/laugh.gif)

maybe something went bonkers when I tried to reboot but something broke, also something was broken witch the KVM thingie since they had to replace some parts.

It's not, and don't worry Ichy we are here to help. But we might as well make some fun of you in the process f you don't mind (*flutter*).

I'm ready for that (IMG:[invalid] style_emoticons/default/tongue.gif)

Shit, you ordered from amazon, yup? It's a no starch press book, you can get 30% off by buying directly from them... (sorry I didn't tell you earlier, I was trying to promote the GNU book)

But with Amazon I don't have free delivery so It may not be more expensive. I live in a small weirdo Country after all.

Now to my Problem. Thanks I have sent them a Support Ticket. Since fasthost is pretty awesome when it comes to support It should not take longer than a hour for them to reply.

Also, esure that you have a srong root password on that seedbox, your IPs are all over the internet now!

No Problem. If someone hacks me he will only find h@ H related stuff in here.
Well for now. Once i am bored of H@h may try to turn it into a torrent seedbox to host torrents for the Gallery.

So for a change no fail on my side (IMG:[invalid] style_emoticons/default/laugh.gif)

maybe something went bonkers when I tried to reboot but something broke, also something was broken witch the KVM thingie since they had to replace some parts.
I'm ready for that (IMG:[invalid] style_emoticons/default/tongue.gif)
But with Amazon I don't have free delivery so It may not be more expensive. I live in a small weirdo Country after all.

Now to my Problem. Thanks I have sent them a Support Ticket. Since fasthost is pretty awesome when it comes to support It should not take longer than a hour for them to reply.
No Problem. If someone hacks me he will only find h@ H related stuff in here.
Well for now. Once i am bored of H@h may try to turn it into a torrent seedbox to host torrents for the Gallery.

Well I may sound paranoid but they might not get "important" information from you but they can use the seedbox for nefarious purposes, which in turn can perma-ban you.

Nah, they will most probably just look at the routing tables. If they confim that the IP goes towards Ichy's box correctly then the issue is with the interface config on the box (although I doubt that's the case).

Well I may sound paranoid but they might not get "important" information from you but they can use the seedbox for nefarious purposes, which in turn can perma-ban you.

Nah, they will most probably just look at the routing tables. If they confim that the IP goes towards Ichy's box correctly then the issue is with the interface config on the box (although I doubt that's the case).

I guess he meant how my Box could be used by evil Hackers and I get banned for this. (would be sad since I like it there)

I guess he meant how my Box could be used by evil Hackers and I get banned for this. (would be sad since I like it there)

Ops, now that you say it it makes more sense that way. Apologies GanGun.

Btw Ichy, stop using the word hacker with a pejorative meaning. A lot of people entitle themselves as hackers with a very good meaning (I am a savannah hacker for an example). GanGun is going to the OHM event according to his signature, that's a hacker event as well. You meant "cracker", just sayin' (IMG:[invalid] style_emoticons/default/rolleyes.gif)

kay!

Now back to our Problem. It is getting weirder and weirder!
In your earlier test you accidentally used a wrong IP 88.208.192.162 instead of 88.208.193.162, 88.208.193.168 and 88.208.193.172

But that is not the Problem here any more. From their tests everything looks okay. I even double checked this by tracerouting to rpc.hentaiathome.net from my server which worked I guess.

CODE

root@server88-208-193-162:~# traceroute rpc.hentaiathome.net
traceroute to rpc.hentaiathome.net (46.21.149.3), 30 hops max, 60 byte packets
1  server88-208-195-254.live-servers.net (88.208.195.254)  0.495 ms  0.485 ms
0.477 ms
2  88.208.255.105 (88.208.255.105)  0.450 ms  0.738 ms  0.728 ms
3  88.208.255.190 (88.208.255.190)  5.347 ms  5.341 ms  5.599 ms
4  ae-1.bb-c.the.lon.gb.oneandone.net (212.227.120.106)  5.315 ms  5.304 ms  5.
560 ms
5  te-1-2.bb-c.nkf.ams.nl.oneandone.net (212.227.120.133)  12.680 ms  12.675 ms
  12.651 ms
6  nikhef.openpeering.nl (195.69.144.189)  12.934 ms  12.952 ms  12.943 ms
7  fiberring.evoswitch.nl-ix.net (193.239.116.159)  13.735 ms  13.729 ms  13.67
8 ms
8  87.255.49.77 (87.255.49.77)  14.008 ms  14.078 ms  14.081 ms
9  subscribe.yangutu.com (46.21.149.3)  14.062 ms !X  14.040 ms !X  14.022 ms !
X
root@server88-208-193-162:~#

Also I tried to start it as root to see if something went wrong with my User setups so I tried starting it as root with java -jar HentaiAtHome.jar --disable_logging but the same problem popped up again.
Also tried to random other ports but it is the same Problem every time!

I even went as far and completely purged one of my Clients, made everything new and tried again.
Same problem (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif)

In your earlier test you accidentally used a wrong IP 88.208.192.162 instead of 88.208.193.162, 88.208.193.168 and 88.208.193.172

Wow, that was stupid. Sorry.

Do not worry about connecting to rpc.hentaiathome.net that shall not be a problem at all. That:

CODE

2013-05-10T14:44:56Z [info] Startup notification failed.

Is an issue with rpc.hentaiathome.net connecting ot your seedbox. (i.e. the other way around.)

I looked at the (correct) IPs now and the response I got are completely different, i.e. nothing replied (now I question myself how do you connect to your box in the first place). Nevertheless, let's try to look at what the seedbox thinks it is doing.

What does:

CODE

ifconfig -a

tells you (on the seedbox)?

Also:

I even went as far and completely purged one of my Clients, made everything new and tried again.
Same problem (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif)

You did not restart the seedbox of the other 2 h@h clients did you? (don't do it)

This post has been edited by blue penguin: May 12 2013, 14:59

Wow, that was stupid. Sorry.

No Problem.

Is an issue with rpc.hentaiathome.net connecting ot your seedbox. (i.e. the other way around.)

I looked at the (correct) IPs now and the response I got are completely different, i.e. nothing replied (now I question myself how do you connect to your box in the first place).

SSH access works as usual.

Nevertheless, let's try to look at what the seedbox thinks it is doing.

ifconfig -a tells me:

CODE

Last login: my IP
root@server88-208-193-162:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:19:99:80:7e:4b
          inet addr:88.208.193.162  Bcast:88.208.195.255  Mask:255.255.252.0
          inet6 addr: fe80::219:99ff:fe80:7e4b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:533915 errors:0 dropped:0 overruns:0 frame:0
          TX packets:362975 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:67878735 (67.8 MB)  TX bytes:78611768 (78.6 MB)
          Interrupt:23 Memory:fc400000-fc420000

eth0:1    Link encap:Ethernet  HWaddr 00:19:99:80:7e:4b
          inet addr:88.208.193.168  Bcast:88.208.195.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:23 Memory:fc400000-fc420000

eth0:2    Link encap:Ethernet  HWaddr 00:19:99:80:7e:4b
          inet addr:88.208.193.172  Bcast:88.208.195.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:23 Memory:fc400000-fc420000

eth0:3    Link encap:Ethernet  HWaddr 00:19:99:80:7e:4b
          inet addr:88.208.192.162  Bcast:88.208.195.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:23 Memory:fc400000-fc420000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:200 (200.0 B)  TX bytes:200 (200.0 B)

root@server88-208-193-162:~#

???

You did not restart the seedbox of the other 2 h@h clients did you? (don't do it)

I tried yesterday but after i got the same error with the other IPs I stopped trying with them and only tested with the first client and main IP.

This post has been edited by Ichy: May 12 2013, 17:11

SSH access works as usual.

I see TCP traffic is allowed, but ping's protocol is blocked from your box. The ssh RSA keys on all three IPs are the same so we can be 99.999999999% sure that the network points all IPs to your box alright.

That:

CODE

eth0      Link encap:Ethernet  HWaddr 00:19:99:80:7e:4b
          inet addr:88.208.193.162  Bcast:88.208.195.255  Mask:255.255.252.0

eth0:3    Link encap:Ethernet  HWaddr 00:19:99:80:7e:4b
          inet addr:88.208.192.162  Bcast:88.208.195.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:23 Memory:fc400000-fc420000

Two interfaces with the same IP do not look promissing. I'd never setup a multi IP on the same ethernet card, but this seems pretty dodgy to me.

Could you try to ping (from inside the sedbox) all three IPs? please. If the pings are doing alright we will check the ports that h@h is using.

I tried yesterday but after i got the same error with the other IPs I stopped trying with them and only tested with the first client and main IP.

So, currently only only 1 h@h is running correctly, yes?

This post has been edited by blue penguin: May 12 2013, 17:37

protip: Remove this from your post (I'll remove it from mine once I am aware that you read it):

Edited out.

Could you try to ping (from inside the sedbox) all three IPs? please. If the pings are doing alright we will check the ports that h@h is using.

Sure

CODE

64 bytes from 88.208.193.162: icmp_req=64 ttl=64 time=0.037 ms
64 bytes from 88.208.193.162: icmp_req=65 ttl=64 time=0.019 ms
64 bytes from 88.208.193.162: icmp_req=66 ttl=64 time=0.016 ms
64 bytes from 88.208.193.162: icmp_req=67 ttl=64 time=0.019 ms
64 bytes from 88.208.193.162: icmp_req=68 ttl=64 time=0.016 ms
64 bytes from 88.208.193.162: icmp_req=69 ttl=64 time=0.016 ms
64 bytes from 88.208.193.162: icmp_req=70 ttl=64 time=0.028 ms
64 bytes from 88.208.193.162: icmp_req=71 ttl=64 time=0.017 ms
64 bytes from 88.208.193.162: icmp_req=72 ttl=64 time=0.015 ms
64 bytes from 88.208.193.162: icmp_req=73 ttl=64 time=0.017 ms
64 bytes from 88.208.193.162: icmp_req=74 ttl=64 time=0.017 ms
64 bytes from 88.208.193.162: icmp_req=75 ttl=64 time=0.015 ms
64 bytes from 88.208.193.162: icmp_req=76 ttl=64 time=0.014 ms
^C
--- 88.208.193.162 ping statistics ---
76 packets transmitted, 76 received, 0% packet loss, time 74997ms
rtt min/avg/max/mdev = 0.014/0.017/0.040/0.006 ms

CODE

64 bytes from 88.208.193.168: icmp_req=9 ttl=64 time=0.019 ms
64 bytes from 88.208.193.168: icmp_req=10 ttl=64 time=0.016 ms
64 bytes from 88.208.193.168: icmp_req=11 ttl=64 time=0.014 ms
64 bytes from 88.208.193.168: icmp_req=12 ttl=64 time=0.025 ms
64 bytes from 88.208.193.168: icmp_req=13 ttl=64 time=0.016 ms
64 bytes from 88.208.193.168: icmp_req=14 ttl=64 time=0.014 ms
64 bytes from 88.208.193.168: icmp_req=15 ttl=64 time=0.018 ms
64 bytes from 88.208.193.168: icmp_req=16 ttl=64 time=0.016 ms
64 bytes from 88.208.193.168: icmp_req=17 ttl=64 time=0.015 ms
64 bytes from 88.208.193.168: icmp_req=18 ttl=64 time=0.015 ms
64 bytes from 88.208.193.168: icmp_req=19 ttl=64 time=0.013 ms
^C
--- 88.208.193.168 ping statistics ---
19 packets transmitted, 19 received, 0% packet loss, time 17999ms
rtt min/avg/max/mdev = 0.013/0.019/0.042/0.009 ms

CODE

64 bytes from 88.208.193.172: icmp_req=18 ttl=64 time=0.014 ms
64 bytes from 88.208.193.172: icmp_req=19 ttl=64 time=0.013 ms
64 bytes from 88.208.193.172: icmp_req=20 ttl=64 time=0.017 ms
64 bytes from 88.208.193.172: icmp_req=21 ttl=64 time=0.015 ms
64 bytes from 88.208.193.172: icmp_req=22 ttl=64 time=0.014 ms
64 bytes from 88.208.193.172: icmp_req=23 ttl=64 time=0.017 ms
64 bytes from 88.208.193.172: icmp_req=24 ttl=64 time=0.015 ms
64 bytes from 88.208.193.172: icmp_req=25 ttl=64 time=0.016 ms
64 bytes from 88.208.193.172: icmp_req=26 ttl=64 time=0.020 ms
64 bytes from 88.208.193.172: icmp_req=27 ttl=64 time=0.015 ms
^C
--- 88.208.193.172 ping statistics ---
27 packets transmitted, 27 received, 0% packet loss, time 25997ms
rtt min/avg/max/mdev = 0.013/0.016/0.037/0.006 ms

It seems endless so I ctrl+c to make it stop.

So, currently only only 1 h@h is running correctly, yes?

Nope currently none is running. I stopped it after I got the error. Should I keep it active?

Edited out.

Thanks, edited out on my post as well.

It seems endless so I ctrl+c to make it stop.

Yup, by default it tries an infinite number of times.

Nope currently none is running. I stopped it after I got the error. Should I keep it active?

Could you reboot the seedbox and then try to start each of the h@h clients, please? I am a little lost where exactly we are and that will set me back on track (for example, moments ago I was still thinking that 2 of the h@h clients are still running).

The pings are alright, we will try checking the ports in a moment.

Sure.
Server has now rebooted and now all 3 Clients got the error but are still active.

OK, here we go then, we will simulate how rpc.hentaiathome.net sees your seedbox and h@h clients:

Legend: You will need to substitute a few things in the commands, I marked them as <thing to substitue>. For example: "<IP for the seedbox>" shall be substituted to "88.208.193.168". i.e. you substitute the <> symbols as well.

1st Shutdown all h@h clients
2nd Ensure that you can run the program "telnet" from your PC, it run in the command line window. It is the most basic networking program but microsoft started to disable it in the recent vesions of MS windows (I've heard). If you cannot run it google for "enable telnet in windows 7".
3rd annotate on a piece of paper the IP and PORT each of the h@hs, that thingies you get from https://e-hentai.org/hentaiathome.php . Basically the IPs we were trying in the past posts plus the PORTs.
4th For each of the ports run on the seedbox:

CODE

netstat -an | grep <PORT>

and no output shall appear.
5th Now for each of the h@h clients follow the procedure:

Run on the seedbox:

CODE

perl -e 'use strict; use warnings; use IO::Socket; my ($lh, $lp) = ("<THE IP>", <THE PORT>); my $sock = new IO::Socket::INET (LocalHost => $lh, LocalPort => $lp, Proto => "tcp", Listen => 1, Reuse => 1) or die "Crap, I cannot even create socket: $!"; my $asock = $sock->accept; print while <$asock>; close $asock;'

it will hang. Leave the window open and open a DOS box to run telnet. (PS: that <$asock> do not need to be substituted by anything, leave it like that).
Then run on your PC

CODE

telnet <THE IP> <THE PORT>

If telnet produces this output:

CODE

telnet 127.0.0.1 33666
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

all is good. Now whatever you type on the PC's command window (and hit return) appears on the seedbox (magic!). To exit from the telnet type Ctrl+] end then return, then type q and return, it will close the hanging command on the seedbox as well.
But if the output from the telnet looks similar to this one:

CODE

telnet 192.168.0.102 33666
Trying 192.168.0.102...
telnet: connect to address 192.168.0.102: No route to host

then we have problems.

This basically opens a socket on the seedbox and connects to it using telnet from your PC. Therefore it is very important that <THE IP> and <THE PORT> be exactly the same on both commands.

Crap... I just missed a HV hourlie battle while typing and testing this.

But if the output from the telnet looks similar to this one: then we have problems.

(IMG:[invalid] style_emoticons/default/sad.gif)

(IMG:[s14.directupload.net] http://s14.directupload.net/images/130512/wu95b8c2.jpg)
Basically the German edition of the error we should not have...

Sadly no mistake on my side because I tried twice to make sure. With all IPs.

Crap... I just missed a HV hourlie battle while typing and testing this.

You can have the Pots I got from mine. Remember when we got Equipment from hourlies? (IMG:[invalid] style_emoticons/default/dry.gif)

(IMG:[s14.directupload.net] http://s14.directupload.net/images/130512/wu95b8c2.jpg)
Basically the German edition of the error we should not have...

Most probably the ports are locked (like a firewall). But before we go aftert the guys at fasthosts let's try a few ports that are unlikely to be blocked.

Try to run that perl and telnet on the following ports: 20, 23, 80, 8080 and 8081. i.e. first check if the port is not already in used with:

CODE

netstat -an | grep <PORT>

(no output means that the port is not in use). And if the port is NOT in use run the perl and check with telnet on your PC.

It is very unlikely that por 80 is blocked. And it is very likely that netstat will have some output for port 20 (and you will not be able to run the perl or telnet on it thereof).

If we find some ports that can be used we will simply use these for h@h. And effectively overcome the blockade.

You can have the Pots I got from mine. Remember when we got Equipment from hourlies? (IMG:[invalid] style_emoticons/default/dry.gif)

I still get equips from REs, I just got a Fair Cotton Cap of the Thunder-Child and a Fine Longsword of Balance earlier (IMG:[invalid] style_emoticons/default/smile.gif)

20 - in use
23 - in use
80 - in use
8080 - not in use - same error like the other ports
8081 - not in use - same error like the other ports

I still get equips from REs, I just got a Fair Cotton Cap of the Thunder-Child and a Fine Longsword of Balance earlier

When Tenb changed the RE atthe beginning I often got Exquisites of even above out of them (IMG:[invalid] style_emoticons/default/anime_cry.gif)

Can you paste the "netstat -an | grep 80" output, please? That command is just a quick hack and might lie sometimes, I doubt that port 80 is in actually use. Well, unless you are running a web server on that seedbox.

CODE

root@server88-208-193-162:~# netstat -an | grep 80
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN
udp6       0      0 fe80::219:99ff:fe80:123 :::*
unix  2      [ ACC ]     STREAM     LISTENING     8803     /var/run/apache2/cgis
ock.1339
unix  2      [ ACC ]     STREAM     LISTENING     8680     private/scache
unix  2      [ ]         DGRAM                    9803

This post has been edited by Ichy: May 12 2013, 21:08

Wow, are you running a web server there? Something is really using that port...

Run:

CODE

lsof | grep TCP | grep 80

to see what is running on that port, please.

Before we go after the guys at fasthost we shall prove that what we are doing is correct. And that's the perfect port to prove it.

This post has been edited by blue penguin: May 12 2013, 21:16

perl -e 'use strict; use warnings; use IO::Socket; my ($lh, $lp) = ("88.208.193.162", 80); my $sock = new IO::Socket::INET (LocalHost => $lh, LocalPort => $lp, Proto => "tcp", Listen => 1, Reuse => 1) or die "Crap, I cannot even create socket: $!"; my $asock = $sock->accept; print while <$asock>; close $asock;'

gives me:

CODE

Crap, I cannot even create socket: Address already in use at -e line 1.

/edit: oh you edited your post (IMG:[invalid] style_emoticons/default/laugh.gif)

This post has been edited by Ichy: May 12 2013, 21:16