similar to: [PATCH 1/4] xen/netback: shutdown the ring if it contains garbage.

Tune xen_netbk_count_requests to not touch working array beyond limit, so that we can make working array size constant. Signed-off-by: Wei Liu <wei.liu2@citrix.com> --- drivers/net/xen-netback/netback.c | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c index

VM traffic is already limited by a throughput limit, but there is no control over the maximum packet per second (PPS). In DDOS attack the major issue is rather PPS than throughput. With provider offering more bandwidth to VMs, it becames easy to coordinate a massive attack using VMs. Example: 100Mbits ~ 200kpps using 64B packets. This patch provides a new option to limit VMs maximum packets per

We''ve been hitting the following issue on a variety of hosts and recent Xen/dom0 version combinations. Here''s an excerpt from our latest: Xen: 4.1.4 (xenbits @ 23432) Dom0: 3.7.1-x86_64 BUG: unable to handle kernel NULL pointer dereference at 000000000000001c IP: [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ebt_comment

Hello we see the same with debian Wheezy. Apr 16 16:02:25 hypervisor3 kernel: [2441115.664216] vif vif-17-0: vif17.0: Frag is bigger than frame. Apr 16 16:02:25 hypervisor3 kernel: [2441115.664267] vif vif-17-0: vif17.0: fatal error; disabling device Apr 16 16:02:25 hypervisor3 kernel: [2441115.675667] BUG: unable to handle kernel NULL pointer dereference at 00000000000008b8 Apr 16 16:02:25

Netback and netfront only use one event channel to do tx / rx notification. This may cause unnecessary wake-up of process routines. This patch adds a new feature called feautre-split-event-channel to netback, enabling it to handle Tx and Rx event separately. Netback will use tx_irq to notify guest for tx completion, rx_irq for rx notification. If frontend doesn''t support this feature,

This patch adds code to handle SKB_GSO_TCPV6 skbs and construct appropriate extra or prefix segments to pass the large packet to the frontend. New xenstore flags, feature-gso-tcpv6 and feature-gso-tcpv6-prefix, are sampled to determine if the frontend is capable of handling such packets. Signed-off-by: Paul Durrant <paul.durrant@citrix.com> Cc: Wei Liu <wei.liu2@citrix.com> Cc: David

time_after_eq() only works if the delta is < MAX_ULONG/2. For a 32bit Dom0, if netfront sends packets at a very low rate, the time between subsequent calls to tx_credit_exceeded() may exceed MAX_ULONG/2 and the test for timer_after_eq() will be incorrect. Credit will not be replenished and the guest may become unable to send packets (e.g., if prior to the long gap, all credit was exhausted).

Hi, First a confession - The box in question is a 1.2.35 box, so this may be solved in a newer version as I know the JB code is all hugely changed, but... It may be worth checking into. Scenario: - IAX outbound call from Asterisk, which rings okay. - Remote end sends ANSWER, which we immediately ACK. - The ANSWER control packet gets put into the JB (that's how I read the code) - The remote

Hi Xen developers, I had some questions regarding XSA39, and I hope you all can answer them. We''ve been rolling out some hosts with the XSA39 patch applied and have come across a problem where a few of our customer DomUs keep hitting the conditions which call netbk_fatal_tx_err(), mostly "Frag is bigger than frame." These specific DomUs hit it repeatedly, between once every

This dependence is undesirable and logically incorrect. It''s undesirable because Xen network protocol should not depend on a OS-specific constant. It''s incorrect because the ring slots required doesn''t correspond to the number of frags a SKB has (consider compound page frags). This patch removes this dependence by correctly counting the ring slots required.

I have this in sip show history for a particular channel marked as dead (should be removed) in sip show channels: 1. TxReqRel INVITE / 102 INVITE 2. Rx SIP/2.0 / 102 INVITE 3. CancelDestroy 4. Rx SIP/2.0 / 102 INVITE 5. CancelDestroy 6. Unhold SIP/2.0 7. Rx SIP/2.0 / 102 INVITE 8. CancelDestroy 9. Unhold SIP/2.0 10. Rx

hallo, i am really confused how nativ briging is working with asterisk, i use a asterisk server as central server and register another asterisk and an iaxcomm client to the server, all three have public ips on the internet. somtimes, when i call from iaxcomm to my asterisk, the calls go peer to peer (i can see it with tcpdump) but sometimes the get routed through the central asterisk server

The code to detect fragments in checksum_setup() was missing for IPv4 and too eager for IPv6. (It transpires that Windows seems to send IPv6 packets with a fragment header even if they are not a fragment - i.e. offset is zero, and M bit is not set). Signed-off-by: Paul Durrant <paul.durrant@citrix.com> Cc: Wei Liu <wei.liu2@citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com>

I'm taking inbound calls on an * server, then transferring them to a second * server where they join a MeetMe conference. If I have 'notransfer=yes' set on the first * server it works fine, but if I allow the transfer (call then shifts to be between the DID provider and the second server), the call is dropped 3-5 minutes later. There is no firewall on my end, and the two

Reported-by: Nikita Borzykh <sample.n@gmail.com> Reported-by: Paul Harvey <stockingpaul@hotmail.com> Suggested-by: Ian Campbell <Ian.Campbell@citrix.com> Signed-off-by: Matt Wilson <msw@amazon.com> --- drivers/net/xen-netback/interface.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/net/xen-netback/interface.c

Hi all, i have the following setup PSTN -> routing server (asterisk 1.6.2.11) -> IAX -> callcenter asterisk 1.6.2.9 -> SIP -> agent Does work quit fine - then agent does have the abibility to transfer a call to a third party - the agent can initiate the transfer over a web interface - it does generate a asterisk manager atxfer request... So agent does initiate transfer - call

On Thu, Oct 20, 2016 at 01:55:21PM -0400, Jarod Wilson wrote: > hyperv_net: > - set min/max_mtu, per Haiyang, after rndis_filter_device_add > > virtio_net: > - set min/max_mtu > - remove virtnet_change_mtu > vmxnet3: > - set min/max_mtu > > xen-netback: > - min_mtu = 0, max_mtu = 65517 > > xen-netfront: > - min_mtu = 0, max_mtu = 65535 > >

The Asterisk Development Team has announced the release of Asterisk 1.6.1.18. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.6.1.18 resolves several issues reported by the community, and would have not been possible without your participation. Thank you! The following are a few of the issues resolved by

The Asterisk Development Team has announced the release of Asterisk 1.6.1.18. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.6.1.18 resolves several issues reported by the community, and would have not been possible without your participation. Thank you! The following are a few of the issues resolved by

The Asterisk Development Team has announced the release of Asterisk 1.6.2.6. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.6.2.6 resolves several issues reported by the community, and would have not been possible without your participation. Thank you! The following are a few of the issues resolved by community