Please forgive me if you receive this message twice. Hello, I have a problem with use of kannel and I begin to get some headaches! Help of anybody will be great! I'am using kannel on an arm processor with this logfile: group = core admin-port = 13000 wapbox-port = 13002 admin-password = bar wdp-interface-name = "*" log-file = "/tmp/kannel.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" #admin-deny-ip = "" #admin-allow-ip = "" #access-log = "access.log" group = wapbox bearerbox-host = localhost log-file = "/tmp/wapbox.log" log-level = 0 syslog-level = none Here are the command lines I have entered: gw/bearerbox gw/wapkannel.conf & gw/wapbox gw/wapkannel.conf & when I try to test it with fakewap (fakewap "http://wap.ugc.fr";) or with WinWap on an other device, Wapbox is suddently killed and I don't understand the reason why. Here are the messages I caught: from fakewap: 2001-07-18 10:14:19 [0] INFO: Timeout while receiving from socket. and from wapbox: 2001-07-18 10:14:08 [10] DEBUG: boxc_sender: sent message 2001-07-18 10:14:10 [9] INFO: Client <127.0.0.1> closed connection 2001-07-18 10:14:10 [10] DEBUG: Thread 10 (gw/bb_boxc.c:boxc_sender) terminates. 2001-07-18 10:14:10 [9] DEBUG: Thread 9 (gw/bb_boxc.c:function) terminates. Wapbox has been killed but bearerbox is still running. But if I launch kannel on a i386-pc, it works properly. Now, if I look on my network, everything start correctly, but after acknowledging HTTP GET, kannel send a TCP [Fin Ack] to wap.ugc.fr instead of sending a WTP+WSP WSP Reply to WinWap host (see below for further details). Does someone understand why wapbox is killed? Do I miss installing something in my configuration that could explain the difference between my arm device and an other device? regards, Paul Gounot. Here are description of packets that traffic on the network: 10.777769 Winwap.host -> kannel.host WTP+WSP WSP Connect 10.951350 kannel.host -> Winwap.host WTP+WSP WSP ConnectReply 10.951713 Winwap.host -> kannel.host WTP+WSP WTP Ack 15.227617 Winwap.host -> kannel.host WTP+WSP WSP Get 15.771908 kannel.host -> nameserver DNS Standard query A wap.ugc.fr 15.885724 nameserver -> kannel.host DNS Standard query response A 62.160.234.145 15.890257 kannel.host -> wap.ugc.fr TCP 2066 > www [SYN] Seq=2363957271 Ack=0 Win=5840 Len=0 15.992598 wap.ugc.fr -> kannel.host TCP www > 2066 [SYN, ACK] Seq=3464766732 Ack=2363957272 Win=32120 Len=0 15.993507 kannel.host -> wap.ugc.fr TCP 2066 > www [ACK] Seq=2363957272 Ack=3464766733 Win=5840 Len=0 16.621568 kannel.host -> wap.ugc.fr HTTP GET / HTTP/1.1 16.774177 wap.ugc.fr -> kannel.host TCP www > 2066 [ACK] Seq=3464766733 Ack=2363958090 Win=31856 Len=0 16.803560 wap.ugc.fr -> kannel.host HTTP HTTP/1.1 200 OK 16.804630 kannel.host -> wap.ugc.fr TCP 2066 > www [ACK] Seq=2363958090 Ack=3464767974 Win=8687 Len=0 next for arm processor: 16.882314 kannel.host -> wap.ugc.fr TCP 2066 > www [FIN, ACK] Seq=2363958090 Ack=3464767974 Win=8687 Len=0 17.053227 wap.ugc.fr -> kannel.host TCP www > 2066 [ACK] Seq=3464767974 Ack=2363958091 Win=31856 Len=0 17.054175 wap.ugc.fr -> kannel.host TCP www > 2066 [FIN, ACK] Seq=3464767974 Ack=2363958091 Win=31856 Len=0 17.054962 kannel.host -> wap.ugc.fr TCP 2066 > www [ACK] Seq=2363958091 Ack=3464767975 Win=8687 Len=0 20.425752 Winwap.host -> kannel.host WTP+WSP WSP Get 25.632776 Winwap.host -> kannel.host WTP+WSP WSP Get 30.839769 Winwap.host -> kannel.host WTP+WSP WSP Get next for i386-PC: 17.212570 kannel.host -> Winwap.host WTP+WSP WSP Reply 17.213870 Winwap.host -> kannel.host WTP+WSP WTP Ack 17.267042 Winwap.host -> kannel.host WTP+WSP WSP Get 17.318471 kannel.host -> wap.ugc.fr HTTP GET /ugc.wbmp HTTP/1.1 17.568855 wap.ugc.fr -> kannel.host HTTP HTTP/1.1 200 OK 17.568982 kannel.host -> wap.ugc.fr TCP 3126 > www [ACK] Seq=3334706178 Ack=3416309353 Win=11169 Len=0 17.576120 kannel.host -> Winwap.host WTP+WSP WSP Reply 17.577549 Winwap.host -> kannel.host WTP+WSP WTP Ack
