search for: txflag

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 t...

...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 t...

...xoks" : Channel(s) are signalled using FXO Koolstart protocol. # "sf" : Channel(s) are signalled using in-band single freq tone. # Syntax as follows: # channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag> # rxfreq is rx tone freq in hz, rxbw is rx notch (and decode) # bandwith in hz (typically 10.0), rxflag is either 'normal' or # 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone # level in dbm, txflag is either...

...tart protocol. # "fxoks" : Channel(s) are signalled using FXO Koolstart protocol. # "sf" : Channel(s) are signalled using in-band single freq tone. # Syntax as follows: # channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag> # rxfreq is rx tone freq in hz, rxbw is rx notch (and decode) # bandwith in hz (typically 10.0), rxflag is either 'normal' or # 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone # level in dbm, txflag is either 'normal' or 'inverted'. Set # r...

...fxoks" : Channel(s) are signalled using FXO Koolstart protocol. # "sf" : Channel(s) are signalled using in-band single freq tone. # Syntax as follows: # channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag> # rxfreq is rx tone freq in hz, rxbw is rx notch (and decode) # bandwith in hz (typically 10.0), rxflag is either 'normal' or # 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone # level in dbm, txflag is either &...

...ks" : Channel(s) are signalled using FXO Koolstart protocol. # "sf" : Channel(s) are signalled using in-band single freq tone. # Syntax as follows: # channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag> # rxfreq is rx tone freq in hz, rxbw is rx notch (and decode) # bandwith in hz (typically 10.0), rxflag is either 'normal' or # 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone # level in dbm, txflag is eith...

...ndstart protocol. # "fxoks" : Channel(s) are signalled using FXO Koolstart protocol. # "sf" : Channel(s) are signalled using in-band single freq tone. # Syntax as follows: # channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag> # rxfreq is rx tone freq in hz, rxbw is rx notch (and decode) # bandwith in hz (typically 10.0), rxflag is either 'normal' or # 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone # level in dbm, txflag is either 'normal' or 'inverted'. Set # rxfr...

...>> 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...

...>> 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...

...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 genera...

...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 genera...

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 > > functi...

...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 > > functi...

...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 coul...

...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 coul...

...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 p...

...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 p...