Login

satimis · 2006-12-01, 03:19 AM

Hi folks,

Ubuntu-6.06.1-LAMP-server-amd64

Apache2

Domain: satimis.homelinux.com

(registered with dynsdn.com)

Apache is running on this server which is for test purpose.

On browser

[/url]http://satimis.homelinux.com

https://satimis.homelinux.com

satimis.homelinux.com

http://satimis.homelinux.com:443

https://satimis.homelinux.com:443

satimis.homelinux.com:443

http://satimis.homelinux.com:8080

https://satimis.homelinux.com:8080

satimis.homelinux.com:8080

all of them failed to visit the homepage on /var/www/. They only hung there until time out.

Both ports 443 and 8080 are open and not stealth. I have them checked on;

[url=http://www.grc.com/]http://www.grc.com/

SheildsUp

# cat /etc/hosts

Code:
127.0.0.1	   localhost.localdomain   localhost
192.168.0.100   sever1.example.com   server1
ubuntu

# The following lines are desirable for IPv6 capable hosts
::1	 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

However

//localhost

//localhost:443

//localhost:8080

all displayed the homepage.

There is no hardware firewall between server and Internet. The server is connected with a CAT5 cable to an ADSL modem. Another end of the ADSL modem is connected to telephone wall socket with a telephone line. The ADSL modem is supplied by ISP and does not require setup.

Please help. TIA

B.R.

satimis

***anyweb*** · 2006-12-01, 07:47 AM

are you absolutely SURE that iptables/firewall is not blocking those ports ?

and is apache really listening on those ports ?

netstat -an |grep tcp

should show you what is listening

satimis · 2006-12-01, 09:53 AM

Hi anyweb,

Quote:are you absolutely SURE that iptables/firewall is not blocking those ports ?

Whether you meant 80, 443 and 8080?

Quote:and is apache really listening on those ports ?

netstat -an |grep tcp

should show you what is listening

$ netstat -an | grep tcp

Code:
tcp		0	  0 0.0.0.0:2049			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:932			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:45350		 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:3306		  0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:747			 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:56877		   0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:111		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:6000			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:753			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:46292		 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:21			  0.0.0.0:*			   LISTEN
tcp		0	  0 58.152.169.2:53		 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:53			0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:631		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:8888			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:25			  0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:953		   0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:45350		 127.0.0.1:43988		 ESTABLISHED
tcp		0	  0 127.0.0.1:43988		 127.0.0.1:45350		 ESTABLISHED
tcp		0	  0 58.152.169.2:52172	  72.14.253.147:80		ESTABLISHED
tcp		0	  0 58.152.169.2:54508	  72.14.255.147:80		ESTABLISHED
tcp6	   0	  0 :::993				  :::*					LISTEN
tcp6	   0	  0 :::995				  :::*					LISTEN
tcp6	   0	  0 :::2222				 :::*					LISTEN
tcp6	   0	  0 :::110				  :::*					LISTEN
tcp6	   0	  0 :::143				  :::*					LISTEN
tcp6	   0	  0 :::6000				 :::*					LISTEN
tcp6	   0	  0 :::80				   :::*					LISTEN
tcp6	   0	  0 :::8080				 :::*					LISTEN
tcp6	   0	  0 :::25				   :::*					LISTEN
tcp6	   0	  0 ::1:953				 :::*					LISTEN
tcp6	   0	  0 :::443				  :::*					LISTEN

ports 80, 443, 8080 are listened by tcp6.

Tks.

B.R.

satimis

***anyweb*** · 2006-12-01, 11:10 AM

yep, meaning that it's listening for ipv6 connections and not 'normal' internet traffic

i dont know how you've configured it to do that but it's certaintly not listening on regular port 80

checkout my webserver listen properties

Quote:tcp 0 0 192.168.0.128:80 0.0.0.0:* LISTEN

so, are you using ipv6 at all ? if not re-configure your network settings and/or httpd.conf to listen on your IP and not your IPV6

cheers

anyweb

satimis · 2006-12-01, 02:23 PM

Hi anyweb,

Quote:yep, meaning that it's listening for ipv6 connections and not 'normal' internet traffic

i dont know how you've configured it to do that but it's certaintly not listening on regular port 80

I haven't configured the network after installing Ubuntu-6.06.1-LAMP-server-amd6.

I followed;

[/url][url=http://www.howtoforge.com/perfect_setup_ubuntu_6.06]http://www.howtoforge.com/perfect_setup_ubuntu_6.06

to build this server for test and absorbing knowhow as well. Neither I configured listening ipv6. I even don't fully understand its application.

Quote:so, are you using ipv6 at all ? if not re-configure your network settings and/or httpd.conf to listen on your IP and not your IPV6

Please advise which file shall I edit;

$ cat /etc/hosts

Code:
127.0.0.1	   localhost.localdomain   localhost
192.168.0.100   sever1.example.com   server1
ubuntu

# The following lines are desirable for IPv6 capable hosts
::1	 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

$ cat /etc/network/interfaces

Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
 address 127.0.0.1
 netmask 255.0.0.0

auth eth0
iface eth0 inet dhcp

auto dsl-provider
iface dsl-provider inet ppp
provider dsl-provider

# added by pppoeconf
auto eth0
#pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf

$ cat /etc/apache2/httpd.conf

Code:
# This is here for backwards compatability reasons and to support
#  installing 3rd party modules directly via apxs2, rather than
#  through the /etc/apache2/mods-{available,enabled} mechanism.
#
#LoadModule mod_placeholder /usr/lib/apache2/modules/mod_placeholder.so

ServerName "localhost"

# httpd.conf listen directive, change "80" to some other value
#Listen 80

No entry on this file.

and how to make such a change. TIA

B.R.

satimis

***anyweb*** · 2006-12-01, 02:42 PM

try this

[/url][url=http://www.ubuntuforums.org/archive/index.php/t-87798.html]http://www.ubuntuforums.org/archive/index.php/t-87798.html

and then restart, and do a new netstat -an |grep tcp

is apache listening on tcp port 80 then ?

satimis · 2006-12-02, 02:54 PM

Hi anyweb,

Tks for your URL

Performed following test;

on /etc/modprobe.d/aliases

added follows;

alias net-pf-10 ipv6 off

alias net-pf-10 off

alias ipv6 off

#alias net-pf-10 ipv6

Code:
# network protocols ##########################################################
alias net-pf-1  unix
alias net-pf-2  ipv4
alias net-pf-3  ax25
alias net-pf-4  ipx
alias net-pf-5  appletalk
alias net-pf-6  netrom
alias net-pf-7  bridge
alias net-pf-8  atm
alias net-pf-9  x25
alias net-pf-10 ipv6 off
alias net-pf-10 off
alias ipv6 off
#alias net-pf-10 ipv6
alias net-pf-11 rose
alias net-pf-12 decnet
# 13 NETBEUI
alias net-pf-15 af_key
alias net-pf-16 af_netlink
alias net-pf-17 af_packet
# 18 ASH
alias net-pf-19 af_econet
alias net-pf-20 atm
# 22 SNA
alias net-pf-23 irda
alias net-pf-24 pppoe
alias net-pf-25 wanrouter
alias net-pf-26 llc
alias net-pf-31 bluetooth
....

Rebooted PC

On browser;

satimis.homelinux.com (still failed displaying webpage)

219.79.147.166 (displayed webpage. IP address on connection)

$ sudo ping -c 3 satimis.homelinux.com

Code:
Password:
PING satimis.homelinux.com (58.152.181.13) 56(84) bytes of data.

--- satimis.homelinux.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2002ms

$ sudo netstat -an |grep tcp

Code:
tcp		0	  0 0.0.0.0:2049			0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:3306		  0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:43211		 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:716			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:111		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:6000			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:913			 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:722			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:36242		 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:21			  0.0.0.0:*			   LISTEN
tcp		0	  0 219.79.147.166:53	   0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:53			0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:631		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:8888			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:25			  0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:953		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:57499		   0.0.0.0:*			   LISTEN
tcp		0	  0 219.79.147.166:42524	72.14.255.104:80		ESTABLISHED
tcp		0	  0 219.79.147.166:42608	72.14.255.104:80		ESTABLISHED
tcp		0	  0 127.0.0.1:54789		 127.0.0.1:36242		 ESTABLISHED
tcp		0	  0 127.0.0.1:36242		 127.0.0.1:54789		 ESTABLISHED
tcp6	   0	  0 :::993				  :::*					LISTEN
tcp6	   0	  0 :::995				  :::*					LISTEN
tcp6	   0	  0 :::2222				 :::*					LISTEN
tcp6	   0	  0 :::110				  :::*					LISTEN
tcp6	   0	  0 :::143				  :::*					LISTEN
tcp6	   0	  0 :::6000				 :::*					LISTEN
tcp6	   0	  0 :::80				   :::*					LISTEN
tcp6	   0	  0 :::8080				 :::*					LISTEN
tcp6	   0	  0 :::25				   :::*					LISTEN
tcp6	   0	  0 ::1:953				 :::*					LISTEN
tcp6	   0	  0 :::443				  :::*					LISTEN

Tks.

B.R.

satimis

znx · (This post was last modified: 2006-12-02, 07:19 PM by znx.)

This is a firewall issue, attempting to scan that system shows:

Code:
Host n058152181013.netvigator.com (58.152.181.13) appears to be up ... good.
Interesting ports on n058152181013.netvigator.com (58.152.181.13):
PORT	 STATE	SERVICE
80/tcp   filtered http
443/tcp  filtered https
8080/tcp filtered http-proxy

Obviously there is no IPv6 address, so I can't scan those ports, so all ports are filtered.

Look into your firewall setup.

satimis · (This post was last modified: 2006-12-02, 11:03 PM by satimis.)

znx,

Quote:Obviously there is no IPv6 address, so I can't scan those ports, so all ports are filtered.

Look into your firewall setup.

$ sudo iptables -L

Code:
Password:
Chain INPUT (policy ACCEPT)
target	 prot opt source			   destination

Chain FORWARD (policy ACCEPT)
target	 prot opt source			   destination
TCPMSS	 tcp  --  anywhere			 anywhere			tcp flags:SYN,RST/S YN tcpmss match 1400:1536 TCPMSS clamp to PMTU

Chain OUTPUT (policy ACCEPT)
target	 prot opt source			   destination

$ sudo iptables -L -n -v

Code:
Chain INPUT (policy ACCEPT 10142 packets, 9083K bytes)
pkts bytes target	 prot opt in	 out	 source			   destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination
0	 0 TCPMSS	 tcp  --  *	  ppp0	0.0.0.0/0			0.0.0.0/0		   tcp flags:0x06/0x02 tcpmss match 1400:1536 TCPMSS clamp to PMTU

Chain OUTPUT (policy ACCEPT 9482 packets, 1410K bytes)
pkts bytes target	 prot opt in	 out	 source			   destination

It is quite strange to me. I can ping 219.79.144.63 which is the IP address on connection. But failed to ping "satimis.homelinux.com"

On browser 219.79.144.63 can browse the webpage and "satimis.homelinux.com" failed.

I login DYNDNS.COM and found the IP there has been updated 219.79.144.63. It seems DYNDNS.COM has not redirected satimis.homelinux.com to 219.79.144.63

My server is off if I'm not working on it.

B.R.

satimis

***anyweb*** · 2006-12-02, 11:05 PM

Quote:On browser;satimis.homelinux.com (still failed displaying webpage)

219.79.147.166 (displayed webpage. IP address on connection)

$ sudo ping -c 3 satimis.homelinux.com

CODE

Password:

PING satimis.homelinux.com (58.152.181.13) 56(84) bytes of data.

--- satimis.homelinux.com ping statistics ---

3 packets transmitted, 0 received, 100% packet loss, time 2002ms

something about that ^ doesnt look right

which ip should you be, the 58 one or the 219 one ?

sort that out first then see if you can fix this issue

cheers

anyweb

Login
Username/Email:
Password:	Lost Password?
	Remember me