On 8/1/2014 8:28 μμ, Les Mikesell wrote:
> The concept doesn't even make sense for TCP connections where the
> stack requires acks and sequencing. Are you trying to bridge to a
> capture device or something?
Thank you all for your enlightening feedback, which helped me better
understand my situ
On Wed, Jan 8, 2014 at 1:34 PM, Brian Miller wrote:
>
>> that doesn't make any sense.
>>
>> a SYN packet comes in, is forwarded to serverA and serverB
>>
>> both servers reply with an 'ack' man, is the client tcp stack going
>> to be confused!
>
>
> He didn't say anything about both servers r
On Wed, 2014-01-08 at 11:23 -0800, John R Pierce wrote:
> that doesn't make any sense.
>
> a SYN packet comes in, is forwarded to serverA and serverB
>
> both servers reply with an 'ack' man, is the client tcp stack going
> to be confused!
He didn't say anything about both servers replyi
On 1/8/2014 5:02 AM, Nikolaos Milas wrote:
> Actually, I don't want load balancing; I want incoming http traffic (to
> port 8080) to be forwarded to*ALL* defined target IP addresses.
that doesn't make any sense.
a SYN packet comes in, is forwarded to serverA and serverB
both servers reply with
On 01/08/2014 11:32 AM, Darr247 wrote:
> On 2014-01-08 8:02 AM, Nikolaos Milas wrote:
>> Actually, I don't want load balancing; I want incoming http traffic
>> (to port 8080) to be forwarded to *ALL* defined target IP addresses.
> Sometimes the correct answer is, "you can't do that." :)
>
> You ca
On Wed, Jan 8, 2014 at 11:50 AM, Joseph Spenner wrote:
>
>> Actually, I don't want load balancing; I want incoming http traffic
>> (to port 8080) to be forwarded to *ALL* defined target IP addresses.
>>
>
> What is the goal (other than forward 1 request to 2 servers)?
> It would kinda be a mess, s
- "Nikolaos Milas" escreveu:
> De: "Nikolaos Milas"
> Para: "CentOS mailing list"
> Enviadas: Quarta-feira, 8 de Janeiro de 2014 11:02:48 (GMT-0300) Auto-Detected
> Assunto: Re: [CentOS] Forward http traffic
>
> On 8/1/2014 11:54 πμ, Anton
On 2014-01-08 8:02 AM, Nikolaos Milas wrote:
> Actually, I don't want load balancing; I want incoming http traffic
> (to port 8080) to be forwarded to *ALL* defined target IP addresses.
Sometimes the correct answer is, "you can't do that." :)
You can talk TO port 80 on all the defined target IP
From: Nikolaos Milas
> Actually, I don't want load balancing; I want incoming http traffic (to
> port 8080) to be forwarded to *ALL* defined target IP addresses.
Could you describe the traffic exchange you expect...?
1. http request to 8080.
2. request is forwarded to n servers on 80.
3. n serv
- "Nikolaos Milas" escreveu:
> De: "Nikolaos Milas"
> Para: "CentOS mailing list"
> Enviadas: Quarta-feira, 8 de Janeiro de 2014 11:02:48 (GMT-0300) Auto-Detected
> Assunto: Re: [CentOS] Forward http traffic
>
> On 8/1/2014 11:54 πμ, Anton
On 8/1/2014 11:54 πμ, Antonio da Silva Martins Junior wrote:
> Well, I had only used with a "range". Maybe you can take a look on a
> software load-balancer, like haproxy, or use something like nginx. Then
> forward to the load-balancer instead to the servers.
Thanks,
Actually, I don't want load
- "Nikolaos Milas" escreveu:
> De: "Nikolaos Milas"
> Para: "CentOS mailing list"
> Enviadas: Quarta-feira, 8 de Janeiro de 2014 6:43:16 (GMT-0300) Auto-Detected
> Assunto: Re: [CentOS] Forward http traffic
>
> On 7/1/2014 6:19 μμ, Antonio
On 7/1/2014 6:19 μμ, Antonio da Silva Martins Junior wrote:
> If you put it that way only xxx will receive packets, to balance betwin
> both of them
> you will need this:
>
> -A PREROUTING -s 10.250.250.0/24 -p tcp -m tcp --dport 8080 -j DNAT
> --to-destination xxx.xxx.xxx.xxx-yyy.yyy.yyy.yyy
- "Nikolaos Milas" escreveu:
> De: "Nikolaos Milas"
> Para: centos@centos.org
> Enviadas: Terça-feira, 7 de Janeiro de 2014 10:28:33 (GMT-0300) Auto-Detected
> Assunto: [CentOS] Forward http traffic
>
> Hello,
>
> On CentOS 6.5 x86_64 I
Am 07.01.2014 um 15:01 schrieb Vipul Agarwal :
> On Tue, Jan 7, 2014 at 12:28 PM, Nikolaos Milas wrote:
>
>> Hello,
>>
>> On CentOS 6.5 x86_64 I have (/etc/sysconfig/iptables):
>>
>> *filter
>> :INPUT ACCEPT [0:0]
>> :FORWARD ACCEPT [0:0]
>> :OUTPUT ACCEPT [0:0]
>> :RH-Firewall-1-INPUT - [0:0]
On Tue, Jan 7, 2014 at 12:28 PM, Nikolaos Milas wrote:
> Hello,
>
> On CentOS 6.5 x86_64 I have (/etc/sysconfig/iptables):
>
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> :RH-Firewall-1-INPUT - [0:0]
> -A INPUT -j RH-Firewall-1-INPUT
> -A FORWARD -j RH-Firewall-
Hello,
On CentOS 6.5 x86_64 I have (/etc/sysconfig/iptables):
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp
17 matches
Mail list logo