<div>2009/7/15 Harald Welte <span dir="ltr"><<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br></div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="h5">On Wed, Jul 15, 2009 at 11:06:48AM +0200, Eric Cathelinaud wrote:<br>> 2009/7/10 Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>><br>><br>> > On Fri, Jul 10, 2009 at 12:29:47PM +0200, Eric Cathelinaud wrote:<br>
> > > Well i still have sometimes this error message. I have it when I attach a<br>> > > mobile on the network.<br>> > > I saw 2 "unknow" packets comes from the Remote Network to the Remote User<br>
> > > during the attach process. Their size are quite small.<br>> > > I join in attached file a screen of my results.<br>> ><br>> > it would help if you can put the pcap file (with at least one good and one<br>
> > 'bad' packet) somewhere online or even send it to the list (if its small<br>> > and you only select a couple of packets, you can attach it).<br>> ><br>> > --<br>> > - Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>><br>
> > <a href="http://laforge.gnumonks.org/" target="_blank">http://laforge.gnumonks.org/</a><br>> ><br>> > ============================================================================<br>> > "Privacy in residential applications is a desirable marketing option."<br>
> > (ETSI EN 300 175-7 Ch. A6)<br>> ><br>><br>><br>> In the attached file there are 5 malformed packets and 2 unknow packets.<br><br></div></div>just to make it clear: this pcap was generated using bsc_hack's pcap option,<br>
correct? it seems like sometimes we write truncated packets to that file.<br><br>There is a different method, using mISDN's debug tool (see<br><a href="http://www.misdn.org/index.php/Debugtool" target="_blank">http://www.misdn.org/index.php/Debugtool</a>). I think if somebody can confirm<br>
this method works, i.e. use mISDNdebugtool to write a 'dumpfile' and then open<br>that with wireshark, then we can actually remove the pcap code from OpenBSC<br>altogether.<br><br>Would you mind trying that method and report if you still see broken/unknown<br>
packets?<br><br>Thanks!<br><font color="#888888">--<br></font>
<div>
<div></div>
<div class="h5">- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/" target="_blank">http://laforge.gnumonks.org/</a><br>============================================================================<br>
"Privacy in residential applications is a desirable marketing option."<br> (ETSI EN 300 175-7 Ch. A6)<br></div></div></blockquote></div>
<div><br> </div>
<div>
<div>Ok i will try it and tell u ;-)</div>
<div> </div>
<div>Thanks<br><br>Eric Cathelinaud</div></div>