You are not logged in.

Pages: 1

#1 2008-12-03 17:33:49

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

[SOLVED]mini web server droopy problems

Hi, I've installed arch a few days ago and I only can say its superb, but I'm having some problems using droopy a mini web server that allows other people to upload files to my pc. http://stackp.online.fr/?p=28

I installed it, run it 

$ droopy
Configuration found in /home/envy/.droopy
Files will be uploaded to /home/envy/subidas
HTTP server running... Check it out at http://localhost:8000
localhost.localdomain - - [03/Dec/2008 18:18:51] "GET / HTTP/1.1" 200 -

It just work fine if I type http://localhost:8000/ on firefox, but when I try to use my real ip firefox gets connection refused and nobody including me can view droopy's web :S. First i though was iptables issue but afeter a few hours fighting I decided to delete all rules... and now i have 

$ sudo iptables -L
Contraseña:
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     tcp  --  anywhere             anywhere            tcp spt:8000 
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:8000 

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:8000 
ACCEPT     udp  --  anywhere             anywhere            udp spt:8000

And it still doesn't work sad any ideas? Thanks smile

Last edited by dolmoboy (2008-12-09 21:41:11)

Offline

#2 2008-12-03 22:14:47

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

Have you checked the /etc/hosts.allow file?

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#3 2008-12-03 23:42:37

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

Re: [SOLVED]mini web server droopy problems

fukawi2 wrote:

Have you checked the /etc/hosts.allow file?

Well kind of,

/etc/hosts.allow

#
# /etc/hosts.allow
#

ALL: ALL

# End of file

/etc/hosts.deny

#
# /etc/hosts.deny
#

# ALL: ALL: DENY
ALL : ALL :DENY
# End of file

I tried some other configs but I couldn't find any clear info to config them. :S Do you know if those files are right ?
Thxs!

Offline

#4 2008-12-04 00:50:19

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

What IP are you trying to connect to? And what's the output of `ifconfig`?

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#5 2008-12-04 01:35:16

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

Re: [SOLVED]mini web server droopy problems

fukawi2 wrote:

What IP are you trying to connect to? And what's the output of `ifconfig`?

ifconfig

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1D:60:66:04:DC  
          inet addr:192.168.1.34  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:60ff:fe66:4dc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4721132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5894540 errors:0 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000 
          RX bytes:3263044000 (3111.8 Mb)  TX bytes:818129968 (780.2 Mb)

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:202487 errors:0 dropped:0 overruns:0 frame:0
          TX packets:202487 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:43456901 (41.4 Mb)  TX bytes:43456901 (41.4 Mb)

What I'm trying to do is send mi IP to someone(anyone) and he puts it on his browser with the ":8000" to get access to my droopy web server smile
Don't know if I'm explaining me quite well. Thxs!

Offline

#6 2008-12-04 05:43:54

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

dolmoboy wrote:

What I'm trying to do is send mi IP to someone(anyone) and he puts it on his browser with the ":8000" to get access to my droopy web server smile

Which IP address are you sending?  Sending the one from the output of ifconfig won't work...

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#7 2008-12-04 14:24:24

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

Re: [SOLVED]mini web server droopy problems

fukawi2 wrote:
dolmoboy wrote:

What I'm trying to do is send mi IP to someone(anyone) and he puts it on his browser with the ":8000" to get access to my droopy web server smile

Which IP address are you sending?  Sending the one from the output of ifconfig won't work...

I know, I send the IP from http://whatsmyip.org/, the real one.

Offline

#8 2008-12-04 21:48:58

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

Goodo smile

In that case, you have the proper port forward setup on your modem / router(s)?

EDIT: You're not using a proxy in Firefox / Opera / Epiphany / browser-of-your-choice are you?

Last edited by fukawi2 (2008-12-04 21:49:49)

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#9 2008-12-04 21:56:00

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

Re: [SOLVED]mini web server droopy problems

fukawi2 wrote:

Goodo smile

In that case, you have the proper port forward setup on your modem / router(s)?

EDIT: You're not using a proxy in Firefox / Opera / Epiphany / browser-of-your-choice are you?

I don't have any proxy at all.

And my router's config is ... 

Application      Trigger      Open      Remove
Name      Protocol      Port Range      Protocol      Port Range       
                       Start      End             Start      End       
Droopy      TCP/UDP      8000      8000      TCP      8000      8000

I think they are right :S, are they ? thxs smile

Last edited by dolmoboy (2008-12-04 22:13:20)

Offline

#10 2008-12-04 21:59:23

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

dolmoboy wrote:

And my router's config is ... 

Application      Trigger      Open      Remove
Name      Protocol      Port Range      Protocol      Port Range       
                       Start      End             Start      End       
Droopy      TCP/UDP      8000      8000      TCP      8000      8000

I think they are right :S, Am I ? thxs smile

Looks right - except it doesn't show what IP address it forwards to - did you omit that? It should be forwarding to 192.168.1.34

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#11 2008-12-04 22:20:05

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

Re: [SOLVED]mini web server droopy problems

fukawi2 wrote:
dolmoboy wrote:

And my router's config is ... 

Application      Trigger      Open      Remove
Name      Protocol      Port Range      Protocol      Port Range       
                       Start      End             Start      End       
Droopy      TCP/UDP      8000      8000      TCP      8000      8000

I think they are right :S, Am I ? thxs smile

Looks right - except it doesn't show what IP address it forwards to - did you omit that? It should be forwarding to 192.168.1.34

I didn't omit anything, in "port triggering" option doesn't show anything about IP's just ports :S
Here's description "

NAT -- Port Triggering Setup

Some applications require that specific ports in the Router's firewall be opened for access by the remote parties. Port Trigger dynamically opens up the 'Open Ports' in the firewall when an application on the LAN initiates a TCP/UDP connection to a remote party using the 'Triggering Ports'. The Router allows the remote party from the WAN side to establish new connections back to the application on the LAN side using the 'Open Ports'. A maximum 32 entries can be configured.

Nothing about IP's sad

I was wondering about using "DMZ Host" option, Is to risky for home use? Would it help? Thxs! smile

Offline

#12 2008-12-04 23:44:24

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

DMZ is a bit of overkill for 1 port, if your modem supports Port Triggering and DMZ, it should definately support Port Forwarding. What make / model is it?

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#13 2008-12-05 14:39:22

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

Re: [SOLVED]mini web server droopy problems

fukawi2 wrote:

DMZ is a bit of overkill for 1 port, if your modem supports Port Triggering and DMZ, it should definately support Port Forwarding. What make / model is it?

Well I didn't find any "Port Forwarding" option over "NAT" section, I have 3 options, Port Triggering, DMZ and Virtual Server. Here's Virtual Server description:

Virtual Server allows you to direct incoming traffic from WAN side (identified by Protocol and External port) to the Internal server with private IP address on the LAN side. The Internal port is required only if the external port needs to be converted to a different port number used by the server on the LAN side. A maximum 32 entries can be configured.

Server Name      External Port Start      External Port End      Protocol      Internal Port Start      Internal Port End      Server IP Address
Droopy                     8000                     8000           TCP/UDP                  8000                     8000             192.168.1.34

That's the config I have, but it still doesn't work. My router is Comtrend CT-5361 :S thxs for worrying so much smile

Offline

#14 2008-12-09 04:41:01

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

Sorry for the delay - I missed your reply somehow...

That sounds like what you want. Before your friend tries the connection, run this command as root and see if the packets are reaching your comptuer or still being blocked at the router:

tcpdump -lnn -i ethX port 8000

Replace ethX with your network interface

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#15 2008-12-09 14:57:29

dolmoboy
Member
Registered: 2008-12-03
Posts: 9

Re: [SOLVED]mini web server droopy problems

fukawi2 wrote:

Sorry for the delay - I missed your reply somehow...

That sounds like what you want. Before your friend tries the connection, run this command as root and see if the packets are reaching your comptuer or still being blocked at the router:

tcpdump -lnn -i ethX port 8000

Replace ethX with your network interface

Well, thanks for all your help, now it works big_smile
DROOPY

HTTP server running... Check it out at http://localhost:8000
171.Red-80-34-177.staticIP.rima-tde.net - - [09/Dec/2008 15:23:58] "GET / HTTP/1.1" 200 -
171.Red-80-34-177.staticIP.rima-tde.net - - [09/Dec/2008 15:23:59] "GET /favicon.ico HTTP/1.1" 200 -
171.Red-80-34-177.staticIP.rima-tde.net - - [09/Dec/2008 15:24:02] "GET /favicon.ico HTTP/1.1" 200 -
171.Red-80-34-177.staticIP.rima-tde.net - - [09/Dec/2008 15:24:18] Started file transfer
171.Red-80-34-177.staticIP.rima-tde.net - - [09/Dec/2008 15:24:25] Received: 1081187954.jpg
171.Red-80-34-177.staticIP.rima-tde.net - - [09/Dec/2008 15:24:25] "POST / HTTP/1.1" 200 -
176.Red-88-31-159.staticIP.rima-tde.net - - [09/Dec/2008 15:32:55] "GET / HTTP/1.1" 200 -
176.Red-88-31-159.staticIP.rima-tde.net - - [09/Dec/2008 15:32:56] "GET /favicon.ico HTTP/1.1" 200 -
176.Red-88-31-159.staticIP.rima-tde.net - - [09/Dec/2008 15:33:12] Started file transfer
176.Red-88-31-159.staticIP.rima-tde.net - - [09/Dec/2008 15:33:15] Received: 2.jpg
176.Red-88-31-159.staticIP.rima-tde.net - - [09/Dec/2008 15:33:15] "POST / HTTP/1.1" 200 -
localhost.localdomain - - [09/Dec/2008 15:34:14] "GET / HTTP/1.1" 200 -
localhost.localdomain - - [09/Dec/2008 15:34:14] "GET /favicon.ico HTTP/1.1" 200 -
localhost.localdomain - - [09/Dec/2008 15:34:17] "GET /favicon.ico HTTP/1.1" 200 -

TCPDUMP

15:24:21.964163 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.007270 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.007282 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 125785, win 63888, length 0
15:24:22.040987 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.041007 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 126977, win 63888, length 0
15:24:22.089435 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.132698 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.132709 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 129881, win 63888, length 0
15:24:22.166377 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.166413 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 131073, win 63888, length 0
15:24:22.208072 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.251457 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.251468 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 133977, win 63888, length 0
15:24:22.285200 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.285228 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 135169, win 63888, length 0
15:24:22.328076 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.370293 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.370304 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 138073, win 63888, length 0
15:24:22.404185 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.404218 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 139265, win 63888, length 0
15:24:22.446814 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.490253 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.490273 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 142169, win 63888, length 0
15:24:22.524143 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.524165 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 143361, win 63888, length 0
15:24:22.567056 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.608928 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.608946 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 146265, win 63888, length 0
15:24:22.642664 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.642686 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 147457, win 63888, length 0
15:24:22.685833 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.729198 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.729218 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 150361, win 63888, length 0
15:24:22.762656 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.762682 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 151553, win 63888, length 0
15:24:22.804564 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.846454 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.846468 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 154457, win 65535, length 0
15:24:22.881385 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:22.881394 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 155649, win 65535, length 0
15:24:22.924534 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.924554 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 157101, win 65535, length 0
15:24:22.966684 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:22.966699 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 158553, win 65535, length 0
15:24:23.000406 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.000418 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 159745, win 65535, length 0
15:24:23.043545 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.043563 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 161197, win 65535, length 0
15:24:23.085678 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.085696 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 162649, win 65535, length 0
15:24:23.120405 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.120420 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 163841, win 65535, length 0
15:24:23.162071 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.162083 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 165293, win 65535, length 0
15:24:23.205656 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.205665 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 166745, win 65535, length 0
15:24:23.239139 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.239160 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 167937, win 65535, length 0
15:24:23.280818 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.280834 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 169389, win 65535, length 0
15:24:23.324180 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.324197 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 170841, win 65535, length 0
15:24:23.359145 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.359158 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 172033, win 65535, length 0
15:24:23.401085 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.401101 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 173485, win 65535, length 0
15:24:23.442944 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.442958 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 174937, win 65535, length 0
15:24:23.478128 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.478144 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 176129, win 65535, length 0
15:24:23.519589 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.519604 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 177581, win 65535, length 0
15:24:23.562922 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.562936 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 179033, win 65535, length 0
15:24:23.598113 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.598127 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 180225, win 65535, length 0
15:24:23.640039 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.640052 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 181677, win 65535, length 0
15:24:23.681700 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.681717 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 183129, win 65535, length 0
15:24:23.717393 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.717406 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 184321, win 65535, length 0
15:24:23.758819 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.798737 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 185773, win 65535, length 0
15:24:23.801940 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.835381 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.835393 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 188417, win 65535, length 0
15:24:23.877798 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.920433 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:23.920452 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 191321, win 65535, length 0
15:24:23.954365 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:23.954395 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 192513, win 65535, length 0
15:24:23.997555 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.040674 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.040688 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 195417, win 65535, length 0
15:24:24.074374 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.074406 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 196609, win 65535, length 0
15:24:24.116333 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.159455 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.159472 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 199513, win 65535, length 0
15:24:24.193111 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.193142 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 200705, win 65535, length 0
15:24:24.236336 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.278178 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.278196 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 203609, win 65535, length 0
15:24:24.312327 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.312346 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 204801, win 65535, length 0
15:24:24.355043 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.398191 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.398205 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 207705, win 65535, length 0
15:24:24.432101 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.432136 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 208897, win 65535, length 0
15:24:24.475343 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.516943 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.516956 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 211801, win 65535, length 0
15:24:24.550654 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.550689 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 212993, win 65535, length 0
15:24:24.594037 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.636921 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.636936 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 215897, win 65535, length 0
15:24:24.670635 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.670657 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 217089, win 65535, length 0
15:24:24.712777 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.754462 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.754475 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 219993, win 65535, length 0
15:24:24.789401 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.789431 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 221185, win 65535, length 0
15:24:24.832757 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.874664 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.874677 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 224089, win 65535, length 0
15:24:24.909321 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:24.909339 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 225281, win 65535, length 0
15:24:24.951543 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.993659 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:24.993680 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 228185, win 65535, length 0
15:24:25.027858 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:25.027889 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 229377, win 65535, length 0
15:24:25.071753 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.113211 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.113226 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 232281, win 65535, length 0
15:24:25.146884 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:25.146918 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 233473, win 65535, length 0
15:24:25.189044 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.232162 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.232178 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 236377, win 65535, length 0
15:24:25.266849 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:25.266870 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 237569, win 65535, length 0
15:24:25.309292 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.351916 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.351939 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 240473, win 65535, length 0
15:24:25.385648 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:25.385672 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 241665, win 65535, length 0
15:24:25.427807 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.470704 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.470719 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 244569, win 65535, length 0
15:24:25.505616 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 1192
15:24:25.505638 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 245761, win 65535, length 0
15:24:25.548046 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1, win 65535, length 1452
15:24:25.565121 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [P.], ack 1, win 65535, length 572
15:24:25.565141 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 247785, win 65535, length 0
15:24:25.666727 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [P.], ack 247785, win 65535, length 17
15:24:25.718904 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 247785, win 65535, length 1452
15:24:25.718963 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [FP.], seq 1470:1708, ack 247785, win 65535, length 238
15:24:25.842683 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1470, win 65535, length 0
15:24:25.850266 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [.], ack 1709, win 65297, length 0
15:24:25.918268 IP 80.34.177.171.25400 > 192.168.1.34.8000: Flags [F.], seq 247785, ack 1709, win 65297, length 0
15:24:25.918285 IP 192.168.1.34.8000 > 80.34.177.171.25400: Flags [.], ack 247786, win 65144, length 0
15:32:55.063038 IP 88.31.159.176.1277 > 192.168.1.34.8000: Flags [S], seq 2202462381, win 16384, options [mss 1460,nop,nop,nop,nop], length 0
15:32:55.063070 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [S.], seq 4110674046, ack 2202462382, win 5840, options [mss 1460], length 0
15:32:55.224916 IP 88.31.159.176.1277 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 0
15:32:55.278649 IP 88.31.159.176.1277 > 192.168.1.34.8000: Flags [P.], ack 1, win 17424, length 250
15:32:55.278667 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [.], ack 251, win 6432, length 0
15:32:55.330788 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [P.], ack 251, win 6432, length 17
15:32:55.393661 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [.], ack 251, win 6432, length 1460
15:32:55.393766 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [FP.], seq 1478:2648, ack 251, win 6432, length 1170
15:32:55.619870 IP 88.31.159.176.1277 > 192.168.1.34.8000: Flags [.], ack 18, win 17407, length 0
15:32:55.619891 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [.], ack 251, win 6432, length 1452
15:32:55.619895 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [.], ack 251, win 6432, length 8
15:32:55.862089 IP 88.31.159.176.1277 > 192.168.1.34.8000: Flags [.], ack 2649, win 17424, length 0
15:32:55.862429 IP 88.31.159.176.1277 > 192.168.1.34.8000: Flags [F.], seq 251, ack 2649, win 17424, length 0
15:32:55.862465 IP 192.168.1.34.8000 > 88.31.159.176.1277: Flags [.], ack 252, win 6432, length 0
15:32:55.981411 IP 88.31.159.176.1278 > 192.168.1.34.8000: Flags [S], seq 3816028151, win 16384, options [mss 1460,nop,nop,nop,nop], length 0
15:32:55.981428 IP 192.168.1.34.8000 > 88.31.159.176.1278: Flags [S.], seq 4125056410, ack 3816028152, win 5840, options [mss 1460], length 0
15:32:56.124207 IP 88.31.159.176.1278 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 0
15:32:56.170789 IP 88.31.159.176.1278 > 192.168.1.34.8000: Flags [P.], ack 1, win 17424, length 240
15:32:56.170809 IP 192.168.1.34.8000 > 88.31.159.176.1278: Flags [.], ack 241, win 6432, length 0
15:32:56.277129 IP 192.168.1.34.8000 > 88.31.159.176.1278: Flags [P.], ack 241, win 6432, length 17
15:32:56.340969 IP 192.168.1.34.8000 > 88.31.159.176.1278: Flags [.], ack 241, win 6432, length 1452
15:32:56.341072 IP 192.168.1.34.8000 > 88.31.159.176.1278: Flags [FP.], seq 1470:2639, ack 241, win 6432, length 1169
15:32:56.560104 IP 88.31.159.176.1278 > 192.168.1.34.8000: Flags [.], ack 1470, win 17424, length 0
15:32:56.601411 IP 88.31.159.176.1278 > 192.168.1.34.8000: Flags [.], ack 2640, win 16255, length 0
15:32:56.641073 IP 88.31.159.176.1278 > 192.168.1.34.8000: Flags [F.], seq 241, ack 2640, win 16255, length 0
15:32:56.641086 IP 192.168.1.34.8000 > 88.31.159.176.1278: Flags [.], ack 242, win 6432, length 0
15:33:12.003663 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [S], seq 2777818442, win 16384, options [mss 1460,nop,nop,nop,nop], length 0
15:33:12.003687 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [S.], seq 71258946, ack 2777818443, win 5840, options [mss 1460], length 0
15:33:12.142702 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 0
15:33:12.225582 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [P.], ack 1, win 17424, length 584
15:33:12.225597 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 585, win 7008, length 0
15:33:12.408591 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:12.408601 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 2037, win 8712, length 0
15:33:12.608431 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:12.608440 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 3489, win 11616, length 0
15:33:12.805818 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:12.805842 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 4941, win 14520, length 0
15:33:12.989809 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:12.989831 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 6393, win 17424, length 0
15:33:13.188646 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:13.188664 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 7845, win 20328, length 0
15:33:13.381330 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:13.381350 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 9297, win 23232, length 0
15:33:13.568049 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:13.568064 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 10749, win 26136, length 0
15:33:13.765227 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:13.765250 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 12201, win 29040, length 0
15:33:13.964287 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:13.964308 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 13653, win 31944, length 0
15:33:14.144862 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.144875 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 15105, win 34848, length 0
15:33:14.344923 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.344936 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 16557, win 37752, length 0
15:33:14.557561 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.557577 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 18009, win 40656, length 0
15:33:14.559029 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.559047 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 19461, win 43560, length 0
15:33:14.637842 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.637862 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 20913, win 46464, length 0
15:33:14.639081 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.639092 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 22365, win 49368, length 0
15:33:14.640572 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.640584 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 23817, win 53724, length 0
15:33:14.658567 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.658583 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 25269, win 56628, length 0
15:33:14.707052 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.707068 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 26721, win 59532, length 0
15:33:14.868717 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.868730 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 28173, win 62436, length 0
15:33:14.877581 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.877601 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 29625, win 63888, length 0
15:33:14.879064 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.879074 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 31077, win 63888, length 0
15:33:14.950497 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.950518 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 32529, win 63888, length 0
15:33:14.951956 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.951967 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 33981, win 63888, length 0
15:33:14.953691 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1, win 17424, length 1452
15:33:14.953701 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 35433, win 63888, length 0
15:33:14.961290 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [P.], ack 1, win 17424, length 946
15:33:14.961310 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 36379, win 63888, length 0
15:33:15.075100 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [P.], ack 36379, win 63888, length 17
15:33:15.128546 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 36379, win 63888, length 1452
15:33:15.128687 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [FP.], seq 1470:1708, ack 36379, win 63888, length 238
15:33:15.348129 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1470, win 17424, length 0
15:33:15.348333 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [.], ack 1709, win 17186, length 0
15:33:15.368272 IP 88.31.159.176.1281 > 192.168.1.34.8000: Flags [F.], seq 36379, ack 1709, win 17186, length 0
15:33:15.368288 IP 192.168.1.34.8000 > 88.31.159.176.1281: Flags [.], ack 36380, win 63888, length 0
15:35:29.932080 IP 192.168.1.34.55072 > 58.69.137.44.8000: UDP, length 65
454 packets captured
454 packets received by filter
0 packets dropped by kernel

When you asked me about my port forward setup, I had configured nothing, so I configured at that moment but I forgot to reboot my router, so when i tested it didn't work so I desisted. Now when I was testing tcpdump my friends could enter droopy's web and they uploaded a few photos and all was working perfectly :S. It must be that don't you think?

Thanks Again! big_smile

Offline

#16 2008-12-09 21:28:28

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: [SOLVED]mini web server droopy problems

That would be it smile

Glad I could help - could you edit your original post to mark it as [SOLVED] please? smile

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

Pages: 1

Board footer

Powered by FluxBB