Multihomed Client


 
Thread Tools Search this Thread
Top Forums Programming Multihomed Client
# 1  
Old 08-30-2005
Multihomed Client

Hi,

I am writing a socket program at the moment that uses both of the clients network interfaces. The program tries to create two socket connections to the server over a LAN connection and a GPRS connection. I have tried to update the routing table using the route command but that proved unsuccessful. I would be grateful for any help.

Thanks,
Marty
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. AIX

NIM : remove nim client info from the client

Hi. I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ? Tks (2 Replies)
Discussion started by: stephnane
2 Replies

2. IP Networking

HOWTO: Linux multihomed dns client - reverse lookup

The following thread is closed: 133552-howto-linux-multihomed-dns-client (Sorry I am not allowed to post URLs) Therefore I write this append in an own thread. The HOWTO in the referenced thread helped me a lot and I only want to append how to make reverse lookup working for a local zone: ... (0 Replies)
Discussion started by: scheruga
0 Replies

3. UNIX for Advanced & Expert Users

Multihomed server, eth1 not working

Hey everyone. We're in the process of deploying a number of servers. They're HP DL360 G6's. OS is RHEL 5.4 They've got two on board NIC's, as well as an additional dual port network card, giving us a total of 4 NIC's. Eth0 and Eth2 are bonded together using the bonding module, and the resulting... (2 Replies)
Discussion started by: msarro
2 Replies

4. IP Networking

HOWTO: Linux multihomed dns client

The Linux resolver queries all nameservers in the order they are listed in /etc/resolver.conf. If a nameserver times out, it advances on to the following nameserver. But, if a nameserver returns "not found" (NXDOMAIN) it stops. This behaviour is problematic when you need to resolve names from... (0 Replies)
Discussion started by: colemar
0 Replies

5. Programming

Client/Server Socket Application - Preventing Client from quitting on server crash

Problem - Linux Client/Server Socket Application: Preventing Client from quitting on server crash Hi, I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64. I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies

6. IP Networking

Multihomed can not ping gateway

Hello this is my first post at this forum. Apologize for my lack of network understanding but Im posting to learn. I have a problem reaching default gateway 10.18.110.1 If I use my laptop I can ping 10.18.110.1 but with our red hat multihomed server the gateway does not respond to ping. cat... (11 Replies)
Discussion started by: vettec3
11 Replies

7. HP-UX

SSH client

As user root and with some users I can use ssh to connect to remote hosts. But with a specific user I can't use ssh client because: $ ssh OpenSSL version mismatch. Built against 90807f, you have 90703f Is it a $PATH problem or what? HP-UX version is 11.11. (2 Replies)
Discussion started by: untamed
2 Replies

8. IP Networking

Multihomed DNS Clients?

I'm not sure it that's the right term for what I'm asking about, but it's the best I could come up with. Here is my situation... I'm setting up a network using OpenVPN. The clients I'm setting up will need to be able to access their own DNS servers (to resolve internal names at their location)... (4 Replies)
Discussion started by: deckard
4 Replies

9. UNIX for Dummies Questions & Answers

SSH client

How can I use ssh client with proxy support? If possible: with proxy chain support. :) (2 Replies)
Discussion started by: zylwyz
2 Replies
Login or Register to Ask a Question
accept(2)							System Calls Manual							 accept(2)

Name
       accept - accept a connection on a socket

Syntax
       #include <sys/types.h>
       #include <sys/socket.h>

       accept(s, addr, addrlen)
       int ns, s;
       struct sockaddr *addr;
       int *addrlen;

Description
       The  system call accepts a connection on a socket. The argument s is a socket that has been created with the call, bound to an address with
       the call and is listening for connections after a call.	The system call extracts the first connection on the queue of pending connections,
       creates	a new socket with the same properties of s and allocates a new file descriptor, ns, for the socket.  If no pending connections are
       present on the queue, and the socket is not marked as nonblocking, blocks the caller until a connection	is  present.   If  the	socket	is
       marked  nonblocking  and  no  pending  connections  are present on the queue, returns an error.	The accepted socket, ns, cannot be used to
       accept more connections.  The original socket s remains open.

       The argument addr is a result parameter that is filled in with the address of the connecting entity, as known to the communications  layer.
       The  exact format of the addr parameter is determined by the domain in which the communication is occurring.  The addrlen is a value-result
       parameter; it should initially contain the amount of space pointed to by addr.  On return, addr contains the actual length in bytes of  the
       address returned.  This call is used with connection-based socket types, currently with SOCK_STREAM.

       You can use the call for the purposes of doing an call by selecting the socket for reading.

Return Values
       The call returns -1 on error.  If the call succeeds, it returns a non-negative integer which is a descriptor for the accepted socket.

Diagnostics
       The call fails if:

       [EBADF]	      The descriptor is invalid.

       [ENOTSOCK]     The descriptor references a file, not a socket.

       [EOPNOTSUPP]   The referenced socket is not of type SOCK_STREAM.

       [EFAULT]       The addr parameter is not in a writable part of the user address space.

       [EWOULDBLOCK]  The socket is marked nonblocking and no connections are present to be accepted.

See Also
       bind(2), connect(2), listen(2), select(2), socket(2)

																	 accept(2)