|
Still do direct routing. You only need to use the tunl interfaces to get the
kernel to answer that IP address. Make sure you turn arp off with -arp.
I'm doing direct routing now. All my virtual servers have VIPs as their
ethernet aliases; all my real servers have VIPs as their tunnel aliases.
Best of luck --
Ted
P.S.
I'm going to post that doc soon on lvs-users
----- Original Message -----
From: Stephen D. Williams <sdw@xxxxxxx>
To: Ted Pavlic <tpavlic@xxxxxxxxxxx>
Cc: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Monday, September 13, 1999 12:01 AM
Subject: Re: Emergency problem with extra ARP's, 2.2.12/13Pre6, DR mode
> Can I still do direct routing or do I have to actually use tunneling with
the
> tun devices?
>
>
> Ted Pavlic wrote:
>
> > Try installing the tunnel device with a VIP and doing a -noarp on that.
I
> > believe there's documentation saying to do this... 2.2.x kernels really
> > added some odd arping.
>
> If you run accross this reference, I'd appreciate a pointer. I thought I
read
> everything.
>
> Thanks!
> sdw
>
> >
> >
> > Things work fine for me -- install the VIP aliases not on your loopback
> > device and not on your eth device, but on tunnel devices (and their
aliases)
> > (even if you're not doing tunnelling -- you just need a different
device...
> > tunl0 or ppp0... something besides lo or eth)
> >
> > All the best --
> > Ted
> >
> > ----- Original Message -----
> > From: Stephen D. WIlliams <sdw@xxxxxxx>
> > To: Jerome Richard <jrichard@xxxxxxxxxxxxxx>;
> > <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>; <linux-kernel@xxxxxxxxxxxxxxxx>
> > Sent: Sunday, September 12, 1999 10:13 PM
> > Subject: Re: Emergency problem with extra ARP's, 2.2.12/13Pre6, DR mode
> >
> > > This apparently doesn't work because the check is done for the
Ethernet
> > device (rather than
> > > loopback in this case) since that is where the request came from.
> > >
> > > We need a check for the flag on the device that corresponds to the IP
> > address to determine
> > > if it's address is 'public'.
> > >
> > > sdw
> > >
> > > "Stephen D. WIlliams" wrote:
> > >
> > > > After searching through the kernel, finding IFF_NOARP, tracing it
out to
> > the device flags
> > > > interface and then finally seeing '-arp' in the ifconfig man page,
I'm
> > trying that to see
> > > > if it works.
> > > >
> > > > Is there some problem with using this (like it doesn't work)?
> > > >
> > > > Thanks!
> > > > sdw
> > > >
> > > > "Stephen D. WIlliams" wrote:
> > > >
> > > > > Jerome Richard wrote:
> > > > >
> > > > > > "Stephen D. WIlliams" wrote:
> > > > > >
> > > > > > > ...
> > > > > > >
> > > > > > > Kernel 2.2.13pre6 from Alan's directory on ftp.funet.fi with
the
> > > > > > > ipvs-0.8.3-2.2.12 patch applied... (2.2.12 crashed every 5
min
> > for some
> > > > > > > reason...)
> > > > > > >
> > > > > > > To test I can put a permanent entry ARP entry in the test
system
> > but I Really
> > > > > > > can't do that with the router, especially since I will want to
> > failover.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > sdw
> > > > > >
> > > > > > What kind of hardware do you have for the LAN ? swith or hub ?
> > Because some kind of
> > > > > > switchs have an ARP caching feature (Like Cabletron 6000). In
this
> > case, you must
> > > > > > disable ARP caching on all port of the swicth using VIP
(Director
> > and servers).
> > > > > >
> > > > > > Bye,
> > > > > > jerome.
> > > > >
> > > > > Allied Tellisyn 8124xl managed switch... There is nothing in it's
> > configuration about
> > > > > the ARP level, only MAC address handling.
> > > > >
> > > > > Also, watching the output from arpwatch I believe that the Linux
boxes
> > really are
> > > > > sending ARP replies when they shouldn't.
> > > > >
> > > > > If anyone with experience tracking that down in the kernel could
help
> > I would
> > > > > appreciate it!
> > > > >
> > > > > Thanks!
> > > > > sdw
> > > > >
> > > > > --
> > > > > OptimaLogic - Finding Optimal Solutions
> > Web/Crypto/OO/Unix/Comm/Video/DBMS
> > > > > sdw@xxxxxxx Stephen D. Williams Senior Consultant/Architect
> > http://sdw.st
> > > > > 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W
703-995-0407Fax
> > 5Jan1999
> > > >
> > > > --
> > > > OptimaLogic - Finding Optimal Solutions
> > Web/Crypto/OO/Unix/Comm/Video/DBMS
> > > > sdw@xxxxxxx Stephen D. Williams Senior Consultant/Architect
> > http://sdw.st
> > > > 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W
703-995-0407Fax
> > 5Jan1999
> > > >
> > >
> ----------------------------------------------------------------------
> > > > LinuxVirtualServer.org mailing list -
lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > > > To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
> > > > For additional commands, e-mail:
lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
> > >
> > > --
> > > OptimaLogic - Finding Optimal Solutions
> > Web/Crypto/OO/Unix/Comm/Video/DBMS
> > > sdw@xxxxxxx Stephen D. Williams Senior Consultant/Architect
> > http://sdw.st
> > > 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W 703-995-0407Fax
> > 5Jan1999
> > >
> > >
> > >
> > >
> > > ----------------------------------------------------------------------
> > > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > > To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
> > > For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
> > >
> > >
> >
> > ----------------------------------------------------------------------
> > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
> > For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
>
> --
> OptimaLogic - Finding Optimal Solutions
Web/Crypto/OO/Unix/Comm/Video/DBMS
> sdw@xxxxxxx Stephen D. Williams Senior Consultant/Architect
http://sdw.st
> 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W 703-995-0407Fax
5Jan1999
>
>
>
----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
|
