Sure, I checked the "protocol = udp" option many, many times. For what I know now is that I tried to configure a udp-based program with Piranha for a lot of times, but it did not work, while at the s
I find that rather surprising, considering one of the documented use cases for Piranha is to load balance DNS requests! Did you specify "protocol = udp" in the configuration? Graeme _________________
Hi, all It turned out that the UDP service configured with the nice-looking Piranha is not working! OMG!!! Simon's post inspired me, so I reconfigured UDP-based virtual service with ipvsadm in a cons
No, I don't think it is too old for the features you are using to work. _______________________________________________ Please read the documentation before posting - it's available at: http://www.li
Hi, Simon Since you have mentioned kernel version here, I checked about that and I'm running 2.6.18-238.19.1.el5.centos.plus, is that a bit too old? Wang _____________________________________________
Now I'm testing a trivial UDP-based program with LVS, just a few bytes in the packet. Wireshark on the director shows the size of UDP packet is 520 bytes, no overly large udp packet size message, and
Nope. There's no iptables ruleset running there, and I think we do not need to do extra iptables work to let those packets through, right? I even disabled firewall and SELinux, but no luck. Wang ____
Hi Roger, if you are seeing that problem then I suggest turning off both GRO and LRO on the interface on the director that receives the packets. e.g. generic-receive-offload: on large-receive-offload
Hi Wang, I have had similar problems where the director thinks the packet size is larger than mtu of the real server and sends back this message. Do you see anything in wireshark to indicate this. Ov
I assume you have an iptables ruleset running there. Is there a hole in it which lets those packets through? Graeme _______________________________________________ Please read the documentation befor
Yes, I tried to make my application listen to real IP / virtual IP / INADDR_ANY, not working. But I think the problem isn't that. As I mentioned in the original post, the LVS router seemed not delive
Sure, I've set up the UDP service. By the way, I'm using Piranha on CentOS 5 to manage the LVS configuration, maybe that's the problem? I'll try to manage LVS with other approaches. _________________
Hi, I think you need to set your application on the real servers to listen to the udp port on all ip's or at least the real ip and then it needs to respond to the client on the vip. Roger. __________
Hi Wang, there shouldn't be anything particularly special about UDP. Do you have a UDP (-u) virtual service configured as well as the original TCP (-t) virtual service? ______________________________
Hi, all I've set up LVS with DR mode for Apache, it worked OK. Then I set up another Virtual Service for an UDP based program on the same boxes, but it won't work. Running Wireshark on the director s