I meant to say LVS/DR. Not LVS/Nat or LVS/Tun. The RealServers/Back-End machines reply directly back to the client.
As I said, works fine with 4.7. I'm sure it's something 5.0-current specific. I'm currently processing 500K emails per day with this setup. :)
Hmmm, I think I need to run tcpdump on a the client too. I'm only looking at the traffic between the LVS machine and the Real Server.
Thanks
Ken
On Thursday, February 13, 2003, at 06:35 PM, Terry Lambert wrote:
Ken McKittrick wrote:I've got a FreeBSD5.0-R machine that doesn't work with Linux Virtual
Server. This is for SMTP and WWW services.
I'm using LVS-Direct Routing. The LVS machine has the 66.218.0.54 Real
IP and 66.218.0.58 and 66.218.0.59 as Virtual IP's. The FreeBSD machine
has 66.218.0.28 and a Real IP on fxp0 and 66.218.0.58/59 on lo0 with
-arp.
Running tcpdump host 66.218.0.54 I can see the requests come in, but
nothing is going back out. When you telnet into port 25 the connection
times out.
I've running Linux LVS with FreeBSD4-STABLE SMTP machines in production
so I'm confident that it's a FreeBSD 5.0 issue.
I'm guessing this is some LVS specific terminology that someone made up because they did not read the literature before writing their code? Is this the DSR or "Direct Server Return" configuration? If so, the answer is that you need to specify the LVS as the default return route, and not answer locally, even though it appears to be a local net. This can be handled using explicit routes for the alias IP addresses. You *did* put the alias IP addresses on the loopback interface, and turn of ARP'ing for them, right? If you need more help, probably the correct place to ask is not the -current list, but the -net list (after you replace the terminology "LVS-Direct" with it's real name; I'm only guessing you meant DSR here). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
