Login Modem Adsl Default

D-Link DSL504T

username admin

password admin

IP 192.168.1.1

Tecom AR1031

username admin

password admin

IP 192.168.1.1

netlink adsl router

username admin

password conexant

IP 10.0.0.2

Cron Job Script Calculator

This calculator requires the use of Javascript enabled and capable browsers. This is designed to assist you in generating the syntax for creating a CRON job on your UNIX, Linux or other 'NIX system. Most often, they are Internet servers. CRON is a UNIX/Linux function that will allow you to execute a command or job at a designated specific time automatically. CRON is somewhat like a system task scheduler on any operating system. All have task schedulers, some are simple to set up and use and others, like CRON are a little unfriendly. All times that are set for execution are based on the systems time clock. If used as an Internet server, that may be in a different time zone. You may want to see some of our time based calculators to assist you in determining the difference in time. You might also need to know that UNIX and other 'NIX systems use timestamping to mark and calculate time differences. Our To and From timestamping calculators may be of help to you. If you determine that you do NOT have the ability to run CRON on your 'NIX system and need to have the functionality of it, we have written a CRON emulator script called MUL8CRON that allows the same thing to happen without CRON. Contact us about it. Here are some examples of the CRON command line. Our defaults in the calculator are set so that any entered job will run every hour.

Delay pools are stupid

Delay pools are stupid; why can't I download something at full speed when the network is used only by me?

Unfortunately, you can't do much about it.

The only thing you can do is to use cron and reconfigure it, for example, at 1.00 am, so that Squid won't use delay pools, then reconfigure it again, let's say at 7.30 am, to use delay pools.

To do this, create two separate config files, called for example squid.conf-day and squid.conf-night, and put them into /opt/squid/etc/.

squid.conf-day would be the exact copy of a config we created earlier

Configuring Squid to use the delay pools feature

Configure our squid.conf file (located under /opt/squid/etc/squid.conf):

#squid.conf

#Every option in this file is very well documented in the original squid.conf file

#and on http://www.visolve.com/squidman/Configuration%20Guide.html

#

#The ports our Squid will listen on.

http_port 8080

icp_port 3130

#cgi-bins will not be cached.

acl QUERY urlpath_regex cgi-bin \?

no_cache deny QUERY

#Memory the Squid will use. Well, Squid will use far more than that.

cache_mem 16 MB

#250 means that Squid will use 250 megabytes of disk space.

cache_dir ufs /cache 250 16 256

Advanced squid issues, upkeep scripts, and disk management

Previously I wrote an article on setting up squid, and after that wrote a few things about the various disk storage methods squid makes available. I also touched upon how squid was not always reliable, and how I made some scripts to deal with that. I have since refined these scripts, and now enjoy very few squid related problems leading to downtime. In this article I share these scripts with you. For disk storage, I said that COSS was the clear winner, and though this is generally true, there are a few more things to keep in mind.

COSS is great if you need to cache a large number of small files that do not exceed a certain total size. There are a few reasons for this. First of all, COSS can only access a certain number of total objects per storage location. In order to have a large cache size, you need to increase the maximum allowed size of each object, and increase the size of your stripes. This necessarily increases ram usage. It also has a limit, so that beyond about 100gb (I forget the exact value), you cannot really have a COSS partition bigger than that.

New SSL Proxies

Because SSL websites are very hard to block, SSL Access to Vtunnel.com has always been popular, and now makes up about 50% of traffic to that site.

In case Vtunnel.com is blocked anyway, however, we now offer SSL access to several other web based proxies that we host:

https://www.btunnel.com

https://www.ctunnel.com

https://www.dtunnel.com

https://www.vtunnel.com

https://www.ztunnel.com

https://www.polysolve.com

https://www.beatfiltering.com

Enjoy!

Article Source http://www.freeproxies.org/blog/

Turkey Blocks Youtube.com, Freeproxies.org steps in to help

With the recent blockage of youtube.com, which has thus far last nearly two weeks, many of the residents and visitors of Turkey have been unable to access this very popular site. Thankfully, administrators at freeproxies.org were able to handle the massive influx of Turkish visitors looking to access youtube.com any way that they could.

In just one short week, access to youtube.com from Turkish visitors has more than doubled our total traffic and more than tripled our total bandwidth usage. Whereas youtube support typically peaks our usage at about 150 megabits per second, in recent days it has been using over 800 megabits per second. Luckily our servers and our service provider have been up to the task to ramp up our service very quickly. This, combined with spare capacity we had on hand to deal with such an event, have led to the site running more or less as expected, despite serving over 25 youtube videos per second during peak hours.