From: Fawad Halim <fawad@fawad.net>
To: linux-kernel@vger.kernel.org
Subject: Linksys connectivity problem using 2.6.0-test4
Date: Wed, 10 Sep 2003 06:46:52 -0500 [thread overview]
Message-ID: <3F5F0F2C.5080407@fawad.net> (raw)
Hi,
I'm having trouble connecting to the http based admin ports on my
LinkSys VPN router (BEFVP41) using the 2.6.0-test4 kernel on Redhat 9.
The connectivity works fine with 2.4.20-19.9 from Redhat as well as
other 2.4.x kernels. With the 2.6 kernel, I can ping the machine, but
can't connect to the http ports (80, 8080)
# uname -a
Linux chuckie 2.6.0-test4-fh1 #1 Mon Sep 1 05:43:07 CDT 2003 i686 athlon
i386 GNU/Linux
# nmap 192.168.3.1
Starting nmap 3.30 ( http://www.insecure.org/nmap/ ) at 2003-09-10 06:42 CDT
Interesting ports on 192.168.3.1:
(The 1642 ports scanned but not shown below are in state: closed)
Port State Service
80/tcp open http
8080/tcp open http-proxy
Nmap run completed -- 1 IP address (1 host up) scanned in 2.468 seconds
# ping -c 1 192.168.3.1
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.
64 bytes from 192.168.3.1: icmp_seq=1 ttl=149 time=1.44 ms
--- 192.168.3.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.448/1.448/1.448/0.000 ms
# telnet 192.168.3.1 80
Trying 192.168.3.1...
telnet: connect to address 192.168.3.1: Connection refused
The VPN router is doing NAT correctly for both kernels, and connectivity
to services other than the router itself is fine.
I am not sure where to even begin debugging this problem.
Regards
-fawad
next reply other threads:[~2003-09-10 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 11:46 Fawad Halim [this message]
2003-09-10 18:11 ` Linksys connectivity problem using 2.6.0-test4 Dmitry Torokhov
2003-09-10 17:54 ` Fawad Halim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F5F0F2C.5080407@fawad.net \
--to=fawad@fawad.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox