Skip to main content

Installing BitTorrent on Fedora Core 5



Ok fellas. This is pretty plain and simple.

[root@tarrydev ~]# yum -y install bittorrent
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
core [1/3]
core 100% |=========================| 1.1 kB 00:00
extras [2/3]
extras 100% |=========================| 1.1 kB 00:00
updates [3/3]
updates 100% |=========================| 951 B 00:00 E updates 100% |=========================| 951 B 00:14
Reading repository metadata in from local files
primary.xml.gz 3% | | 24 kB 00:10 E primary.xml.gz 14% |=== | 112 kB 00:08 E primary.xml.gz 27% |====== | 208 kB 00:05 E primary.xml.gz 42% |========== | 328 kB 00:03 E primary.xml.gz 57% |============== | 440 kB 00:02 E primary.xml.gz 72% |================== | 560 kB 00:01 E primary.xml.gz 89% |====================== | 688 kB 00:00 E primary.xml.gz 100% |=========================| 767 kB 00:02
core : ################################################## 2207/2207
Added 2207 new packages, deleted 0 old in 12.84 seconds
primary.xml.gz 4% |= | 40 kB 00:06 E primary.xml.gz 17% |==== | 160 kB 00:05 E primary.xml.gz 25% |====== | 240 kB 00:04 E primary.xml.gz 35% |======== | 328 kB 00:03 E primary.xml.gz 43% |========== | 408 kB 00:03 E primary.xml.gz 52% |============= | 496 kB 00:02 E primary.xml.gz 61% |=============== | 576 kB 00:02 E primary.xml.gz 70% |================= | 664 kB 00:01 E primary.xml.gz 79% |=================== | 744 kB 00:01 E primary.xml.gz 88% |====================== | 832 kB 00:00 E primary.xml.gz 97% |======================== | 912 kB 00:00 E primary.xml.gz 100% |=========================| 937 kB 00:03
extras : ################################################## 2620/2620
Added 2620 new packages, deleted 0 old in 15.08 seconds
primary.xml.gz 100% |=========================| 0 B 00:30
ftp://ftp.tecnoera.com/pub/fedora/linux/updates/5/i386/repodata/primary.xml. gz: [Errno 4] Socket Error: timed out
Trying other mirror.
http://www.muug.mb.ca/pub/fedora/linux/core/updates/5/i386/repodata/primary. xml.gz: [Errno 12] Timeout:
Trying other mirror.
primary.xml.gz 4% |= | 8.0 kB 00:08 E primary.xml.gz 29% |======= | 48 kB 00:04 E primary.xml.gz 74% |================== | 120 kB 00:01 E primary.xml.gz 100% |=========================| 161 kB 00:01
updates : ################################################## 521/521
Added 521 new packages, deleted 0 old in 3.39 seconds
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for bittorrent to pack into transaction set.
bittorrent-4.4.0-1.fc5.no 80% |==================== | 32 kB 00:00 E bittorrent-4.4.0-1.fc5.no 100% |=========================| 40 kB 00:00
---> Package bittorrent.noarch 0:4.4.0-1.fc5 set to be updated
--> Running transaction check
--> Processing Dependency: python-crypto for package: bittorrent
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for python-crypto to pack into transaction set.
python-crypto-2.0.1-2.fc5 100% |=========================| 14 kB 00:00
---> Package python-crypto.i386 0:2.0.1-2.fc5 set to be updated
--> Running transaction check

Dependencies Resolved

============================================================================ =
Package Arch Version Repository Size
============================================================================ =
Installing:
bittorrent noarch 4.4.0-1.fc5 extras 1.1 M
Installing for dependencies:
python-crypto i386 2.0.1-2.fc5 extras 190 k

Transaction Summary
============================================================================ =
Install 2 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 1.2 M
Downloading Packages:
(1/2): python-crypto-2.0. 21% |===== | 40 kB 00:01 E (1/2): python-crypto-2.0. 84% |===================== | 160 kB 00:00 E (1/2): python-crypto-2.0. 100% |=========================| 190 kB 00:00
(2/2): bittorrent-4.4.0-1 3% | | 40 kB 00:07 E (2/2): bittorrent-4.4.0-1 14% |=== | 160 kB 00:06 E (2/2): bittorrent-4.4.0-1 22% |===== | 240 kB 00:05 E (2/2): bittorrent-4.4.0-1 30% |======= | 328 kB 00:04 E (2/2): bittorrent-4.4.0-1 37% |========= | 408 kB 00:04 E (2/2): bittorrent-4.4.0-1 45% |=========== | 496 kB 00:03 E (2/2): bittorrent-4.4.0-1 53% |============= | 576 kB 00:02 E (2/2): bittorrent-4.4.0-1 61% |=============== | 664 kB 00:02 E (2/2): bittorrent-4.4.0-1 68% |================= | 744 kB 00:01 E (2/2): bittorrent-4.4.0-1 76% |=================== | 832 kB 00:01 E (2/2): bittorrent-4.4.0-1 84% |===================== | 912 kB 00:00 E (2/2): bittorrent-4.4.0-1 92% |======================= | 1.0 MB 00:00 E (2/2): bittorrent-4.4.0-1 99% |======================== | 1.1 MB 00:00 E (2/2): bittorrent-4.4.0-1 100% |=========================| 1.1 MB 00:04
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 1ac70ce6
Public key for python-crypto-2.0.1-2.fc5.i386.rpm is not installed
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-extras
Importing GPG key 0x1AC70CE6 "Fedora Project "
Key imported successfully
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: python-crypto ######################### [1/2]
Installing: bittorrent ######################### [2/2]

Installed: bittorrent.noarch 0:4.4.0-1.fc5
Dependency Installed: python-crypto.i386 0:2.0.1-2.fc5
Complete!

Installing the GUI

[root@tarrydev ~]# yum -y install bittorrent-gui
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
core [1/3]
extras [2/3]
updates [3/3]
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for bittorrent-gui to pack into transaction set.
bittorrent-gui-4.4.0-1.fc 100% |=========================| 13 kB 00:00
---> Package bittorrent-gui.noarch 0:4.4.0-1.fc5 set to be updated
--> Running transaction check

Dependencies Resolved

============================================================================ =
Package Arch Version Repository Size
============================================================================ =
Installing:
bittorrent-gui noarch 4.4.0-1.fc5 extras 107 k

Transaction Summary
============================================================================ =
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 107 k
Downloading Packages:
(1/1): bittorrent-gui-4.4 22% |===== | 24 kB 00:01 E (1/1): bittorrent-gui-4.4 100% |=========================| 107 kB 00:00
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: bittorrent-gui ######################### [1/2]
Removing : BitTorrent ######################### [2/2]

Installed: bittorrent-gui.noarch 0:4.4.0-1.fc5
Complete!

For your Security Enhanced linux with Firewalling do the following to allow for the ports...


[root@tarrydev ~]# /sbin/iptables -I INPUT -p tcp --destination-port 6881:69 99 -j ACCEPT

SAVE

[root@tarrydev ~]# /sbin/iptables-save > /etc/sysconfig/iptables

List them tables

[root@tarrydev ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpts:6881:iatp-normalpri
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT ipv6-crypt-- anywhere anywhere
ACCEPT ipv6-auth-- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ftp
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:smtp
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
ACCEPT udp -- anywhere anywhere state NEW udp dpt:netbios-ns
ACCEPT udp -- anywhere anywhere state NEW udp dpt:netbios-dgm
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:netbios-ssn
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:microsoft-ds
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:https
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited


You're done!

Comments

Popular posts from this blog

DeepLearningTrucker Part 1

Avastu Blog is migrating to IdeationCloud.com; 1st Jan 2009 live

YOU DON'T HAVE TO DO ANYTHING. WITHIN 2 SECONDS YOU WILL BE REDIRECTED TO THE NEW HOME OF AVASTU BLOG. PLEASE DO UPDATE AVASTU BLOG'S URL to : http://www.ideationcloud.com on your website.

I will send out emails personally to those who are using my link(s) on their sites.

Thanks much for your co-operation and hope you enjoy the new site and its cool new features :-)




Not like the site is unlive or something..on the contrary, its beginning to get a lot of attention already. Well most of the work is done, you don't have to worry about anything though:

What won't change

Links/Referrals: I will be redirecting the links (all links which you may have cross-posted) to IdeationCloud.com - so you don't have to do anything in all your posts and links. Although, I would urge however that you do change the permalinks, especially on your blogs etc yourselfThis blog is not going away anywhere but within a few months, I will consider discontinuing its usage. I won't obviously do …

Cloud Security: Eliminate humans from the "Information Supply Chain on the Web"

My upcoming article, part - 3 data center predictions for 2009, has a slideshot talking about the transition from the current age to the cloud computing age to eventually the ideation age- the age where you will have clouds that will emote but they will have no internal employees.

Biggest management disasters occur because internal folks are making a mess of the playground.

Om's blog is carrying an article about Cloud security and it is rather direct but also makes a lot of sense:

I don’t believe that clouds themselves will cause the security breaches and data theft they anticipate; in many ways, clouds will result in better security. Here’s why: Fewer humans –Most computer breaches are the result of human error; only 20-40 percent stem from technical malfunctions. Cloud operators that want to be profitable take humans out of the loop whenever possible.Better tools – Clouds can afford high-end data protection and security monitoring tools, as well as the experts to run them. I trust…