search for: txflags

On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > On Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > > On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > > > If the IPv6 fragment id has not been set and we perform > > > fragmentation due to UFO, select a new fragment id. > > > When we store the fragment id into skb_shinfo,

On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > On Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > > On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > > > If the IPv6 fragment id has not been set and we perform > > > fragmentation due to UFO, select a new fragment id. > > > When we store the fragment id into skb_shinfo,

...of tx flags. > >> Maybe ip6_frag_id == 0 should mean "not set". > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > move into the skb_shared_info area. > > That's what I originally wanted to do, but had to move and grow txflags thus > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > from the protocol perspective and could actually be generated by the id generator > functions. This may cause us to...

...of tx flags. > >> Maybe ip6_frag_id == 0 should mean "not set". > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > move into the skb_shared_info area. > > That's what I originally wanted to do, but had to move and grow txflags thus > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > from the protocol perspective and could actually be generated by the id generator > functions. This may cause us to...

After speaking with several people, and even participating in a forum of several other people with echo issues, I thought I'd share what we've done (well actually what our chief R&D engineer, Brett Bourn has done...) First let me say that normal cheapy PC hardware couldn't be made to function with out echo. We tried on both the single port Digium T1 card and the 4 port Digium T1

Em (20:59:21), Asterisk Users Mailing List - Non-Commercial Discussion escreveu: >On Tue, Jun 21, 2005 at 08:09:52PM -0300, Alessandro wrote: >> >> Does Somebody know why no load modules to FXS? I used zaptel-1.0.7 >> version. > >What color are the modules? >Post your /etc/zaptel.conf > >-- >Mike Mike, The color is green, red ans bluw. Link

zaptel compiles fine (make linux26) but when I modprobe ztdummy I get the follow error. [root@localhost zaptel]# modprobe ztdummy Notice: Configuration file is /etc/zaptel.conf line 0: Unable to open master device '/dev/zap/ctl' 1 error(s) detected FATAL: Error running install command for ztdummy System info: Linux localhost.localdomain 2.6.9-5.0.5.ELsmp #1 SMP Thu May 19 19:24:44

Hi all, Does somebody know why no load modules to FXS? I used zaptel-1.0.7 version driver. [root@server1 zaptel-1.0.7]# modprobe wctdm ZT_CHANCONFIG failed on channel 3: Invalid argument (22) Did you forget that FXS interfaces are configured with FXO signalling and that FXO interfaces use FXS signalling? /lib/modules/2.4.21-27.EL/misc/wcfxs.o: post-install wcfxs failed

Hi All I have problem with LIBMFCR2 for once Exchange I using Sangoma card, the firstly. my ssystem run successful with MFCR2, connected to E10 (Acatel Exchange), after that, i move connection connect to EWSD (Siemens), my system don't work. error protocol R2. my system: Asterisk CVS 1.1.X LibMFCR2 pre.005 and unicall-pre.005 this's my setting and my setting wanpipe1.conf

...>> Hmm we seem to be out of tx flags. >> Maybe ip6_frag_id == 0 should mean "not set". > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > move into the skb_shared_info area. That's what I originally wanted to do, but had to move and grow txflags thus skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid from the protocol perspective and could actually be generated by the id generator functions. This may cause us to call the id generation m...

...>> Hmm we seem to be out of tx flags. >> Maybe ip6_frag_id == 0 should mean "not set". > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > move into the skb_shared_info area. That's what I originally wanted to do, but had to move and grow txflags thus skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid from the protocol perspective and could actually be generated by the id generator functions. This may cause us to call the id generation m...

...should mean "not set". > > > > > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > > > move into the skb_shared_info area. > > > > > > That's what I originally wanted to do, but had to move and grow txflags thus > > > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > > > > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > > > from the protocol perspective and could actually be generated by the id generat...

...should mean "not set". > > > > > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > > > move into the skb_shared_info area. > > > > > > That's what I originally wanted to do, but had to move and grow txflags thus > > > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > > > > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > > > from the protocol perspective and could actually be generated by the id generat...

Hi, all I have installed TDM400 with 1 FXS and 1 FXP ports. Now I am goig through documentation on how to configure it. It mentions 3 protocols: Loopstart, Groundstart and Koolstart. Which one do I use? Can someone send me sample zaptel.conf file for Australia? This will save me some time and will be used as a working example. Thanks, Rudolf

...t; Maybe ip6_frag_id == 0 should mean "not set". > > > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > > move into the skb_shared_info area. > > > > That's what I originally wanted to do, but had to move and grow txflags thus > > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > > from the protocol perspective and could actually be generated by the id generator > > functio...

...t; Maybe ip6_frag_id == 0 should mean "not set". > > > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > > move into the skb_shared_info area. > > > > That's what I originally wanted to do, but had to move and grow txflags thus > > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > > from the protocol perspective and could actually be generated by the id generator > > functio...

...gt; > > > > > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > > > > > move into the skb_shared_info area. > > > > > > > > > > That's what I originally wanted to do, but had to move and grow txflags thus > > > > > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > > > > > > > > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > > > > > from the protocol perspective and could...

...gt; > > > > > > > > Maybe that is the best idea. Definitely the ufo_fragid_set bit should > > > > > > move into the skb_shared_info area. > > > > > > > > > > That's what I originally wanted to do, but had to move and grow txflags thus > > > > > skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > > > > > > > > > > I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > > > > > from the protocol perspective and could...

...t; >>>>>>> Maybe that is the best idea. Definitely the ufo_fragid_set bit should > >>>>>>> move into the skb_shared_info area. > >>>>>> > >>>>>> That's what I originally wanted to do, but had to move and grow txflags thus > >>>>>> skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > >>>>>> > >>>>>> I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > >>>>>> from the protocol pe...

...t; >>>>>>> Maybe that is the best idea. Definitely the ufo_fragid_set bit should > >>>>>>> move into the skb_shared_info area. > >>>>>> > >>>>>> That's what I originally wanted to do, but had to move and grow txflags thus > >>>>>> skb_shinfo ended up growing. I wanted to avoid that, so stole an skb flag. > >>>>>> > >>>>>> I considered treating fragid == 0 as unset, but a 0 fragid is perfectly valid > >>>>>> from the protocol pe...