RE: Sending packets through different interfaces and with different IPs to the same destination

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Assuming this is a lab environment, and all you want to do is check
performance, your easiest solution is not iptables related.
You can run your tests in two different IP subnets, one for the wired and
one for the wireless.
Optimally, your server would have two physical NICs for a clean test.
Even if it doesn't, you can configure alias addresses on a single NIC on the
server.

> -----Original Message-----
> From: netfilter-owner@xxxxxxxxxxxxxxx [mailto:netfilter-
> owner@xxxxxxxxxxxxxxx] On Behalf Of Javier G?lvez Guerrero
> Sent: Monday, December 01, 2008 11:38 AM
> To: netfilter@xxxxxxxxxxxxxxx
> Subject: Re: Sending packets through different interfaces and with
> different IPs to the same destination
> 
> Any idea about this?
> 
> Any help would be much appreciated. Thanks
> Javi
> 
> 
> 2008/11/28 Javier Gálvez Guerrero <javier.galvez.guerrero@xxxxxxxxx>:
> > Hi all,
> >
> > I want to monitor the quality of two different interfaces on a
> > client-server architecture. Let the interfaces be a wired ethernet
> > (eth0) and a wireless adapter (ath0). I want to use IPERF to get
> > performance statistics from these two interfaces. In the server I
> > start two different IPERF processes with two different ports (60301
> > for ath0 connections and 60302 for eth0 connections) listening to the
> > client to send dummy packets in order to get statistics.
> >
> > In the client side I have configured interface ath0 with IP x.x.x.178
> > and eth0 with IP x.x.x.179 and I want the IPERF process sending
> > packets to server port 60301 (this is an argument for IPERF) sends
> > them through the ath0 interface with IP 178 and IPERF process sending
> > packets to server port 60302 does it through the eth0 interface with
> > IP 179, just as they are configured. Then the server receives these
> > packets and process them properly (acknowledging them through the
> > correct client interface and IP). It could be seen as a sort of
> > interface load balancing, but all load balancing examples I've found
> > on the Internet are targeted to router load balancing, and that's not
> > what I want.
> >
> > I've been reading some iptables documentation through the official
> > site and other similar cases found googling and I've tried some
> > configurations with IPTABLES and IP ROUTE (I have used SNAT, TOS and
> > MARK) in order to get this working but everything I've tried hasn't
> > worked. Always some links fail to get the proper IP or MAC and the
> > configuration becomes unstable after a while, working correctly once
> > and the next time wrong.
> >
> > I would like someone to help me with any piece of advice, idea or
> > similar experience reporting, then I can make this work as desired.
> > Any help would be much appreciated.
> >
> >
> > Regards,
> > Javi
> >
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux