{"id":1317,"date":"2018-01-19T19:22:42","date_gmt":"2018-01-19T19:22:42","guid":{"rendered":"http:\/\/goofy-trucks.flywheelsites.com\/php-scripts-for-interacting-with-networks\/"},"modified":"2018-01-19T19:24:41","modified_gmt":"2018-01-19T19:24:41","slug":"php-scripts-for-interacting-with-networks","status":"publish","type":"post","link":"https:\/\/phpbuilder.com\/php-scripts-for-interacting-with-networks\/","title":{"rendered":"PHP Scripts for Interacting with Networks"},"content":{"rendered":"
\n
\n
By Leidago Noabeb<\/div>\n
on December 14, 2010<\/div>\n<\/p><\/div>\n
\n
PHP has a great many tools for interacting with a network and also with the Internet. In this article, I examine some of those tools and functions to show how exactly you can use them to make your scripts more useful in a network environment. Click here<\/a> to download the accompanying source code.<\/div>\n

Accessing Other Websites with PHP<\/h2>\n
Accessing other sites with PHP is extremely easy, but why would you want to do that? If you just want to get information from a website (for instance, a website that offers weather reports for a city that is of interest to you), then you can write a spider to get that information and more.<\/div>\n
In PHP, you access a website in pretty much the same way that you would access a text file on your hard drive — by using fopen()<\/code>.<\/div>\n
<\/p>\n
fopen(http:\/\/localhost\/websecure\/ftp.php<\/em>, \"r\");<\/pre>\n
<\/code><\/div>\n
The fopen()<\/code> function that you use to open files is the same one you use to open Web pages, because a Web page is essentially a file on a server.  The fopen()<\/code> method has the modes listed in the following table.<\/div>\n
Table 1. Modes of fopen()<\/em> Method<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n
Mode<\/th>\nMeaning<\/th>\n<\/tr>\n
r<\/td>\nReading only — Begins reading at the start of the file<\/td>\n<\/tr>\n
r+<\/td>\nReading or writing — Begins reading at the start of the file<\/td>\n<\/tr>\n
w<\/td>\nWriting only — Creates the file if it does not exist, and overwrites any existing contents<\/td>\n<\/tr>\n
w+<\/td>\nReading or writing — Creates the file if it does not exist, and overwrites any existing contents (when writing)<\/td>\n<\/tr>\n
a<\/td>\nWriting only — Creates the file if it does not exist, and appends the new data to the end of the file<\/td>\n<\/tr>\n
a+<\/td>\nReading or writing — Creates the file if it does not exist, and overwrites any existing contents (when writing)<\/td>\n<\/tr>\n
x<\/td>\nWriting only — Creates the file if it does not exist, but does nothing (issues a warning) when the file does exist<\/td>\n<\/tr>\n
x+<\/td>\nReading or writing — Creates the file if it does not exist, but does nothing (issues a warning) when the file does exist<\/td>\n<\/tr>\n<\/table>\n<\/div>\n
You will be able to open a file only for reading, unless the permissions are set otherwise. Also, you will have to use a trailing slash after a directory because fopen<\/code> does not support redirects. For example, this example is fine:<\/div>\n
<\/p>\n
fopen(\"http:\/\/localhost\/websecure\/ftp.php\/\", \"r\");<\/pre>\n
<\/code><\/div>\n
But this one will fail:<\/div>\n
<\/p>\n
fopen(http:\/\/localhost\/websecure\/ftp.php, \"r\");<\/pre>\n
<\/code><\/div>\n
When you’ve opened a file, you can pretty much treat it the same way that you would any other file, using common functions such as file()<\/code> or fgets()<\/code> to place or retrieve the data.<\/div>\n
Example code might be something like this:<\/div>\n
<\/p>\n
<!DOCTYPE html PUBLIC \"-\/\/W3C\/\/DTD XHTML 1.0 Transitional\/\/EN\"     \"http:\/\/www.w3.org\/TR\/xhtml1\/DTD\/xhtml1-transitional.dtd\">\n<html xmlns=\"http:\/\/www.w3.org\/1999\/xhtml\">\n<head>\n<meta http-equiv=\"Content-Type\" content=\"text\/html; charset=iso-8859-1\" \/>\n<title>Untitled Document<\/title>\n<\/head>\n\n<body>\n<form action=\"tester.php\" method=\"get\">\n<input name=\"url\" type=\"text\" \/>\n<input name=\"\" type=\"button\" \/>\n<\/form>\n<\/body>\n<\/html><\/pre>\n
<\/code><\/div>\n
And the processing code might look something like this:<\/div>\n
<\/p>\n
<?\n$url=$_POST['url'];\n$fp=file($url);\n$n=count($fp);\n$r=rand(0,($n-1));\necho trim($fp[$r]);\necho $n;\n?><\/pre>\n
<\/code><\/div>\n
DNS and PHP<\/h2>\n
PHP provides a powerful set of functions for DNS name resolution. The functions that PHP provides are limited to DNS client functionality; it provides no server-related functions. However, the DNS client functions are enough because most applications will require only a name-resolution service. Below is a list of some of the functions that are available in PHP (from the PHP manual):<\/div>\n
<\/p>\n
gethostbyname()\n    string gethostbyname(string hostname)<\/pre>\n
<\/code><\/div>\n
This function takes a single argument — the hostname of a machine — and returns a string corresponding to the IP address:<\/div>\n
<\/p>\n
    <?php \n    $host = \"localhost\"; \n    $ip = gethostbyname($host);\n\n    echo \"The IP address of $host is $ip\"; \n    ?><\/pre>\n
<\/code><\/div>\n
This script displays the IP address of http:\/\/localhost<\/em> as a dot-separated string of numbers. We need to obtain the IP address of a host before we can connect to it using the sockets API, as you shall soon see.<\/div>\n
<\/p>\n
gethostbynamel()\n\n    array gethostbynamel(string hostname)<\/pre>\n
<\/code><\/div>\n
Machines running operating systems that support virtual IP addresses (that is, one network card can have multiple IP addresses) can have more than one IP address associated with them. In this case, gethostbynamel()<\/code> works like gethostbyname()<\/code> but returns the complete list of IP addresses associated with that hostname as an array:<\/div>\n
<\/p>\n
    <?php \n    $host= \"localhost\"; \n    $ip= gethostbynamel($host);\n\n    echo(\"The IP addresses of $hostare:<br>n\"); \n    for ($i = 0; $i < count($ip); $i++) {\n        echo(\"$ip [i] <br>n\"); \n    }\n    ?><\/pre>\n
<\/code><\/div>\n
Assuming that web.local.com<\/em> is a machine with multiple IP addresses, this script prints a list of all those addresses.<\/div>\n
The other scenario where one DNS name maps on to multiple IP addresses is when certain DNS server implementations (such as BIND) support a feature known as DNS round robin. This is a rudimentary load-balancing mechanism where one DNS name maps to multiple machines (that is, IP addresses of multiple machines). The DNS queries are resolved by the server to each of these IP addresses using a round robin scheme, thereby distributing the request load between multiple machines. Find more information on BIND here<\/a>.<\/div>\n
<\/p>\n
gethostbyaddr()\n    string gethostbyaddr(string ip_address)<\/pre>\n
<\/code><\/div>\n
This function does the reverse of gethostbyname()<\/code> in that, given the IP address as an argument, it returns the host name corresponding to it.<\/div>\n
<\/p>\n
    <?php \n    $ip = \"127.0.0.1\"; \n    $host= gethostbyaddr($ip);\n\n    echo(\"The host name corresponding to the IP\n          address $ip is $host\"); \n    ?><\/pre>\n
<\/code><\/div>\n
This script displays the hostname corresponding to the IP address 127.0.0.1, which is always the localhost machine (that is, the machine the script was run on).<\/div>\n
While each machine on the TCP\/IP network must have at least one IP address, there is no requirement that it should have a DNS name. Thus, it is entirely possible that a machine may have an IP address and no DNS entry. In which case, the function returns the ip_address<\/code> argument itself. In fact, if an error occurs, the return value of the function is the ip_address<\/code> argument.<\/div>\n
<\/p>\n
getprotobyname()\n\n    int getprotobyname(string name)<\/pre>\n
<\/code><\/div>\n
This function returns the protocol number associated with a TCP\/IP protocol, which is a unique integer associated with the protocol name that is passed to it as an argument. The name to protocol mapping is stored in a text file, usually in \/etc\/protocols<\/em> on UNIX-derived systems and %SystemRoot%System32driversetcprotocol<\/em> on Microsoft Windows NT or Windows 2000.<\/div>\n
<\/p>\n
getprotobynumber()\n    string getprotobynumber(int number)<\/pre>\n
<\/code><\/div>\n
This function has just the opposite functionality of the getprotobyname()<\/code> function in that, given the protocol number as an argument, it displays the protocol name.<\/div>\n
<\/p>\n
getservbyname()\n    int getservbyname(string service, string protocol)<\/pre>\n
<\/code><\/div>\n
We need to obtain a well-known port number at which a service is running before our client can connect to it. This function takes a service name and the transport protocol (that is, either TCP or UDP) and returns the port number associated with the service. On most UNIX machines, the port number to service mapping is specified in the \/etc\/services<\/em> file:<\/div>\n
<\/p>\n
    <?php \n    $protocol = \"smtp\"; \n    $portNum = getservbyname($protocol, \"tcp\");\n\n    echo(\"The port number of the $protocol service is $portNum\"); \n    ?><\/pre>\n
<\/code><\/div>\n
This prints the port number of the Simple Mail Transfer Protocol (SMTP) as 25. On most UNIX machines, the information mapping the protocol name with the protocol number is available in the \/etc\/protocol<\/em> file.<\/div>\n
<\/p>\n
getservbyport()\n    string getservbyport(int port, string protocol)<\/pre>\n
<\/code><\/div>\n
This function has just the opposite functionality of getservbyname()<\/code>; it prints the service name associated with the port number argument. The protocol argument indicates the transport protocol (that is TCP or UDP) that the service is implemented over.<\/div>\n
As we saw, the getprotobyname()<\/code>, getprotobynumber()<\/code>, getservbyname()<\/code>, and getservbynumber()<\/code> functions obtain their information from files on the local file system (on most platforms). Therefore, they are not really DNS functions, but I examine them in this context because they are essentially resolver functions.<\/div>\n<\/div>\n
<\/p>\n
\n
1<\/div>\n
| <\/div>\n
2<\/a> <\/div>\n
Next Page \u00bb<\/a><\/div>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"
Use these PHP tools and functions to make your PHP scripts more useful in a network<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1317","post","type-post","status-publish","format-standard","hentry","category-tutorials"],"_links":{"self":[{"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/posts\/1317","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/comments?post=1317"}],"version-history":[{"count":1,"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/posts\/1317\/revisions"}],"predecessor-version":[{"id":3205,"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/posts\/1317\/revisions\/3205"}],"wp:attachment":[{"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/media?parent=1317"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/categories?post=1317"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/phpbuilder.com\/wp-json\/wp\/v2\/tags?post=1317"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}