Bug 466807 - google fork to support ipv6, for fedora 11
Summary: google fork to support ipv6, for fedora 11
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ipvsadm
Version: rawhide
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL: http://www.linuxvirtualserver.org/sof...
Whiteboard:
: 466805 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-13 18:17 UTC by acount closed by user
Modified: 2008-12-24 15:31 UTC (History)
2 users (show)

Fixed In Version: 1.25-1
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-24 15:31:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description acount closed by user 2008-10-13 18:17:57 UTC 
I think that the kernel bits are alredy included into 2.6.27

-thanks-
Comment 1 acount closed by user 2008-10-13 18:20:03 UTC 
*** Bug 466805 has been marked as a duplicate of this bug. ***
Comment 2 John Poelstra 2008-10-17 22:51:23 UTC 
What is bug or RFE here?  2.6.27 is already in rawhide.
Comment 3 acount closed by user 2008-10-18 22:49:00 UTC 
RFE , ipvsadm needs the google hacks to handle ipv6 (kernel side included into 2.6.27 or .28-git) : http://sixpak.org/vince/google/ipvsadm/?C=M;O=D
Comment 4 acount closed by user 2008-11-09 12:02:36 UTC 
IPv6 load balancing: http://kb.linuxvirtualserver.org/wiki/IPv6_load_balancing
Comment 5 Matthias Saou 2008-12-22 18:51:23 UTC 
http://www.linuxvirtualserver.org/software/ipvs.html

From what can be read now, 1.25 has been released by upstream now, but requires a kernel more recent than the one currently in devel. I'll prepare the updated package in CVS nevertheless, but will build and push later.
Comment 6 Matthias Saou 2008-12-24 15:31:27 UTC 
I've tested 1.25 on my Fedora 10 system and it worked fine (I only tested IPv4), so I'm pushing the build to devel as it seems like it won't break anything even until the right kernel gets in.
Note You need to log in before you can comment on or make changes to this bug.