Page 1 of 1
New proxy
Posted: Wed Mar 19, 2008 9:24 am
by InoX
The new proxy is not working well, not on v.2.9.51 and v.3.4. Http is very slow most of the time, if I try to stop it, look at the picture(is still running), cache is 0 after upgrade.
Re: New proxy is a crap
Posted: Wed Mar 19, 2008 9:41 am
by janisk
in screen shot you can clearly see that proxy is not enabled.
Re: New proxy is a crap
Posted: Wed Mar 19, 2008 9:55 am
by InoX
If you can read, i say I can't stop it!!! And when is running cache is 0 anyway. No problems in 2.9.51 with old proxy.
Re: New proxy is a crap
Posted: Wed Mar 19, 2008 10:01 am
by janisk
so if you un-check "enable" and then push apply it is still running?
Re: New proxy
Posted: Wed Mar 19, 2008 11:00 am
by InoX
Yes. In both v.2.9 and 3.4. and http was very, very slow.
Re: New proxy
Posted: Wed Mar 19, 2008 11:03 am
by Znuff
We've already been trough this with support.
The Mikrotik webproxy is slow. Very slow compared to squid.
Even upgraded to 3.4 today and it was STILL slow. Under 2.9.x, the webproxy-test was slow _AND_ buggy.
No issues with the old webproxy. Any chance to have that back in 3.x?
Re: New proxy
Posted: Wed Mar 19, 2008 1:17 pm
by WirelessRudy
I have the same settings as Inox (screenshot) but enabled. But my proxy just does not want to work.
All nat and redirect rules in place.
When I disable the proxy all http traffic stops. So this must be a sign the proxy works?
But no cache hits, and data from server is the same as date send to client. But cache hits and hits sends all stay ¨0¨ even after a day with more then 60 users on line.
If I fill in ¨unlimited¨ in Max. Cache Size while ¨cache On Disk¨ ticked on, it stays unlimited (the manual says it should come back with a value)
When I untick the ¨cache On Disk¨ there is a value calculated. But still no hits.
So it looks like the proxy works, but not the cache routine.
rgds
Rudy
Re: New proxy
Posted: Wed Mar 19, 2008 1:58 pm
by janisk
ok, just install 3.5 when it comes out today.
Re: New proxy
Posted: Wed Mar 19, 2008 3:44 pm
by WirelessRudy
Janisk,
Am running 3.5 now.
Proxy started to work now. But not very good.
Initial http pages come in very slowly, the idle
http://www.google.com took 10 secs to load, after that the page came from the cache in a split second. (I cleared history and cache etc. in the browser and rebooted the browser)
but one of my clients told me he could not even browse anymore. He used the same pages to try as i did.
I disabled the proxy and the redirect rule and he can browse again, like I can myself.
He is a wireless client in a routed network while I am just on the LAN side for the main router that has the proxy running.
I have all rules in ´web proxy´ ¨Access¨ and ¨Cache¨ disabled.
Also, the ¨Max. cache Size¨ still keeps saying ´unlimited´ in contrary of what the manual would make me expect (a value).
So, 3.5 improved things for proxy here, but still not good.
rgds.
Re: New proxy
Posted: Thu Mar 20, 2008 10:31 am
by Znuff
Re: New proxy
Posted: Thu Mar 20, 2008 11:16 am
by WirelessRudy
So,
Your proxy stopped working now in 3.5 when it is disabled. Good for you.
But how does it work when it is enabled?
Does it work fine? Or with flaws?
Like said, mine doesn't work very good. Initial pages (not in the cache yet) come to the browsing PC veeerrrryyyy slow. After that it is fast.
Some clients can´t even browse anymore. I think the initial page come in so slow they get a timeout.
Very disappointing. I hoped proxy would improve my clients browsing but I am back to direct again. At least that works and much faster then with the proxy. (At least for new pages.)
Rudy
Re: New proxy
Posted: Thu Mar 20, 2008 12:23 pm
by janisk
i am using routeros proxy myself and i do not experience any slowdowns.\
what pages are slow to open first time, i triet msn.com, yahoo.com, apple.com, hp.com and all of those opened really fast
Re: New proxy
Posted: Thu Mar 20, 2008 12:28 pm
by Znuff
Can we have old squid back in 3.x?
Thanks.
Re: New proxy
Posted: Thu Mar 20, 2008 1:31 pm
by WirelessRudy
i am using routeros proxy myself and i do not experience any slowdowns.\
what pages are slow to open first time, i triet msn.com, yahoo.com, apple.com, hp.com and all of those opened really fast
Janisk:
Proxy enabled: 1st page request 2nd request proxy disabled
msn.com 25s 25s 3s
yahoo.com 8s 19s 3s
apple.com 45s 17s 7s
hp.com 8s 8s 3s
google.com 1s 2s 1s
cnn.com 12s 17s 8s
In between everytime the browser cache and history cleaned and the browser rebooted.
Same test done with two of my clients and they have the same sort of results. One can hardly browse if the proxy is enabled while everything runs fine when it is disabled.
Made these clienst also clear the cache and history everytime.
I have more sites, special the ones with loads of links in them that are really slowed down a lot by the proxy.
Something must be wrong...
Re: New proxy
Posted: Thu Mar 20, 2008 2:24 pm
by Dragonmen
Why not using the separate machine for proxy and reduce the load on router?
Surely the separate machine with squid can run faster than the ROS's integrated proxy and you'll have many, many more features.
Do not use 3.0 branch (yet) as it is slower than 2.X and more buggy.
Re: New proxy
Posted: Thu Mar 20, 2008 3:26 pm
by savage
Said it before, will say it again...
A router is a router, a proxy is a proxy
They are fundamentally different. MT does not support the required hardware to make a good proxy to serve a high number of users, nor does the configurations cater for it. If you want a proxy, install one on a dedicated box...
Re: New proxy
Posted: Fri Mar 21, 2008 2:45 am
by Chupaka
savage, do not mix proxy and cache. I do not use cache in proxy, but I need proxy to log users' web surfing
yesterday I write support twice, but no reply. did Ticket system crashed?.. so, my problem is:
I've just upgraded my ros to 3.5. When trying to go to Internet via web-proxy, it uses my private address (192.168.xxx.xxx) for outgoing connections. When I set my public address (xxx.xxx.xxx.xxx) as proxy Src-Address, I cannot even connect to proxy - telnet to port 80 to any internet site says "Connection refused". Now I found the only workaround: add Src-NAT rule with src-address=192.168.xxx.xxx and out-interface=uplink, action=masquerade. It's working now, but... Please fix that =)
supout.rif were attached. normis, janisk?..