Hi Kao, You are doing fine with the mailing list. Plus you know how to use Wireshark on your own! This should be a breeze.
Smells like a firewall issue. However it is not, since it would show in netstat. Let's look at some logs: Kill all bearerbox wapbox processes. Start from one shell: bearebox -v 0 <conffile> >From another shell: wapbox -v 0 <confile> Cpature and post. Also please post your entire confile with * where you want to hide info. I can't see anything wrong with what you posted, so there might be something bad elsewhere. BR, Nikos ----- Original Message ----- From: Kao. Josh (GSM) To: Nikos Balkanas ; [email protected] Sent: Wednesday, February 04, 2009 4:45 AM Subject: RE: Can't find a port to receive link request in wap gateway Dear Nikos, Thanks for you suggestion! I’ve put password in my original kannel.conf, I am sorry that I should put some * mark in this column so that it wouldn’t misleading you, sorry again! I also try your suggestion command and it shows the pid and my bearerbox running command. I’ve tried to use wireshark (ethreal) to capture the incoming port 9201 packets and find the kernel will response a RST/ACK when it receives my cell phone’s link request. So I suppose for some reason kernel doesn’t have any record that there is a TCP process listening on the port 9201. Any idea about it? Please tell me if you need more information and please give me some suggestions if you have any idea. Thank you very much! Best Regards, Josh p.s: It’s my first time to use mail list, hope it is a proper way to post a reply message. ------------------------------------------------------------------------------ From: Nikos Balkanas [mailto:[email protected]] Sent: Tuesday, February 03, 2009 9:23 PM To: Kao. Josh (GSM); [email protected] Subject: Re: Can't find a port to receive link request in wap gateway Try "pgrep -fl bearerbox". You shouldn't see anything running. Look at bearerbox.log to find the reason. You should find a panic because it is missing admin-password. Solution: Put an admin-password. BR, Nikos ----- Original Message ----- From: Kao. Josh (GSM) To: [email protected] Sent: Tuesday, February 03, 2009 7:43 AM Subject: Can't find a port to receive link request in wap gateway Dear all, I am trying setup Kannel to be a wap gateway for a long time, but I always have a problem when wap browser connects to Kannel. I find there doesn’t have a port to receive wap browser’s link request because wap browser always show the gateway timeout alert (I set port 9201 on the wap browser gateway port). I use “netstat” and can’t find any process listening wap related port such as 9200, 9201…etc. I’ve tried fake wap sender and it works fine. The following is my Kannel configuration; almost all of them are default value. group = core admin-port = 13000 wapbox-port = 13002 admin-password = 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 = "" group = wapbox bearerbox-host = 127.0.0.1 log-file = "/tmp/wapbox.log" log-level = 0 syslog-level = none I already google this problem for a long time but can’t find any information. So, is there anyone have some idea about this situation? Any clue is appreciated! Thank you very much! Best Regards, Josh ================================================================================================================================================================ This message may contain information which is private, privileged or confidential of Compal Communications, Inc. If you are not the intended recipient of this message, please notify the sender and destroy/delete the message. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. ================================================================================================================================================================ ================================================================================================================================================================ This message may contain information which is private, privileged or confidential of Compal Communications, Inc. If you are not the intended recipient of this message, please notify the sender and destroy/delete the message. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. ================================================================================================================================================================
