Sponsored Content
Special Forums IP Networking Route packets over specified interface Post 302859289 by Subbeh on Wednesday 2nd of October 2013 05:13:25 PM
Old 10-02-2013
Route packets over specified interface

Hi,

I'm quite new to unix networking and ip tables. I'm running a debian (htpc) server with two NIC's; eth0 and wlan0.

I'm trying to set it up in a way that eth0 is the default interface for internet, but some processes should run through wlan0.

For example, I'm using eth0 for downloads and other bandwidth intensive processes but I want things like Spotify to run through wlan0.
For Spotify, this should be a rule in iptables:
Quote:
The following IP ranges should be open on port 4070: 78.31.8.0/21, 193.182.8.0/21.
What's the best way to approach this?

Thanks

Last edited by Subbeh; 10-02-2013 at 06:19 PM..
 

9 More Discussions You Might Find Interesting

1. Solaris

Had to bounce interface to add network route

Hi All, yesterday I was trying to add a network route to my solaris 8 host using 'route add'. Everytime I tried, I kept getting the response 'network is unreachable'. I was trying all kinds of different methods, however I eventually got it to work after bouncing the interface that I was... (2 Replies)
Discussion started by: badoshi
2 Replies

2. Solaris

Route new network interface Solaris 8

Hi there, I'm trying to configure an additional network interface on Solaris 8 (eri0). The interface has been activated, but all the frames are still routed to the current default interface (ce0) I've tried following command (with various syntaxes...) unsuccessfully so far: # route add... (2 Replies)
Discussion started by: sreiniche
2 Replies

3. Solaris

Network interface down after adding static route

Please , I have a problem I have add a statis route on Solaris 10, but after this, the network interface of Server was Offline. The system is in cluster mode (3.2) route add -net 10.10.1.128 -netmask 255.255.255.128 10.10.1.51 ------------------- lo0:... (1 Reply)
Discussion started by: Ruggero
1 Replies

4. Solaris

Command line Interface or GUI Interface not shown on solaris

Dear all, I am a newbie in solaris and I need your advice. I have a Solaris version 5.9 installed on Sunfire V240. I am able to ssh the machine from putty remotely. My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies

5. SCO

Change SCO - GUI or Desktop interface to DOS based interface

Hi all I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface? If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies

6. Solaris

route and interface configuration in solaris

Hi, Every time when i boot my system i have to manually issue the following commands. ifconfig elxl0 plumb 192.168.200.129 netmask 255.255.255.0 up route add default 192.168.200.1 I need some help so that it should be configured permanently and i wouldn't have to manually issue... (2 Replies)
Discussion started by: malikshahid85
2 Replies

7. IP Networking

How to route all incoming packets from one virtual interface?

Hello, I'm trying to route all packets arriving at a particular interface by entering the same interface the virtual interface eth1: 2 and now everything is routed by default gw configured on eth1. eth1 Link encap:Ethernet HWaddr 0a:0e:64:18:52:72 inet addr:192.168.10.15 eth1:2 ... (1 Reply)
Discussion started by: faka
1 Replies

8. IP Networking

How to route packets back to incoming interface?

Hi folks, I have a debian server running an Apache daemon on the eth0 interface. Now from time to time the server has to open an openvpn connection (tun0) to other networks to get some data from there. During this period the Apache is no longer reachable under it's IP address on eth0 because all... (6 Replies)
Discussion started by: flyingwalrus
6 Replies

9. IP Networking

Packet going out of wrong interface due to OS automatically added cache route with lower metric

RHEL 7.0, IPV6 Scenario: I have routed specific network using network scripts. 1. "ip -6 route show" shows that route has been added. ( with metric 1024) 2. Ping of the specific IP through that route is successful. 3. Now after few days, for some reason, we see that cache route appears for... (3 Replies)
Discussion started by: msr1981
3 Replies
IFSYSCTL(5)						       Network configuration						       IFSYSCTL(5)

NAME
ifsysctl[-<interface name>] - per network interface sysctl settings SYNOPSIS
/etc/sysconfig/network/ifsysctl /etc/sysconfig/network/ifsysctl-<interface name> DESCRIPTION
These files are intended to contain sysctl settings, that should be applied when a network interface is created. This are usually interface specific settings, like: net.ipv6.conf.eth0.use_tempaddr = 1 or net.ipv4.conf.eth0.rp_filter = 0 The settings are applied by the /etc/sysconfig/network/scripts/ifup-sysctl script executed via /etc/udev/rules.d/77-network.rules rule (see udev(7)), after the creation and after the rename of the interface name to its persistent name (when applicable), but before the ifup <interface name> -o hotplug may be executed to configure the interface. The settings are not applied by default when the NetworkManager is active (NETWORKMANAGER=yes), except when the IFSYSCTL_NETWORKMANAGER=yes variable is set in the /etc/sysconfig/network/config file. Settings from the ifsysctl- file are applied every time an interface has been created. Settings from the ifsysctl-interface name file are applied when the interface with the corresponding interface name has been created. SYNTAX
The sysctl(8) utility is required to apply the settings. It supports two separator characters for sysctl keywords: a "." in default format and a "/" in the alternate format. Therefore the syntax is basically same to the /etc/sysctl.conf file. Interface names may contain a ".". In the default sysctl format using a "." as separator, that is any "." in the interface name of the key- word, has to be replaced with a "/". In the alternate sysctl format with "/" as separator, normal interface names can be used. Optionally, the ifsysctl files may contain also the $INTERFACE and the $SYSCTL_IF variables, that are automatically replaced with the cur- rent interface name usable in the alternate format and with the sysctl-quoted interface name for the default format, before the settings are passed to the sysctl utility. Note also, that settings with variables in the ifsysctl (without the -<interface name> suffix), will be applied for every interface! Further, files with variables are not compatible to the /etc/sysctl.conf file. EXAMPLES
Settings for "eth0" and "eth0.1" interfaces # using "." as separator: net.ipv6.conf.eth0.use_tempaddr = 1 net.ipv6.conf.eth0/1.use_tempaddr = 1 # using "/" as separator: net/ipv6/conf/eth0/use_tempaddr = 1 net/ipv6/conf/eth0.0/use_tempaddr = 1 Settings with variables: # using "." as separator: net.ipv6.conf.$SYSCTL_IF.use_tempaddr = 1 # using "/" as separator: net/ipv6/conf/$INTERFACE/use_tempaddr = 1 To test your ifsysctl-eth0 or ifsysctl file, use: /etc/sysconfig/network/scripts/ifup-sysctl eth0 -o debug BUGS
Please report bugs at <https://bugzilla.novell.com/> AUTHOR
Marius Tomaschewski <mt@suse.de> SEE ALSO
ifup(8) ifcfg(5) sysctl(8) sysconfig December 2009 IFSYSCTL(5)
All times are GMT -4. The time now is 06:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy