https://wiki.archlinux.org/api.php?action=feedcontributions&user=RamirezTerrix&feedformat=atomArchWiki - User contributions [en]2024-03-28T14:52:01ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Gerbera&diff=358731Gerbera2015-01-29T19:26:35Z<p>RamirezTerrix: /* The Client loses connection after 30 Minutes */</p>
<hr />
<div>[[Category:Streaming]]<br />
{{Related articles start}}<br />
{{Related|Streaming media}}<br />
{{Related articles end}}<br />
<br />
From [http://mediatomb.cc/ MediaTomb - Free UPnP MediaServer]:<br />
<br />
:''MediaTomb is an open source (GPL) UPnP MediaServer with a nice web user interface, it allows you to stream your digital media through your home network and listen to/watch it on a variety of UPnP compatible devices.''<br />
<br />
MediaTomb enables users to stream digital media to UPnP compatible devices like the PlayStation 3 (the Xbox 360 is not yet supported). Several alternatives exist, such as [http://sourceforge.net/projects/fuppes FUPPES], [http://code.google.com/p/ps3mediaserver/ ps3mediaserver], and [[uShare]]. One of MediaTomb's distinguishing features is the ability to customize the server layout based on extracted metadata (scriptable virtual containers); MediaTomb is highly flexible.<br />
<br />
== Installation ==<br />
<br />
MediaTomb is available in the [[AUR]] via {{AUR|mediatomb}}.<br />
<br />
The latest development version is also available in the [[AUR]] via {{AUR|mediatomb-git}}.<br />
<br />
Mediatomb can use its own database, or your local [[MariaDB]] server. For more information about the [[MariaDB]] integration visit the [http://mediatomb.cc/pages/documentation#id2855459 Documentation].<br />
<br />
== Configuration ==<br />
<br />
The default settings may be sufficient for many users, though changes are required for PlayStation 3 support. MediaTomb may be configured and run per-user or as a system-wide daemon. Following installation, either run<br />
<br />
$ mediatomb<br />
<br />
to start MediaTomb as the current user and generate a default configuration in {{ic|~/.mediatomb/config.xml}}, or<br />
<br />
# systemctl start mediatomb<br />
<br />
to start the MediaTomb daemon and generate a default configuration in {{ic|/var/lib/mediatomb/.mediatomb/config.xml}}.<br />
<br />
If you want to use the [[MariaDB]] database backend, you can alternatively run<br />
<br />
# systemctl start mediatomb-mariadb<br />
<br />
which will ensure that [[MariaDB]] is up and running before MediaTomb is.<br />
<br />
<br />
<br />
== Usage ==<br />
<br />
The daemon listens on port 50500 by default. To access the web interface and begin importing media, navigate to http://127.0.0.1:50500/ in your favorite browser (JavaScript required).<br />
<br />
If running per-user instances of MediaTomb, the default port is 49152. However, it is possible that the port will change upon server restart. The URL for the web interface is output during startup. Users may also specify the port manually:<br />
<br />
$ mediatomb -p 50500<br />
<br />
<br />
== Hiding full paths from media players ==<br />
<br />
By default, full directory paths will be shown on devices when they are browsing through folders.<br />
<br />
For example, if you add the directory /media/my_media/video_data/videos/movies, anyone connecting will have to navigate to the 'movies' directory from the root.<br />
<br />
To hide all of that and only show the directory added, you can change the import script.<br />
<br />
For example, this script will automatically truncate the whole directory structure specified in the variable video_root. Any directories added directly under the video root path will show up on UPnP devices starting from the that folder rather than /.<br />
<br />
function addVideo(obj)<br />
{<br />
var video_root = "/media/main_core/Server_Core_Folder/FTP_Services/Media/";<br />
<br />
var absolute_path = obj.location;<br />
<br />
var relative_path = absolute_path;<br />
<br />
if(absolute_path.indexOf(video_root) == 0)<br />
relative_path = absolute_path.replace(video_root, "")<br />
<br />
var chain = new Array();<br />
<br />
var pathSplit = relative_path.split("/");<br />
<br />
for(var i = 0; i < pathSplit.length - 1; i++) <br />
chain.push(pathSplit[i]);<br />
<br />
addCdsObject(obj, createContainerChain(chain));<br />
}<br />
<br />
To also hide the default PC Directory folder from UPnP device directory listings, add the following directly under the server node of your config.xml file.<br />
<br />
<pc-directory upnp-hide="yes"/><br />
<br />
<br />
== Playstation 3 Support ==<br />
<br />
The following notes assume MediaTomb is running as a system-wide daemon. For a per-user install, the locations of the configuration file will be different (see above).<br />
<br />
For PlayStation 3 support, users must set {{Ic|<nowiki><protocolInfo extend="yes"/></nowiki>}}. An "avi" mimetype mapping should also be uncommented for DivX support.<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<protocolInfo extend="yes"/><br />
<br />
...<br />
<br />
<map from="avi" to="video/divx"/><br />
<br />
...<br />
</nowiki>}}<br />
<br />
When importing media to the database, MediaTomb will create a virtual container layout as defined by the {{Ic|<nowiki><virtual-layout type="..."></nowiki>}} option. That is, media will be organized according to metadata (album, artist, etc.) through creation of virtual database objects. If your media is already organized on the file system, you may disable this feature to significantly improve import performance:<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<virtual-layout type="disabled"/><br />
<br />
...<br />
</nowiki>}}<br />
<br />
Users may customize the import script to fine-tune the virtual layout. The [http://mediatomb.cc/dokuwiki/scripting:scripting Scripting] section of the MediaTomb wiki provides several examples. Starting with the built-in script available at {{ic|/usr/share/mediatomb/js/import.js}}:<br />
<br />
$ cp /usr/share/mediatomb/js/import.js /var/lib/mediatomb/.mediatomb/<br />
<br />
... and edit {{ic|/var/lib/mediatomb/.mediatomb/import.js}} as desired. To utilize the customized script, users must set {{Ic|<nowiki><virtual-layout type="js"></nowiki>}} and specify the script's location.<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<virtual-layout type="js"><br />
<import-script>/var/lib/mediatomb/.mediatomb/import.js</import-script><br />
</virtual-layout><br />
<br />
...<br />
</nowiki>}}<br />
<br />
You may have to specify an interface before MediaTomb will be recognized:<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|<nowiki><br />
<server><br />
...<br />
<interface>eth0</interface><br />
...<br />
</server><br />
</nowiki>}}<br />
<br />
... replacing eth0 with the interface you connect on.<br />
<br />
After configuring MediaTomb to your liking, restart the server by running<br />
<br />
# systemctl restart mediatomb<br />
<br />
<br />
== Samsung TV Support ==<br />
For Samsung TV support users should install {{AUR|mediatomb-samsung-tv}} from the [[AUR]], which it's the same as the {{AUR|mediatomb}} package with a few more patches. Note that the TV must have [http://en.wikipedia.org/wiki/Digital_Living_Network_Alliance DLNA] support. Also the server and the TV should be connected to the same network.<br />
<br />
The following note assume MediaTomb is running as a system-wide daemon. For a per-user install, the locations of the configuration file will be different (see above). <br />
<br />
Some models require changes in config.xml. Users should edit the {{Ic|<nowiki><custom-http-headers></nowiki>}} section and add two entries in the {{Ic|<nowiki><mappings></nowiki>}} section for better compatibility.<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<custom-http-headers><br />
<add header="transferMode.dlna.org: Streaming"/><br />
<add header="contentFeatures.dlna.org: DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=017000 00000000000000000000000000"/><br />
</custom-http-headers><br />
<br />
...<br />
<br />
<map from="avi" to="video/mpeg"/><br />
<map from="mkv" to="video/mpeg"/><br />
<br />
...<br />
</nowiki>}}<br />
<br />
== Systemd Integration ==<br />
<br />
The mediatomb package comes with two [[systemd]] service files: mediatomb.service and mediatomb-mariadb.service. They run as 'mediatomb' user, which was created on install, as it isn't secure to run them as root.<br />
<br />
Choose which one you want to use, based on whether you want mediatomb to wait for mariadb to be up and running first or not. I.e. if you use a mariadb backend use mediatomb-mariadb.service, and use mediatomb.service otherwise.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Mediatomb doesn't provide content even though it is added in the webfrontend ===<br />
Be aware of the fact that the user Mediatomb runs under, has to have read rights on the files that are added to be able to provide them. <br />
<br />
So if Mediatomb runs under the user 'mediatomb' the (video-)files either have to be owned by the user 'mediatomb' and need to be readable or the files and the user 'mediatomb' have to belong to the same group with the file being readable ('mediatomb' has to be in the group to which the file belongs (the file then needs the read rights for the group to be set)).<br />
<br />
=== The Client loses connection after 30 Minutes ===<br />
Apparently this is related to SSNP message only being sent once which results in the Client dropping its connection in 30 minutes since it thinks the server is gone.<br />
<br />
In the config.xml add the alive tag<br />
''<br />
<alive>180</alive><br />
<br />
Optional<br />
<br />
Default: 180, this is according to the UPnP specification.<br />
<br />
Interval for broadcasting SSDP:alive messages<br />
<br />
From http://mediatomb.cc/pages/documentation#id2856362''</div>RamirezTerrixhttps://wiki.archlinux.org/index.php?title=Gerbera&diff=358730Gerbera2015-01-29T19:26:18Z<p>RamirezTerrix: /* Troubleshooting */</p>
<hr />
<div>[[Category:Streaming]]<br />
{{Related articles start}}<br />
{{Related|Streaming media}}<br />
{{Related articles end}}<br />
<br />
From [http://mediatomb.cc/ MediaTomb - Free UPnP MediaServer]:<br />
<br />
:''MediaTomb is an open source (GPL) UPnP MediaServer with a nice web user interface, it allows you to stream your digital media through your home network and listen to/watch it on a variety of UPnP compatible devices.''<br />
<br />
MediaTomb enables users to stream digital media to UPnP compatible devices like the PlayStation 3 (the Xbox 360 is not yet supported). Several alternatives exist, such as [http://sourceforge.net/projects/fuppes FUPPES], [http://code.google.com/p/ps3mediaserver/ ps3mediaserver], and [[uShare]]. One of MediaTomb's distinguishing features is the ability to customize the server layout based on extracted metadata (scriptable virtual containers); MediaTomb is highly flexible.<br />
<br />
== Installation ==<br />
<br />
MediaTomb is available in the [[AUR]] via {{AUR|mediatomb}}.<br />
<br />
The latest development version is also available in the [[AUR]] via {{AUR|mediatomb-git}}.<br />
<br />
Mediatomb can use its own database, or your local [[MariaDB]] server. For more information about the [[MariaDB]] integration visit the [http://mediatomb.cc/pages/documentation#id2855459 Documentation].<br />
<br />
== Configuration ==<br />
<br />
The default settings may be sufficient for many users, though changes are required for PlayStation 3 support. MediaTomb may be configured and run per-user or as a system-wide daemon. Following installation, either run<br />
<br />
$ mediatomb<br />
<br />
to start MediaTomb as the current user and generate a default configuration in {{ic|~/.mediatomb/config.xml}}, or<br />
<br />
# systemctl start mediatomb<br />
<br />
to start the MediaTomb daemon and generate a default configuration in {{ic|/var/lib/mediatomb/.mediatomb/config.xml}}.<br />
<br />
If you want to use the [[MariaDB]] database backend, you can alternatively run<br />
<br />
# systemctl start mediatomb-mariadb<br />
<br />
which will ensure that [[MariaDB]] is up and running before MediaTomb is.<br />
<br />
<br />
<br />
== Usage ==<br />
<br />
The daemon listens on port 50500 by default. To access the web interface and begin importing media, navigate to http://127.0.0.1:50500/ in your favorite browser (JavaScript required).<br />
<br />
If running per-user instances of MediaTomb, the default port is 49152. However, it is possible that the port will change upon server restart. The URL for the web interface is output during startup. Users may also specify the port manually:<br />
<br />
$ mediatomb -p 50500<br />
<br />
<br />
== Hiding full paths from media players ==<br />
<br />
By default, full directory paths will be shown on devices when they are browsing through folders.<br />
<br />
For example, if you add the directory /media/my_media/video_data/videos/movies, anyone connecting will have to navigate to the 'movies' directory from the root.<br />
<br />
To hide all of that and only show the directory added, you can change the import script.<br />
<br />
For example, this script will automatically truncate the whole directory structure specified in the variable video_root. Any directories added directly under the video root path will show up on UPnP devices starting from the that folder rather than /.<br />
<br />
function addVideo(obj)<br />
{<br />
var video_root = "/media/main_core/Server_Core_Folder/FTP_Services/Media/";<br />
<br />
var absolute_path = obj.location;<br />
<br />
var relative_path = absolute_path;<br />
<br />
if(absolute_path.indexOf(video_root) == 0)<br />
relative_path = absolute_path.replace(video_root, "")<br />
<br />
var chain = new Array();<br />
<br />
var pathSplit = relative_path.split("/");<br />
<br />
for(var i = 0; i < pathSplit.length - 1; i++) <br />
chain.push(pathSplit[i]);<br />
<br />
addCdsObject(obj, createContainerChain(chain));<br />
}<br />
<br />
To also hide the default PC Directory folder from UPnP device directory listings, add the following directly under the server node of your config.xml file.<br />
<br />
<pc-directory upnp-hide="yes"/><br />
<br />
<br />
== Playstation 3 Support ==<br />
<br />
The following notes assume MediaTomb is running as a system-wide daemon. For a per-user install, the locations of the configuration file will be different (see above).<br />
<br />
For PlayStation 3 support, users must set {{Ic|<nowiki><protocolInfo extend="yes"/></nowiki>}}. An "avi" mimetype mapping should also be uncommented for DivX support.<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<protocolInfo extend="yes"/><br />
<br />
...<br />
<br />
<map from="avi" to="video/divx"/><br />
<br />
...<br />
</nowiki>}}<br />
<br />
When importing media to the database, MediaTomb will create a virtual container layout as defined by the {{Ic|<nowiki><virtual-layout type="..."></nowiki>}} option. That is, media will be organized according to metadata (album, artist, etc.) through creation of virtual database objects. If your media is already organized on the file system, you may disable this feature to significantly improve import performance:<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<virtual-layout type="disabled"/><br />
<br />
...<br />
</nowiki>}}<br />
<br />
Users may customize the import script to fine-tune the virtual layout. The [http://mediatomb.cc/dokuwiki/scripting:scripting Scripting] section of the MediaTomb wiki provides several examples. Starting with the built-in script available at {{ic|/usr/share/mediatomb/js/import.js}}:<br />
<br />
$ cp /usr/share/mediatomb/js/import.js /var/lib/mediatomb/.mediatomb/<br />
<br />
... and edit {{ic|/var/lib/mediatomb/.mediatomb/import.js}} as desired. To utilize the customized script, users must set {{Ic|<nowiki><virtual-layout type="js"></nowiki>}} and specify the script's location.<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<virtual-layout type="js"><br />
<import-script>/var/lib/mediatomb/.mediatomb/import.js</import-script><br />
</virtual-layout><br />
<br />
...<br />
</nowiki>}}<br />
<br />
You may have to specify an interface before MediaTomb will be recognized:<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|<nowiki><br />
<server><br />
...<br />
<interface>eth0</interface><br />
...<br />
</server><br />
</nowiki>}}<br />
<br />
... replacing eth0 with the interface you connect on.<br />
<br />
After configuring MediaTomb to your liking, restart the server by running<br />
<br />
# systemctl restart mediatomb<br />
<br />
<br />
== Samsung TV Support ==<br />
For Samsung TV support users should install {{AUR|mediatomb-samsung-tv}} from the [[AUR]], which it's the same as the {{AUR|mediatomb}} package with a few more patches. Note that the TV must have [http://en.wikipedia.org/wiki/Digital_Living_Network_Alliance DLNA] support. Also the server and the TV should be connected to the same network.<br />
<br />
The following note assume MediaTomb is running as a system-wide daemon. For a per-user install, the locations of the configuration file will be different (see above). <br />
<br />
Some models require changes in config.xml. Users should edit the {{Ic|<nowiki><custom-http-headers></nowiki>}} section and add two entries in the {{Ic|<nowiki><mappings></nowiki>}} section for better compatibility.<br />
<br />
{{hc|/var/lib/mediatomb/.mediatomb/config.xml<br />
|2=<nowiki><br />
...<br />
<br />
<custom-http-headers><br />
<add header="transferMode.dlna.org: Streaming"/><br />
<add header="contentFeatures.dlna.org: DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=017000 00000000000000000000000000"/><br />
</custom-http-headers><br />
<br />
...<br />
<br />
<map from="avi" to="video/mpeg"/><br />
<map from="mkv" to="video/mpeg"/><br />
<br />
...<br />
</nowiki>}}<br />
<br />
== Systemd Integration ==<br />
<br />
The mediatomb package comes with two [[systemd]] service files: mediatomb.service and mediatomb-mariadb.service. They run as 'mediatomb' user, which was created on install, as it isn't secure to run them as root.<br />
<br />
Choose which one you want to use, based on whether you want mediatomb to wait for mariadb to be up and running first or not. I.e. if you use a mariadb backend use mediatomb-mariadb.service, and use mediatomb.service otherwise.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Mediatomb doesn't provide content even though it is added in the webfrontend ===<br />
Be aware of the fact that the user Mediatomb runs under, has to have read rights on the files that are added to be able to provide them. <br />
<br />
So if Mediatomb runs under the user 'mediatomb' the (video-)files either have to be owned by the user 'mediatomb' and need to be readable or the files and the user 'mediatomb' have to belong to the same group with the file being readable ('mediatomb' has to be in the group to which the file belongs (the file then needs the read rights for the group to be set)).<br />
<br />
=== The Client loses connection after 30 Minutes ===<br />
Apparently this is related to SSNP message only being sent once which results in the Client dropping its connection in 30 minutes since it thinks the server is gone.<br />
<br />
In the config.xml add the alive tag<br />
""<br />
<alive>180</alive><br />
<br />
Optional<br />
<br />
Default: 180, this is according to the UPnP specification.<br />
<br />
Interval for broadcasting SSDP:alive messages<br />
<br />
From http://mediatomb.cc/pages/documentation#id2856362''</div>RamirezTerrixhttps://wiki.archlinux.org/index.php?title=Android_tethering&diff=356472Android tethering2015-01-13T13:25:38Z<p>RamirezTerrix: /* USB tethering */</p>
<hr />
<div>[[Category:Networking]]<br />
[[Category:Mobile devices]]<br />
[[fr:Modem attache Android]]<br />
[[ja:Android tethering]]<br />
[[ru:Android tethering]]<br />
Tethering is a way to have internet access on your PC through your smartphone using its network connection. USB tethering and Wi-Fi access point tethering are natively supported since Android Froyo (2.2). In older versions of the Android OS, most unofficial ROMs have this option enabled.<br />
<br />
== Wi-Fi access point ==<br />
Using an Android phone as a Wi-Fi access point (using 3G) has been accessible by default since Froyo (Android 2.2) without needing to root the phone. Moreover, this method will discharge the battery rapidly and tends to cause intense heating, unlike USB.<br />
See : '''menu/wireless & networks/Internet tethering/Wi-Fi access point'''<br />
<br />
== USB tethering ==<br />
<br />
===Tools Needed===<br />
* Root access to the phone (for old Android versions, Froyo (Android 2.2) and beyond can do it natively)<br />
* USB connection cable from your phone to PC<br />
<br />
=== Procedure ===<br />
* Disconnect your computer from any wireless or wired networks<br />
* Connect the phone to your computer using the USB cable (the USB connection mode -- Phone Portal, Memory Card or Charge only -- is not important, but please note that you will not be able to change the USB mode during tethering)<br />
* Enable the tethering option from your phone. This is usually done from {{ic|Settings --> Wireless & Networks --> Internet tethering}} (or {{ic|Tethering & portable hotspot}}, for more recent versions)<br />
* Make sure that the USB interface is recognized by the system by using the following command:<br />
: {{bc|$ ip link}}<br />
: You should be able to see a {{ic|usb0}} or {{ic|enp?s??u?}} device listed like this (notice the enp0s20u3 device).<br />
{{hc|# ip link|<br />
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default <br />
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br />
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000<br />
link/ether ##:##:##:##:##:## brd ff:ff:ff:ff:ff:ff<br />
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000<br />
link/ether ##:##:##:##:##:## brd ff:ff:ff:ff:ff:ff<br />
5: enp0s20u3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000<br />
link/ether ##:##:##:##:##:## brd ff:ff:ff:ff:ff:ff<br />
}}<br />
<br />
{{Note|Take care to use the device name from your own system in the following commands.}}<br />
<br />
{{Warning|The name may change depending on the usb port you use. You may want to [[Network configuration#Change_device_name|change the device name]] to create a unique name for your device regardless of the usb port.}}<br />
<br />
* The final step is to [[Network configuration#Configure the IP address|configure a network connection]] on this interface.<br />
{{Note|In most cases you can use: # dhcpcd}}<br />
<br />
==USB tethering with OpenVPN==<br />
This method works for any old Android version and requires neither root access nor modifications in the phone (it is also suitable for Android 2.2 and later, but no longer required).<br />
<br />
It does not require changes to your browser. In fact, all network traffic is transparently handled for any PC application (except ICMP pings). It is somewhat CPU intensive on the phone at high usage rates (a 500 kBytes/sec data transfer rate may take more than 50% of phone CPU on a powerful Acer Liquid).<br />
<br />
===Tools Needed===<br />
For Arch, you need to [[pacman|install]] the {{pkg|openvpn}} package. It is also required to have the Android SDK installed (which can be obtained [http://developer.android.com/sdk/index.html here] or from the AUR). On the phone, you need the [http://code.google.com/p/azilink/ azilink] application, which is a Java-based NAT that will communicate with OpenVPN on your computer.<br />
<br />
====Configuring the phone connection in Arch Linux====<br />
<br />
Once you have installed the Android SDK, in order to use the provided tools your phone must be properly set up in [[udev]] and your Linux user needs to be granted rights. Otherwise you may need root privileges to use the Android SDK, which is not recommended. To perform this configuration, turn on USB debugging on the phone (usually in Settings -> Applications -> Development -> USB debugging), connect it to the PC by the USB cable and run the {{ic|lsusb}} command. The device should be listed. Example output for the Acer Liquid phone:<br />
<br />
Bus 001 Device 006: ID '''0502''':3202 Acer, Inc. <br />
<br />
Then, create the following file, replacing ''ciri'' by your own Linux user name, and '''0502''' by the vendor ID of your own phone:<br />
<br />
{{hc|/etc/udev/rules.d/51-android.rules|<nowiki><br />
SUBSYSTEM=="usb", ATTR(idVendor)=="0502", MODE="0666" OWNER="ciri"<br />
</nowiki>}}<br />
<br />
As root run the {{ic|udevadm control restart}} command (or reboot your computer) to make the change effective.<br />
<br />
Now run in your linux PC the {{ic|adb shell}} command from the Android SDK as plain (non root) user: you should get a unix prompt ''in your phone''.<br />
<br />
===Procedure===<br />
Run the AziLink application in the phone and select "About" at the bottom to receive instructions, which basically are:<br />
<br />
# You will have to enable USB debugging on the phone if it was not already enabled (usually in Settings -> Applications -> Development -> USB debugging).<br />
# Connect the phone with the USB cable to the PC.<br />
# Run AziLink and make sure that the '''Service active''' option at the top is checked.<br />
# Run the following commands in your Linux PC:<br />
: {{bc|$ adb forward tcp:41927 tcp:41927}}<br />
: {{bc|# openvpn AziLink.ovpn}}<br />
<br />
{{hc|AziLink.ovpn|<nowiki><br />
dev tun<br />
remote 127.0.0.1 41927 tcp-client<br />
ifconfig 192.168.56.2 192.168.56.1<br />
route 0.0.0.0 128.0.0.0<br />
route 128.0.0.0 128.0.0.0<br />
socket-flags TCP_NODELAY<br />
keepalive 10 30<br />
dhcp-option DNS 192.168.56.1<br />
</nowiki>}}<br />
<br />
===Troubleshooting===<br />
<br />
====DNS====<br />
You may need to manually update the contents of [[resolv.conf]] to<br />
<br />
{{hc|/etc/resolv.conf|<br />
nameserver 192.168.56.1<br />
}}<br />
<br />
====NetworkManager====<br />
If you're running NetworkManager, you may need to stop it before running OpenVPN.<br />
<br />
==Tethering via Bluetooth==<br />
<br />
Android (from at least 4.0 onwards, possibly earlier) can provide a Bluetooth personal-area network (PAN) in access point mode.<br />
<br />
NetworkManager can perform this action and handle the network initialisation itself; consult its documentation for more details. <br />
<br />
Alternatively: pair and ensure you can connect your computer and Android device, as described on [[Bluetooth]], then, substituting the address of the device (here given as {{ic|AA_BB_CC_DD_EE_FF}}), do:<br />
<br />
{{bc|<nowiki>$ dbus-send --system --type=method_call --dest=org.bluez /org/bluez/hci0/dev_AA_BB_CC_DD_EE_FF org.bluez.Network1.Connect string:'nap'</nowiki>}}<br />
<br />
This will create a network interface {{ic|bnep0}}. Finally, [[Network configuration#Configure the IP address|configure a network connection]] on this interface; Android offers DHCP by default.<br />
<br />
==Tethering with SOCKS proxy==<br />
<br />
With this method tethering is achieved by port forwarding from the phone to the PC. This is suitable only for browsing. For Firefox, you should set '''network.proxy.socks_remote_dns''' to '''true''' in '''about:config''' ( address bar )<br />
<br />
===Tools Needed===<br />
* {{AUR|android-sdk}} and {{AUR|android-sdk-platform-tools}} from [[AUR]] and {{Pkg|android-udev}} from [[official repositories]]<br />
* USB connection cable from your phone to PC<br />
* Either [http://graha.ms/androidproxy/ Tetherbot] or [https://code.google.com/p/proxoid/ Proxoid]<br />
<br />
===Instructions===<br />
====Tetherbot====<br />
Follow the instructions under '''Using the Socks Proxy''' on [http://graha.ms/androidproxy/].<br />
<br />
====Proxoid====<br />
Follow the instructions demonstrated in the following [http://androidcommunity.com/forums/f23/android-usb-tethering-for-linux-using-proxoid-24875/ link]</div>RamirezTerrixhttps://wiki.archlinux.org/index.php?title=Inkscape&diff=260816Inkscape2013-06-03T06:28:31Z<p>RamirezTerrix: /* Installation */</p>
<hr />
<div>[[Category:Graphics and desktop publishing]]<br />
{{stub}}<br />
<br />
[http://inkscape.org/ Inkscape] is a vector graphics editor application. It is distributed under a free software license, the GNU GPL. Its stated goal is to become a powerful graphics tool while being fully compliant with the XML, SVG, and CSS standards.[http://en.wikipedia.org/wiki/Inkscape]<br />
== Installation ==<br />
{{pkg|inkscape}} can be installed from the [[Official Repositories|official repositories]].<br />
<br />
=== Without GNOME dependencies ===<br />
Inkscape has quite a few [[GNOME]] dependencies, which can be annoying to users of other environments. If you do not want these, you can compile {{AUR|inkscape-bzr}} from the [[Arch User Repository|AUR]].<br />
<br />
==Troubleshooting==<br />
<br />
=== Build error with libpng 1.2.x ===<br />
If inkscape fails to build with the following error:<br />
In file included from /usr/include/libpng12/png.h:474,<br />
from sp-image.cpp:44:<br />
/usr/include/libpng12/pngconf.h:328: error: expected constructor, destructor, or type conversion before '.' token<br />
/usr/include/libpng12/pngconf.h:329: error: '__dont__' does not name a type<br />
<br />
You should be able to solve that by simply commenting the two mentioned Lines in {{ic|/usr/include/libpng12/pngconf.h}} out:<br />
<br />
//__pngconf.h__ already includes setjmp.h;<br />
//__dont__ include it again.;<br />
<br />
(I have got no idea what else those changes influence, so you might want to undo them after inkscape is built. This could be related to Debian Bug#522477 and might get fixed in libpng 1.4)<br />
<br />
== Related pages ==<br />
[[Multimedia in Arch Linux]]<br />
<br />
[http://inkscape.org/ Inkscape Homepage]<br />
<br />
[[Wikipedia:Inkscape|Inkscape at Wikipedia]]</div>RamirezTerrixhttps://wiki.archlinux.org/index.php?title=Talk:Inkscape&diff=260815Talk:Inkscape2013-06-03T06:23:08Z<p>RamirezTerrix: Created page with "inkscape-nognome is no longer avaible via AUR"</p>
<hr />
<div>inkscape-nognome is no longer avaible via AUR</div>RamirezTerrixhttps://wiki.archlinux.org/index.php?title=Inkscape&diff=260814Inkscape2013-06-03T06:22:21Z<p>RamirezTerrix: /* Installation */</p>
<hr />
<div>[[Category:Graphics and desktop publishing]]<br />
{{stub}}<br />
<br />
[http://inkscape.org/ Inkscape] is a vector graphics editor application. It is distributed under a free software license, the GNU GPL. Its stated goal is to become a powerful graphics tool while being fully compliant with the XML, SVG, and CSS standards.[http://en.wikipedia.org/wiki/Inkscape]<br />
== Installation ==<br />
{{pkg|inkscape}} can be installed from the [[Official Repositories|official repositories]].<br />
<br />
=== Without GNOME dependencies ===<br />
Inkscape has quite a few [[GNOME]] dependencies, which can be annoying to users of other environments. If you do not want these, you can compile {{AUR|inkscapeslide-git}} from the [[Arch User Repository|AUR]].<br />
<br />
==Troubleshooting==<br />
<br />
=== Build error with libpng 1.2.x ===<br />
If inkscape fails to build with the following error:<br />
In file included from /usr/include/libpng12/png.h:474,<br />
from sp-image.cpp:44:<br />
/usr/include/libpng12/pngconf.h:328: error: expected constructor, destructor, or type conversion before '.' token<br />
/usr/include/libpng12/pngconf.h:329: error: '__dont__' does not name a type<br />
<br />
You should be able to solve that by simply commenting the two mentioned Lines in {{ic|/usr/include/libpng12/pngconf.h}} out:<br />
<br />
//__pngconf.h__ already includes setjmp.h;<br />
//__dont__ include it again.;<br />
<br />
(I have got no idea what else those changes influence, so you might want to undo them after inkscape is built. This could be related to Debian Bug#522477 and might get fixed in libpng 1.4)<br />
<br />
== Related pages ==<br />
[[Multimedia in Arch Linux]]<br />
<br />
[http://inkscape.org/ Inkscape Homepage]<br />
<br />
[[Wikipedia:Inkscape|Inkscape at Wikipedia]]</div>RamirezTerrix