Blocking bind to outbound interface?
Is there any way to block use of an interface for outbound connections?
I have a host who's primary outbound interface is on a private network (using a private address block for our backbone). Unfortunately, this means that most applications (those not providing an option to select bind address) will bind to this private-net address when establishing outbound connections or sending udp packets.
The host has another address which is a publically accessible ip, but it's not the default route interface.
Is there any way to hide this interface on the host for ALL outbound connections without modifying all applications/app invocations? Or some way of overriding the mechanism for selection of default interface.
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: [email protected]
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems Programming Fax: (573) 341-4216
Use iproute2.
ip route add <network> via <router> src <preferred interface address>
Of course you could more easily make this public IP the primary address on the interface and the private IP secondary...
There are actually a few ways to skin this cat.
-d
Quoted 27 lines · Nathan Neulinger
Is there any way to block use of an interface for outbound connections?
I have a host who's primary outbound interface is on a private network (using a private address block for our backbone). Unfortunately, this means that most applications (those not providing an option to select bind address) will bind to this private-net address when establishing outbound connections or sending udp packets.
The host has another address which is a publically accessible ip, but it's not the default route interface.
Is there any way to hide this interface on the host for ALL outbound connections without modifying all applications/app invocations? Or some way of overriding the mechanism for selection of default interface.
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: [email protected]
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems Programming Fax: (573) 341-4216
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 1 line
:>
I may have the information you need and I may choose only HTML. It's up to you.
Use iproute2.
ip route add <network> via <router> src <preferred interface address>
Of course you could more easily make this public IP the primary address on the interface and the private IP secondary...
There are actually a few ways to skin this cat.
-d
Quoted 27 lines · Nathan Neulinger
Is there any way to block use of an interface for outbound connections?
I have a host who's primary outbound interface is on a private network (using a private address block for our backbone). Unfortunately, this means that most applications (those not providing an option to select bind address) will bind to this private-net address when establishing outbound connections or sending udp packets.
The host has another address which is a publically accessible ip, but it's not the default route interface.
Is there any way to hide this interface on the host for ALL outbound connections without modifying all applications/app invocations? Or some way of overriding the mechanism for selection of default interface.
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: [email protected]
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems Programming Fax: (573) 341-4216
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 1 line
:>
I may have the information you need and I may choose only HTML. It's up to you.