11-26-2002
Routing Problem
I have a question concerning networking. Could any forum
members explain to me why I might be getting "no route
to host" messages when I try to connect through ftp and
http protocols?
I have went to my etc/hosts file and everything seems to be
configured properly. I can connect within my own network.
but cannot connect outside my network.
I am using Sco openserver 5.0.6.
10 More Discussions You Might Find Interesting
1. IP Networking
Hi
I know this problem is more likely some windows problem but it has also something to do with unix.
We have a windows nt environment wich uses AIX (unix) machines as file servers (samba). In our windows network environment we nicely see al the unix file servers via the 10 MB network. Last... (2 Replies)
Discussion started by: Mark Detrez
2 Replies
2. IP Networking
following Problem.
I configured my SuSE Linux 8.0 as a router. I4l, named, ip_forward, iptables (NAT/MASQUERADING) are running or are aktivatet.
I just can get a internet connection about the proxy server squid, but if i want to use other protocols i need functional routing.
(I had this... (1 Reply)
Discussion started by: razor
1 Replies
3. IP Networking
hi,
below is the situation:
my server is in 128.10.200.xxx network.
i have a solaris computer running in a subnet. this computer got 2 nic card.
1 is 172.18.198.xxx , another 1 is 10.100.xxx.11
there is a machine stick with this computer, ip is 10.100.xxx.12
so, 10.100.xxx.11 and... (3 Replies)
Discussion started by: kyhah
3 Replies
4. IP Networking
Hi,
I am trying to set up the following :
- One linux box connected to the net, static address, eth0
- No other eth interface on the box
I want to set up this box in a way it can accept remote connections, like pptp tunnels (which seems the easier to set up unless you have other idea)... (2 Replies)
Discussion started by: aerostar700
2 Replies
5. Solaris
Hi,
I got problem of Sun Solaris 8 routing.
IP of SunA is 10.16.64.164, and have routing table:
10.16.64.0 10.16.64.164 U 1 19236 bge1
10.6.0.0 10.6.0.3 U 1 16534 bge0
224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies
6. Red Hat
hi,
having an issue on a class C network with trying to get a redhat diskless setup going. I am using oracle enterprise 5, which is RHEL 5.3 i believe.
here is the scenario:
sun sparc m4k that i am planning on making the red hat boxes boot off after i get the network issue fixed.
... (3 Replies)
Discussion started by: caddyjoe77
3 Replies
7. AIX
I need the following solution , please help me...
Current situation
ip: 192.168.0.12 persistent and 192.168.254.12 service ip
gateway: 192.168.0.254
subnet: 255.255.255.0
i have added a new ip on a new nic
ip: 10.10.255.40
gateway: 10.10.255.62
subnet: 255.255.255.224
... (1 Reply)
Discussion started by: rajibimran
1 Replies
8. IP Networking
Internet Gateway
192.168.0.201
Server 1
192.168.0.101
192.168.1.101
192.168.2.101
gateway: 192.168.0.201
VIP: 192.168.1.100
VIP: 192.168.2.100
Server 2
192.168.0.102
192.168.1.102
192.168.2.102
gateway: 192.168.0.201
Client 1
192.168.2.201
gateway: 192.168.2.100 (1 Reply)
Discussion started by: hopfensp
1 Replies
9. Solaris
Hi,
I have two physical interfaces on a servers.
We have connected them to differerent subnets.
1) First interface:
10.158.49.87 to newtwork 10.158.49.0, its gateway is 10.158.49.1
(It is added as default gateway)
It is existing set up. It works well
2) Second interface:
... (1 Reply)
Discussion started by: sri243
1 Replies
10. IP Networking
hi folks,
i have a horstbox-router with the following configuration.
it has 4 ethernet ports from wich one (wan0) is configured as an external modem via dhcp. at this port/interface(wan0) it is connected with my home network (other switch).
this configuration results in the following... (14 Replies)
Discussion started by: gencaslan
14 Replies
LEARN ABOUT MOJAVE
curlopt_connect_to
CURLOPT_CONNECT_TO(3) curl_easy_setopt options CURLOPT_CONNECT_TO(3)
NAME
CURLOPT_CONNECT_TO - Connect to a specific host and port instead of the URL's host and port
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_CONNECT_TO,
struct curl_slist *connect_to);
DESCRIPTION
Pass a pointer to a linked list of strings with "connect to" information to use for establishing network connections with this handle. The
linked list should be a fully valid list of struct curl_slist structs properly filled in. Use curl_slist_append(3) to create the list and
curl_slist_free_all(3) to clean up an entire list.
Each single string should be written using the format HOST:PORT:CONNECT-TO-HOST:CONNECT-TO-PORT where HOST is the host of the request, PORT
is the port of the request, CONNECT-TO-HOST is the host name to connect to, and CONNECT-TO-PORT is the port to connect to.
The first string that matches the request's host and port is used.
Dotted numerical IP addresses are supported for HOST and CONNECT-TO-HOST. A numerical IPv6 address must be written within [brackets].
Any of the four values may be empty. When the HOST or PORT is empty, the host or port will always match (the request's host or port is
ignored). When CONNECT-TO-HOST or CONNECT-TO-PORT is empty, the "connect to" feature will be disabled for the host or port, and the
request's host or port will be used to establish the network connection.
This option is suitable to direct the request at a specific server, e.g. at a specific cluster node in a cluster of servers.
The "connect to" host and port are only used to establish the network connection. They do NOT affect the host and port that are used for
TLS/SSL (e.g. SNI, certificate verification) or for the application protocols.
In contrast to CURLOPT_RESOLVE(3), the option CURLOPT_CONNECT_TO(3) does not pre-populate the DNS cache and therefore it does not affect
future transfers of other easy handles that have been added to the same multi handle.
The "connect to" host and port are ignored if they are equal to the host and the port in the request URL, because connecting to the host
and the port in the request URL is the default behavior.
If an HTTP proxy is used for a request having a special "connect to" host or port, and the "connect to" host or port differs from the
requests's host and port, the HTTP proxy is automatically switched to tunnel mode for this specific request. This is necessary because it
is not possible to connect to a specific host or port in normal (non-tunnel) mode.
When this option is passed to curl_easy_setopt(3), libcurl will not copy the entire list so you must keep it around until you no longer use
this handle for a transfer before you call curl_slist_free_all(3) on the list.
DEFAULT
NULL
PROTOCOLS
All
EXAMPLE
CURL *curl;
struct curl_slist *connect_to = NULL;
connect_to = curl_slist_append(NULL, "example.com::server1.example.com:");
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_CONNECT_TO, connect_to);
curl_easy_setopt(curl, CURLOPT_URL, "http://example.com");
curl_easy_perform(curl);
/* always cleanup */
curl_easy_cleanup(curl);
}
curl_slist_free_all(connect_to);
AVAILABILITY
Added in 7.49.0
RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO
CURLOPT_URL(3), CURLOPT_RESOLVE(3), CURLOPT_FOLLOWLOCATION(3), CURLOPT_HTTPPROXYTUNNEL(3),
libcurl 7.54.0 May 20, 2016 CURLOPT_CONNECT_TO(3)