it's not a TTL problem.
a traceroute from a server in Belfast reaches the router in 6 hops, with
24 left before it dies.
I'll try a different router tomorrow if there are no further ideas.
On 11/09/2010 05:31 PM, Paul Murray wrote:
> On Tue, Nov 9, 2010 at 4:11 PM, Kae Verens<kae at verens.com> wrote:
>> has anyone managed it?
>>>> I've the following in "Advanced Setup> NAT> Virtual Servers" :
>> Server Name External Port Start External Port End Protocol
>> Internal Port Start Internal Port End Server IP Address
>> apache 80 80 TCP/UDP 80 80 192.168.1.111
>> apache 443 443 TCP/UDP 443 443 192.168.1.111
>>>>>> but, when I try access the server from outside my network, I don't get
>> anything returned at all.
>>>> the server is up and running (I'm typing on it), and other machines in the
>> LAN can access it at the above IP address.
>>>> when I remove the above entries, I get a simple html document which
>> redirects me to 192.168.1.254 (the router admin IP address). this definitely
>> shouldn't happen, as I have all WAN-side services disabled in "Management>
>> Access Control> Services" (except ICMP).
>>>> any ideas?
> See if you can increase the TTL on packets it generates, it about the
> only reason stuff works on a lan but not on a wan although your wan
> side admin function seems to be at odds with that being the issue.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!