https://wiki.archlinux.org/api.php?action=feedcontributions&user=Nakkiel&feedformat=atomArchWiki - User contributions [en]2024-03-28T08:15:01ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Mirrors&diff=15397Mirrors2006-09-21T00:32:45Z<p>Nakkiel: Added two french mirrors</p>
<hr />
<div>== Enabling your favorite mirror ==<br />
<br />
The default pacman configuration for ''current'' looks like this:<br />
<br />
[current]<br />
Include = /etc/pacman.d/current<br />
<br />
If you want to use the HostEurope mirror as your default mirror, just add it before the <tt>Include</tt> line:<br />
<br />
[current]<br />
Server = <nowiki>ftp://ftp.hosteurope.de/mirror/ftp.archlinux.org/current/os/i686</nowiki><br />
Include = /etc/pacman.d/current<br />
<br />
Pacman will now try to connect to this mirror first. You can do the same for ''testing'', ''extra'', ''community'' and ''unstable''.<br />
<br />
'''Use the same mirror for all repositories. Otherwise packages may get installed that are incompatible to each other (like kernel26 from ''current'' and another (older) kernel module from ''extra'').'''<br />
<br />
== Mirror List ==<br />
<br />
This is a list of all known ArchLinux mirrors, that's more up to date than the [http://www.archlinux.org/download/ official download page] or the [http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/base/pacman/ files in <tt>/etc/pacman.d/</tt>]. If you know a not listed mirror, please add it. Mirrors which are not updated or unavailable for a long time can be deleted.<br />
<br />
Many sites also provide http service, but keep in mind that pacman relies on ftp to determine if a repository got updated. With http it fetches the repository database each time you run <tt>pacman -Sy</tt>, even if it didn't change since the last run.<br />
<br />
=== Global ===<br />
*http://prdownloads.sourceforge.net/archlinux/ (ISO only, no 0.7.2 yet)<br />
<br />
=== Australia ===<br />
*ftp://mirror.pacific.net.au/linux/archlinux/ <sub>[http://mirror.pacific.net.au/linux/archlinux/ http]</sub><br />
<br />
=== Austria ===<br />
*ftp://gd.tuwien.ac.at/opsys/linux/archlinux/ <sub>[http://gd.tuwien.ac.at/opsys/linux/archlinux/ http]</sub><br />
<br />
=== Belgium ===<br />
*ftp://ftp.belnet.be/packages/archlinux/ <sub>[http://ftp.belnet.be/packages/archlinux/ http]</sub><br />
<br />
=== China ===<br />
*http://mirror.vmmatrix.net/ArchLinux/<br />
*http://dxmirror.vmmatrix.net/ArchLinux/<br />
*http://cncmirror.vmmatrix.net/ArchLinux/<br />
<br />
=== Czech Republic ===<br />
*ftp://ftp.sh.cvut.cz/MIRRORS/arch/ <sub>[http://ftp.sh.cvut.cz/MIRRORS/arch/ http]</sub><br />
<br />
=== Estonia ===<br />
*ftp://ftp.estpak.ee/pub/archlinux/ <sub>[http://ftp.estpak.ee/pub/archlinux/ http]</sub><br />
<br />
=== France ===<br />
*ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/archlinux/ <sub>[http://distrib-coffee.ipsl.jussieu.fr/pub/linux/archlinux/ http]</sub> <sub>[rsync://distrib-coffee.ipsl.jussieu.fr/pub/linux/archlinux/ rsync]</sub><br />
* ftp://mir1.archlinuxfr.org/archlinux <sub>[http://mir1.archlinuxfr.org/archlinux http]</sub> <sub>[rsync://mir1.archlinuxfr.org/archlinux rsync]</sub><br />
* ftp://mir2.archlinuxfr.org/archlinux <sub>[http://mir2.archlinuxfr.org/archlinux http]</sub> <sub>[rsync://mir2.archlinuxfr.org/archlinux rsync]</sub><br />
<br />
=== Germany ===<br />
*ftp://ftp.hosteurope.de/mirror/ftp.archlinux.org/ <sub>[http://ftp.hosteurope.de/mirror/ftp.archlinux.org/ http]</sub><br />
*ftp://ftp.tu-chemnitz.de/pub/linux/sunsite.unc-mirror/distributions/archlinux/ <sub>[http://ftp.tu-chemnitz.de/pub/linux/sunsite.unc-mirror/distributions/archlinux/ http]</sub><br />
<br />
=== Great Britain ===<br />
*http://ftp.parrswood.manchester.sch.uk/Mirrors/ftp.archlinux.org/<br />
<br />
=== Greece ===<br />
*ftp://ftp.ntua.gr/pub/linux/archlinux/ <sub>[http://ftp.ntua.gr/pub/linux/archlinux/ http]</sub><br />
<br />
=== Ireland ===<br />
*ftp://ftp.heanet.ie/mirrors/ftp.archlinux.org/ <sub>[http://ftp.heanet.ie/mirrors/ftp.archlinux.org/ http]</sub><br />
<br />
=== Italy ===<br />
*ftp://mi.mirror.garr.it/mirrors/archlinux/ <sub>[http://mi.mirror.garr.it/mirrors/archlinux/ http]</sub><br />
<br />
=== Lithuania ===<br />
*ftp://saule.mintis.lt/pub/linux/ <sub>[http://saule.mintis.lt/pub/linux/ http]</sub> (without ISO and ''community'')<br />
<br />
=== Malaysia ===<br />
*http://mymirror.asiaosc.org/archlinux-distro/ (without ISO, ''community'', ''testing'', ''unstable'')<br />
<br />
=== Netherlands ===<br />
*ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/ <sub>[http://ftp.nluug.nl/pub/metalab/distributions/archlinux/ http]</sub> (1 week out of date)<br />
*ftp://ftp.surfnet.nl/pub/os/Linux/distr/archlinux/ <sub>[http://ftp.surfnet.nl/pub/os/Linux/distr/archlinux/ http]</sub> (same)<br />
=== Norway ===<br />
*http://mirror.djzradio.net/ (no ISOs)<br />
<br />
=== Poland ===<br />
*ftp://sunsite.icm.edu.pl/site/linux-sunsite/distributions/archlinux/ (no ''testing'', one week late)<br />
*ftp://mirror.icis.pcz.pl/archlinux/<br />
<br />
=== Portugal ===<br />
*ftp://gul.est.ips.pt/repos/archlinux/ <sub>[http://gul.est.ips.pt/ftp/repos/archlinux/ http]</sub><br />
*ftp://cesium.di.uminho.pt/pub/archlinux/ <sub>[http://cesium.di.uminho.pt/pub/archlinux/ http]</sub><br />
*ftp://darkstar.ist.utl.pt/pub/archlinux/ <sub>[http://darkstar.ist.utl.pt/archlinux/ http]</sub><br />
<br />
=== Romania ===<br />
*ftp://ftp.iasi.roedu.net/mirrors/archlinux.org/ <sub>[http://ftp.iasi.roedu.net/mirrors/archlinux.org/ http]</sub><br />
<br />
=== Sweden ===<br />
*ftp://ftp.ds.hj.se/pub/os/linux/archlinux/ <sub>[http://ftp.ds.hj.se/pub/os/linux/archlinux/ http]</sub><br />
*ftp://ftp.gigabit.nu/ <sub>[http://ftp.gigabit.nu/archlinux/ http]</sub><br />
<br />
=== Switzerland ===<br />
*ftp://archlinux.puzzle.ch/ <sub>[http://archlinux.puzzle.ch/ http]</sub><br />
<br />
=== Taiwan ===<br />
*ftp://cle.linux.org.tw/pub/ArchLinux/ (no ''community'', ''testing'', ''unstable'')<br />
<br />
=== United States ===<br />
*ftp://ftp-linux.cc.gatech.edu/pub/linux/distributions/archlinux/ <sub>[http://ftp-linux.cc.gatech.edu/pub/linux/distributions/archlinux/ http]</sub><br />
*ftp://mirror.cs.vt.edu/pub/ArchLinux/ <sub>[http://mirror.cs.vt.edu/pub/ArchLinux/ http]</sub><br />
*ftp://arch.os-zen.net/mirror/ <sub>[http://arch.os-zen.net/mirror/ http]</sub><br />
*ftp://ibiblio.org/pub/linux/distributions/archlinux/ <sub>[http://distro.ibiblio.org/pub/linux/distributions/archlinux/ http]</sub></div>Nakkielhttps://wiki.archlinux.org/index.php?title=Network_configuration&diff=15276Network configuration2006-09-13T01:38:28Z<p>Nakkiel: The TCP Window Scaling issue - first submission</p>
<hr />
<div>[[Category:Network]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Configuring_network}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Статический IP и DHCP}}<br />
{{i18n_links_end}}<br />
<br />
== Summary ==<br />
<br />
A simple guide to get your network running.<br />
<br />
<br />
== Load the device module ==<br />
<br />
If you use [[hwdetect]] or [[Replacing Hotplug with LSHWD|lshwd]], they should detect your network card (NIC) module and load it automatically at startup. Otherwise, you will need to know which module is needed for your particular model.<br />
<br />
Search the Web for your card model, or try using a Linux LiveCD to find out the name of the needed module - run [[Linux And Hardware|lsmod]] to show you all currently loaded modules after booting.<br />
<br />
Now when you know which module to use you can load it:<br />
<br />
# modprobe <modulename><br />
<br />
If you don't want / can't use some auto-loader like [[hwdetect]] you can add it into the modules array in <code>/etc/rc.conf</code>, so you don't need to modprobe it everytime you boot. For example, if tg3 is the network module:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
Other common modules are 8139too for cards with the RealTek chipset or sis900 for SiS cards.<br />
<br />
<br />
== Configure IP ==<br />
<br />
=== For DHCP IP ===<br />
<br />
Edit <code>/etc/rc.conf</code> like this:<br />
<br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
INTERFACES=(lo eth0)<br />
ROUTES=(!gateway)<br />
</pre><br />
<br />
=== For Static IP ===<br />
<br />
If you share your internet connection from a Windows box without a router, be sure to use static IPs on both computers. Otherwise you will have LAN issues.<br />
<br />
You need:<br />
<br />
* Your static IP address,<br />
* The netmask,<br />
* The broadcast address,<br />
* Your gateway,<br />
* Your nameservers' IP addresses,<br />
* Your domain name.<br />
<br />
If you are running a private network, it is safe to use IP addresses in 192.168.*.'* for your IPs, with a netmask of 255.255.0.0 and broadcast address of 192.168.255.255. Unless your network has a router, the gateway address does not matter. Edit <code>/etc/rc.conf</code> like this, substituting your own values for the IP, netmask, broadcast, and gateway:<br />
<br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(lo eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
</pre><br />
<br />
and your <code>/etc/resolv.conf</code> like this, substituting your nameservers' IPs and your domain name:<br />
<br />
<pre><br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
</pre><br />
<br />
You may include as many nameserver lines as you wish.<br />
<br />
If you use DHCP and you don't want your DNS servers to change every time you start your network, be sure to add the <code>-R</code> option to <code>DHCPCD_ARGS</code> in <code>/etc/conf.d/dhcpcd</code> (used by in <code>/etc/rc.d/network</code>). This prevents DHCP from rewritting your <code>/etc/resolv.conf</code> every time:<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
<br />
== Final Solution ==<br />
<br />
You might need to add the "-S" option to your dhcpcd arguments in order to get your network to work" <code>DHCPCD_ARGS="-S -t 30 -h $HOSTNAME"</code><br />
<br />
<br />
== Set computer name ==<br />
<br />
Edit <code>/etc/rc.conf</code> and set HOSTNAME to your desired computer name :<br />
HOSTNAME="banana"<br />
<br />
<br />
== Set host name/ip ==<br />
<br />
Edit <code>/etc/hosts</code> and add a similar line with the same HOSTNAME you entered at <code>/etc/rc.conf</code> :<br />
127.0.0.1 banana.localdomain banana<br />
<br />
<br />
== Load configuration ==<br />
To test your settings either reboot the computer, or as root, run <code>/etc/rc.d/network restart</code><br />
Try pinging your gateway, DNS server, ISP provider and other Internet site in that order to detect any connection problems along the way.<br />
<br />
<br />
== Some more settings ==<br />
<br />
=== Wireless Setup ===<br />
<br />
The wireless (wlan) configuration is topic of [[Wireless Setup|another wiki page]].<br />
<br />
=== Firewall ===<br />
<br />
You can install and configure a [[Firewalls|firewall]] to feel more secure ;-)<br />
<br />
=== Ifplugd ===<br />
<br />
You can install a daemon which will automatically configure your ethernet device when a cable is plugged in and automatically unconfigure it if the cable is pulled. This is useful on laptops with onboard network adapters, since it will only configure the interface when a cable is really connected. Other use is when you just need to restart network but don't want to restart computer or do it from shell.<br />
<br />
Installation is very simple since it's in [extra]:<br />
<br />
# pacman -S ifplugd<br />
<br />
By default it is configured to work for eth0 device. This and other settings like delays can be configured in <code>/etc/ifplugd/ifplugd.conf</code>.<br />
<br />
Start it with<br />
<br />
# /etc/rc.d/ifplugd start<br />
<br />
or add it into DAEMONS array in <code>/etc/rc.conf</code><br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The TCP Window Scaling Issue ===<br />
<br />
TCP packets contain a "window" value in their headers indicating how much data the other host may send in return. This value is represented with only 16 bits hence the window size is at most 64Kb. TCP packets are chached for a while (they have to be reordered) and as memory is (or used to be) limited one host could easily run out of it.<br />
<br />
Back in 1992, more and more memory was being available, [http://www.faqs.org/rfcs/rfc1323.html RFC 1323] was written to improve the situation: Window Scaling. The "window" value, provided in all packets will be modified by a Scale Factor defined once, at the very beginning of the connection.<br />
<br />
That 8 bits Scale Factor allows the Window to be up to 32 times higher than the initial 64Kb.<br />
<br />
It appears that some broken routers or firewalls on the Internet are rewriting the Scale Factor to 0 which causes misunderstanding between hosts.<br />
<br />
The Linux kernel 2.6.17 introduced a new calculation scheme generating higher Scale Factors virtualy making the aftermaths of the borken routers or firewalls more visible. <br />
<br />
The resulting connection is at best very slow or broken.<br />
<br />
==== HowTo Diagnose The Problem ? ====<br />
<br />
First of all, let's make it clear: this problem is odd. In some cases, you will not be able to use TCP connections (HTTP, FTP, ...) at all and in others, you will be able to communicate with some hosts (very few).<br />
<br />
'''Warning''': <code>dmesg</code>'s output is ok, logs are clean and <code>ifconfig</code> will report normal status &mdash; and actualy everything is normal.<br />
<br />
If you can't browse any website, but you can ping some rare hosts, chances are great that you're experiencing this issue: ping uses the ICMP protocol and is not affected by TCP issues.<br />
<br />
You can try to use WireShark. You might see successful UDP and ICMP communications but unsuccessful TCP communications (only to foreign hosts).<br />
<br />
=== HowTo Fix It ? (The bad way) ===<br />
<br />
To fix it the bad way, you can change the tcp_rmem value, on which Scale Factor calculation is based. Allthough it may work with most hosts, it's not guaranted, espcially with very distant ones.<br />
<br />
echo "4096 87380 174760" > /proc/sys/net/ipv4/tcp_rmem<br />
<br />
Or you can try to remove one of your stick of RAM (yes sir).<br />
<br />
=== HowTo Fix It ? (The good way) ===<br />
<br />
Simply disable Window Scaling. Even if Window Scaling is a nice TCP feature, it may be uncomfortable especially if you can't fix the broken router. There are several ways to disable Window Scaling and it seems that the most bullet-proof (which will work with most kernels) is to add the following lines to your <code>/etc/rc.local</code> :<br />
<br />
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling<br />
<br />
=== HowTo Fix It ? (The real good way) ===<br />
<br />
This issue is caused by broken routers/firewalls, let's change them. Some users have reported that the broken router was their very own DSL router.<br />
<br />
=== More about it ? ===<br />
<br />
This section is based at LWM: [http://lwn.net/Articles/92727/ TCP window scaling and broken routers] and an article at Kernel Trap: [http://kerneltrap.org/node/6723 Window Scaling on the Internet].<br />
<br />
And more recently, some Archers have been hit by this issue:<br />
<br />
* [http://www.archlinux.org/pipermail/arch/2006-June/011250.html Odd network issue]<br />
* [http://www.archlinux.org/pipermail/arch/2006-September/011943.html Kernel 2.6.17 and TCP window scaling] &mdash; The topic which initiated this article<br />
<br />
There are also several revealant threads on the LKML.</div>Nakkielhttps://wiki.archlinux.org/index.php?title=Network_configuration&diff=15275Network configuration2006-09-13T00:09:22Z<p>Nakkiel: Page clean-up. Writing an article is like writing a software. What about making it readable ?</p>
<hr />
<div>[[Category:Network]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Configuring_network}}<br />
{{i18n_entry|Slovensky|Statická IP a DHCP}}<br />
{{i18n_entry|Русский|Статический IP и DHCP}}<br />
{{i18n_links_end}}<br />
<br />
== Summary ==<br />
<br />
A simple guide to get your network running.<br />
<br />
<br />
== Load the device module ==<br />
<br />
If you use [[hwdetect]] or [[Replacing Hotplug with LSHWD|lshwd]], they should detect your network card (NIC) module and load it automatically at startup. Otherwise, you will need to know which module is needed for your particular model.<br />
<br />
Search the Web for your card model, or try using a Linux LiveCD to find out the name of the needed module - run [[Linux And Hardware|lsmod]] to show you all currently loaded modules after booting.<br />
<br />
Now when you know which module to use you can load it:<br />
<br />
# modprobe <modulename><br />
<br />
If you don't want / can't use some auto-loader like [[hwdetect]] you can add it into the modules array in <code>/etc/rc.conf</code>, so you don't need to modprobe it everytime you boot. For example, if tg3 is the network module:<br />
<br />
MODULES=(!usbserial tg3 snd-cmipci)<br />
<br />
Other common modules are 8139too for cards with the RealTek chipset or sis900 for SiS cards.<br />
<br />
== Configure IP ==<br />
<br />
=== For DHCP IP ===<br />
<br />
Edit <code>/etc/rc.conf</code> like this:<br />
<br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
INTERFACES=(lo eth0)<br />
ROUTES=(!gateway)<br />
</pre><br />
<br />
=== For Static IP ===<br />
<br />
If you share your internet connection from a Windows box without a router, be sure to use static IPs on both computers. Otherwise you will have LAN issues.<br />
<br />
You need:<br />
<br />
* Your static IP address,<br />
* The netmask,<br />
* The broadcast address,<br />
* Your gateway,<br />
* Your nameservers' IP addresses,<br />
* Your domain name.<br />
<br />
If you are running a private network, it is safe to use IP addresses in 192.168.*.'* for your IPs, with a netmask of 255.255.0.0 and broadcast address of 192.168.255.255. Unless your network has a router, the gateway address does not matter. Edit <code>/etc/rc.conf</code> like this, substituting your own values for the IP, netmask, broadcast, and gateway:<br />
<br />
<pre><br />
lo="lo 127.0.0.1"<br />
eth0="eth0 82.137.129.59 netmask 255.255.255.0 broadcast 82.137.129.255"<br />
INTERFACES=(lo eth0)<br />
gateway="default gw 82.137.129.1"<br />
ROUTES=(gateway)<br />
</pre><br />
<br />
and your <code>/etc/resolv.conf</code> like this, substituting your nameservers' IPs and your domain name:<br />
<br />
<pre><br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
</pre><br />
<br />
You may include as many nameserver lines as you wish.<br />
<br />
If you use DHCP and you don't want your DNS servers to change every time you start your network, be sure to add the <code>-R</code> option to <code>DHCPCD_ARGS</code> in <code>/etc/conf.d/dhcpcd</code> (used by in <code>/etc/rc.d/network</code>). This prevents DHCP from rewritting your <code>/etc/resolv.conf</code> every time:<br />
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"<br />
<br />
== Final Solution ==<br />
<br />
You might need to add the "-S" option to your dhcpcd arguments in order to get your network to work" <code>DHCPCD_ARGS="-S -t 30 -h $HOSTNAME"</code><br />
<br />
== Set computer name ==<br />
<br />
Edit <code>/etc/rc.conf</code> and set HOSTNAME to your desired computer name :<br />
HOSTNAME="banana"<br />
<br />
== Set host name/ip ==<br />
<br />
Edit <code>/etc/hosts</code> and add a similar line with the same HOSTNAME you entered at <code>/etc/rc.conf</code> :<br />
127.0.0.1 banana.localdomain banana<br />
<br />
== Load configuration ==<br />
To test your settings either reboot the computer, or as root, run <code>/etc/rc.d/network restart</code><br />
Try pinging your gateway, DNS server, ISP provider and other Internet site in that order to detect any connection problems along the way.<br />
<br />
== Some more settings ==<br />
<br />
=== Wireless Setup ===<br />
<br />
The wireless (wlan) configuration is topic of [[Wireless Setup|another wiki page]].<br />
<br />
=== Firewall ===<br />
<br />
You can install and configure a [[Firewalls|firewall]] to feel more secure ;-)<br />
<br />
=== Ifplugd ===<br />
<br />
You can install a daemon which will automatically configure your ethernet device when a cable is plugged in and automatically unconfigure it if the cable is pulled. This is useful on laptops with onboard network adapters, since it will only configure the interface when a cable is really connected. Other use is when you just need to restart network but don't want to restart computer or do it from shell.<br />
<br />
Installation is very simple since it's in [extra]:<br />
<br />
# pacman -S ifplugd<br />
<br />
By default it is configured to work for eth0 device. This and other settings like delays can be configured in <code>/etc/ifplugd/ifplugd.conf</code>.<br />
<br />
Start it with<br />
# /etc/rc.d/ifplugd start<br />
or add it into DAEMONS array in <code>/etc/rc.conf</code></div>Nakkiel