Unruh wrote:
> Matt Kowalczyk <(E-Mail Removed)> writes:
>
>
>>Captain Dondo wrote:
>>
>>>On Wed, 15 Mar 2006 12:10:37 -0800, Matt Kowalczyk wrote:
>>>
>>>
>>>
>>>>eth0 and ath0 are both connected to different routers. Each router is then
>>>>connected to the internet.
>>>
>>>
>>>Are the routers connected to the same ISP? Or 2 different ISPs?
>>>
>
>
>>Different.
>
>
>>>>Your assumptions are correct. I would want to accomplish something like this:
>>>>All my web traffic, ssh traffic, etc go through eth0 and everything else
>>>>(bittorrent for example) go through ath0. I will look into traffic shaping to
>
>
> What is web traffic as opposed to "everything else"? How is the system
> supposed to know that packet x contains "web traffic" rather than
> "everything else"?
>
By the destination port. web traffic would be 80, ssh would be 22, etc. If I
make a request to
http://www.google.com:80 I would want eth0 to take that
request. However, if I am using bittorrent which uses ports 6881 for example, I
would want ath0 to handle the traffic.
>
>
>>>>see if I can understad how it will solve my problem.
>>>
>>>
>>>I'm not sure if you couldn't achieve something like that with iptables....
>>> It's been a few years, but ISTR doing something similar to route specific
>>>ports out different interfaces.... Worth looking into as well....
>>>
>>>
>
>
>>Thanks for the additional resource.
>
>
> The newest routing software (ip) I believe can do source port based
> routing, but I have never done so.
>
Is that what I need to setup to accomplish my goals?