> > Yes. In my last example of the slow browing to an attached linksys, I was
> > using Firefox on XP. Previously I had thought it was all IE, but it's
> > not.
>
> Am I reading this correctly? Are you experiencing slow downs in
> connections to a Linksys's (device) management web page that is connected
> to the same network on the same subnet? Translated are you experiencing
> slow downs in connections to a equipment when the traffic is not passing
> through your router?
No. To get very specific:
Local net
eth0: 192.168.1.1 - net/mask 192.168.1.0/24
Configuration network (special type of network in my appliance)
eth1: 172.27.1.2 - net/mask 172.27.0.0/30
The configuration network Masq's:
/sbin/iptables -t nat -I POSTROUTING -o eth1 -d 172.27.0.2/255.255.255.252 \
-j SNAT --to-source 172.27.0.2
The SNAT to configration networks is to simplify life, as we don't have to
deal with playing with routes back to the local network in the external
devices, (wifi bridges, satellite terminals, etc)
And we normally browse to these devices via IP not hostname.
So to clarify my situtation:
Depending on what mood Windows is in, browering from a 192.168.1.0/24 host to
172.27.1.1 (linksys bridge in this case) or browsing to 192.168.1.1 (the
appliance itself, running Zope) will become ungodly slow. SOMETIMES it is
just fine.
I am also seeing zope deadlock, which I now believe is related to this
performance problem. When zope locks all other processes are fine, and the
box pings.
To expand further on the zope issue:
A few months ago I was remotly ssh'ed in to an appliance with my partner on
site. Zope had locked. I restarted the process. He connected a few times and
it locked again. I could not get a head reply back when it locked.
(telnet 127.0.0.1 < HEAD / HTTP/1.0)
We restarted it a dozen times with the same thing. It did not stop locking
until we rebooted the machine. All of this was via SSL.
It was at this point I figured it was SSL in zope. I turned off SSL access.
Seemed to help but now we're seeing locking, though maybe less frequently.
I was wondering if it was hardware, IRQ, etc. all but ruled that out. As I
mentioned, I just saw everything run perfectly with my laptop, then I plug
the XP machine in, and it dies.
If you can't tell this is really driving us crazy. I've got the simplest of
networks configs, barely any traffic, and it's running like shit with
direclty attached hosts.
Dave
