I just mentioned that on the other list. (about the fact that those
preliminary steps should be sufficient to show routing is ok) One other
thing that may be in play here. Have you tried stopping the iptables
service and giving it a go. Perhaps it is blocking tcp between
localhost and the new gateway IP. ICMP can be controlled seperately
from IP.
Larry
On Sat, 2004-06-26 at 23:09, Steve Steiner wrote:
> > strace bash -c 'echo "GET /index.html
> > http/1.0
> > " > /dev/tcp/yahoo.com/80'
> >
> > to see where it's hanging up. It returned this:
> >
> > socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
> > connect(3, {sin_family=AF_INET, sin_port=htons(80),
> > sin_addr=inet_addr("66.218.71.198)}}, 16) <pause> = -1 ETIMEDOUT
> > (Connection timed out)
> > close(3) = 0
> >
> > several times (at least three), taking at least a minute to time out (I
> > didn't watch).
> >
> > Does that help?
> >
> > I compiled a different kernel (same source); but the same thing happened.
> >
> You say ping, trace, and name resolution all work. So what's not working?
> Just web browsing and news? Don't miss the forest for the trees. In cases
> like this, it's usually something much simpler than a low-level kernel
> error. If ping and traceroute work, then the routing is fine. Packets get
> out and find their way back. If name resolution works, then you are
> conencting to your ISP's DNS server (I assume you performed a ping by name
> to check this, i.e. ping www.yahoo.com).
>
> Soooo, if it's just news on that maching that's not working, then it must be
> something particular to the news client. Maybe resinstall the news client?
>
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:06:45 EDT