Your message dated Sat, 27 May 2023 05:04:07 +0000
with message-id <[email protected]>
and subject line Bug#1036316: Removed package(s) from unstable
has caused the Debian Bug report #645614,
regarding Fwd: Load Balancing with VRRPd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
645614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645614
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vrrpd
Version : 0.4
I used vrrpd 0.4 to implement redundant network. I have used two
router with two NIC running different instance of vrrp on both the
interface so that virtually it get two router network hidden from
outside world. It worked fine and was able to obtain redundancy with
both master and backup functioning properly.Great !!. I have attached
the .png for the same.
But now, I wanted to move to load balancing part of it... for that i
have created 2 instance of vrrp on each interface so that for one
instance say VRID 100 Router A will be master and for another Instance
say VRID 150 router B act as mast with router A as backup.
Similarly, 2 more instance of VRRP is created on another interface to
hide the internal configuration from external world.
Network Configuration : Server 1 IP : 10.0.0.1 (default set to
10.0.0.100) Server 2 IP : 10.0.0.4 (default set to 10.0.0.150)
Router A at eth0 VRID (10.0.0.2) 100 Master
at eth0 VRID 150 Backup
at eth1 VRID
(20.0.0.2) 200 Master
at eth1 VRID 250 Backup
Router B at eth0 ( IP 10.0.0.3) VRID 100 Backup
at eth0 VRID 150 Master
at eth1 (20.0.0.3) VRID
200 Backup
at eth1 VRID 250 Master
client 1 IP 20.0.0.1 (default set to 20.0.0.200) client 2 IP 20.0.0.4
(default set to 20.0.0.250)
It worked good when am not pinging it from server to client. I mean
for interface ROuter A advertised for VRID 100 and ROuter B advertised
for VRID 150 (checked through wireshark). when i ping from client
20.0.0.4 to 10.0.0.4 according to network 20.0.0.4 send packet to
20.0.0.250(default router) and Router B is master in this case so it
will forward the packet from eth1 to eth0 to 10.0.0.150 and then from
there it should reach to 10.0.0.4.
But strange behavior is found. First of all ping does not work. It
say network out the reach. and when the router B is shut down
according to vrrp router A have following configuration
at eth0- 10.0.0.100 (master)
at eth0-10.0.0.150 (master)
at eth 1-20.0.0.200 (master)
at eth 1-20.0.0.250 (master)
due to this their is ambiguity in assignment of virtual MAC address to
the interface and it set to the corresponding to VRID 100 for eth0 and
VRID 200 for eth1 (original Master) and now it start pinging from
client 20.0.0.4 to server 10.0.0.4
but next time when router B restart it do not change or assign its
Virtual MAC address corresponds to VRID 150 at eth0 and VRID 250 at
eth1 to the two interfaces of router B. and it ping continuously
through router A that should not actually.
Please find the attachments here where in first case normal redundant
network is created and successfully worked. In second and third case
the load balancing is implemented which created ambiguity in
assignment of virtual MAC address and is not working.
I am Using Ubuntu 10.04LTS, kernel 2.6.32-34-generic.
MOHIT VAJPEYEE
TELECOM TECHNOLOGY & MANAGEMENT
IIT DELHI
NEW DELHI-16
INDIA
+91-9650-286457
--- End Message ---
--- Begin Message ---
Version: 1.0-2+rm
Dear submitter,
as the package vrrpd has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1036316
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
