Apache 1.3 Problems
smithi at nimnet.asn.au
Wed Sep 17 05:53:57 UTC 2008
On Tue, 16 Sep 2008, Annelise Anderson wrote:
> On Wed, 17 Sep 2008, Ian Smith wrote:
> > On Tue, 16 Sep 2008 17:48:48 +1000 (EST) mark at legios.org wrote:
> > > > On Tue, 16 Sep 2008 mark at legios.org wrote:
> > From a digest post, trimming a bit ..
Trimming lots this time ..
> > Ok, ping and DNS look fine. I (also) can traceroute your box this far:
> > 14 bbrb-isp.Stanford.EDU (126.96.36.199) 193.489 ms 193.562 ms 195.603
> > ms
> > 15 * * *
> > 16 * * *
> > 17 * * *
> > 18 * *^C
> > I don't know whether you allow inbound traceroutes? but the question
> > now is, how many routers between you and and bbrb-isp.Stanford.EDU ?
> > Can you show us a 'traceroute bbrb-isp.Stanford.EDU' from your machine?
> I think port 80 is being filtered. I have started talking to the admins.
> The traceroute looks like this--
> andrsn 2:23PM ~ % traceroute bbrb-isp.Stanford.EDU
> traceroute to bbrb-isp.Stanford.EDU (188.8.131.52), 64 hops max, 40 byte packets
> 1 goz-srtr-vlan910.Stanford.EDU (184.108.40.206) 0.610 ms 0.571 ms 0.711 ms
> 2 * bbra-rtr.Stanford.EDU (172.20.4.1) 1.093 ms *
> 3 * * *
> 4 * * *
> ....and so forth indefinitely.
While talking to the admins, you might show them your traceroute too.
It's a bit strange that bbrb-isp.Stanford.EDU responds to traceroutes
from the outside, but not from your internal machine. Of course it may
be that the port 80 blocking (and/or traceroute blocking) is occurring
on another router between you and bbrb-isp .. we can see at least two.
> When I filter out non-tcp traffic nothing shows up at all.
Obviously mail works both ways. tcptraceroute was also a good clue.
> I have not tried another port yet, but will do that now.
Happy hunting, Ian
More information about the freebsd-questions