From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] firewall or ...?
Date: Wed, 23 Jan 2013 16:30:00 +0100 [thread overview]
Message-ID: <20130123163000.52ebc529@skate> (raw)
In-Reply-To: <2DD0B9C711CDFC45A3A266C78966CE7F40E42155@G4W3291.americas.hpqcorp.net>
Dear Jenkins, Lee (ISS Houston),
On Wed, 23 Jan 2013 15:22:56 +0000, Jenkins, Lee (ISS Houston) wrote:
> It looks open to me. Can anyone suggest why the web server is only
> serving requests from localhost?
It might be configured explicitly to listen only on localhost, or it
might bind itself only on the interfaces that are up at the moment the
web server is started.
Do you get a "Connection refused", or does your HTTP client times out?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-23 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 15:22 [Buildroot] firewall or ...? Jenkins, Lee
2013-01-23 15:30 ` Thomas Petazzoni [this message]
2013-01-23 15:40 ` Jenkins, Lee
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=20130123163000.52ebc529@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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