FYI, my phone's Internet/Java settings are as follows:

Use Proxy: Yes
Proxy Address: MY_PUBLIC_IP
Port: 9200

Also, tcpdump allows me to see the phone's TCP SYN message arrive at the 
machine where Kannel is running, but I then see a TCP RST immediately go back 
towards the phone.  To me, this means that there is no server process listening 
on TCP port 9200.  Netstat also does not show anything bound to TCP port 9200, 
only for UDP port 9200.

The following two log entries in the kannel logfile show that kannel is bound 
to UDP port 9200:

    2007-10-11 13:53:48 [14316] [0] DEBUG: udpc_create: Bound to UDP 
<76.183.185.202:9200>

So, does kannel not support TCP connections?  If it does, then why did it not 
bind itself to TCP port 9200?

I am sure this issue is due to a simple configuration mistake on my part, but I 
have gone through the entire kannel documentation for configuration and I can't 
find the option that I need to add/modify to the configuration file.

Can someone throw me a bone?!

Thanks,

- Jorge

From: [EMAIL PROTECTED]
To: [email protected]
Subject: Why is the WAP GW not proxying requests?
Date: Wed, 10 Oct 2007 15:30:48 -0400










Hi, I have configured Kannel as a WAP GW and I can see that requests from my 
handset's browser do come in to kannel, but I do not see kannel proxying these 
requests to the target URL.  Could someone help me troubleshoot this or 
determine what is missing from my configuration?

Configuration
========

# kannel configuration file
# NOTE: YOU MUST HAVE A BLANK LINE SEPARATING THE GROUPS
group = core
admin-port = 13000
admin-password = admin
wapbox-port = 13002
wdp-interface-name = "*"
log-file = "/var/log/kannel/bearerbox.log"
log-level = 0

# WAP GW Configuration
group = wapbox
bearerbox-host = 127.0.0.1
http-interface-name = ether1
log-level = 0


Bearer box Logs
==========
[EMAIL PROTECTED] ~]# bearerbox -v 0 /etc/kannel.conf 
2007-10-10 14:06:28 [3591] [0] INFO: Debug_lvl = 0, log_file = <none>, log_lvl 
= 0
2007-10-10 14:06:28 [3591] [0] WARNING: DLR: using default 'internal' for 
storage type.
2007-10-10 14:06:28 [3591] [0] INFO: DLR using storage type: internal
2007-10-10 14:06:28 [3591] [0] DEBUG: Kannel bearerbox version `1.4.1'.
Build `Oct 16 2006 10:48:15', compiler `4.1.1 20061011 (Red Hat 4.1.1-30)'.
System Linux, release 2.6.22.2-42.fc6, version #1 SMP Wed Aug 15 12:34:26 EDT 
2007, machine i686.
Hostname host.home.bogus, IP 127.0.0.1.
Libxml version 2.6.26.
Using OpenSSL 0.9.8b 04 May 2006.
Using native malloc.

2007-10-10 14:06:28 [3591] [0] INFO: Added logfile 
`/var/log/kannel/bearerbox.log' with level `0'.
2007-10-10 14:06:28 [3591] [0] INFO: HTTP: Opening server at port 13000.
2007-10-10 14:06:28 [3591] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to 
pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
2007-10-10 14:06:28 [3591] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) 
maps to pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 2 
(gwlib/http.c:server_thread)
2007-10-10 14:06:28 [3591] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) 
maps to pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 3 
(gw/bb_http.c:httpadmin_run)
2007-10-10 14:06:28 [3591] [0] DEBUG: starting UDP sender/receiver module
2007-10-10 14:06:28 [3591] [0] INFO: Adding interface *
2007-10-10 14:06:28 [3591] [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9200>
2007-10-10 14:06:28 [3591] [4] DEBUG: Thread 4 (gw/bb_udp.c:udp_receiver) maps 
to pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 4 
(gw/bb_udp.c:udp_receiver)
2007-10-10 14:06:28 [3591] [5] DEBUG: Thread 5 (gw/bb_udp.c:udp_sender) maps to 
pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 5 (gw/bb_udp.c:udp_sender)
2007-10-10 14:06:28 [3591] [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9201>
2007-10-10 14:06:28 [3591] [6] DEBUG: Thread 6 (gw/bb_udp.c:udp_receiver) maps 
to pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 6 
(gw/bb_udp.c:udp_receiver)
2007-10-10 14:06:28 [3591] [7] DEBUG: Thread 7 (gw/bb_udp.c:udp_sender) maps to 
pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 7 (gw/bb_udp.c:udp_sender)
2007-10-10 14:06:28 [3591] [0] DEBUG: starting wapbox connection module
2007-10-10 14:06:28 [3591] [8] DEBUG: Thread 8 (gw/bb_boxc.c:wdp_to_wapboxes) 
maps to pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 8 
(gw/bb_boxc.c:wdp_to_wapboxes)
2007-10-10 14:06:28 [3591] [9] DEBUG: Thread 9 (gw/bb_boxc.c:wapboxc_run) maps 
to pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 9 
(gw/bb_boxc.c:wapboxc_run)
2007-10-10 14:06:28 [3591] [0] DEBUG: starting WDP router
2007-10-10 14:06:28 [3591] [10] DEBUG: Thread 10 (gw/bearerbox.c:wdp_router) 
maps to pid 3591.
2007-10-10 14:06:28 [3591] [0] DEBUG: Started thread 10 
(gw/bearerbox.c:wdp_router)
2007-10-10 14:06:28 [3591] [0] INFO: ----------------------------------------
2007-10-10 14:06:28 [3591] [0] INFO: Kannel bearerbox II version 1.4.1 starting
2007-10-10 14:06:28 [3591] [0] INFO: MAIN: Start-up done, entering mainloop
2007-10-10 14:07:30 [3591] [9] INFO: Client connected from <127.0.0.1> 
2007-10-10 14:07:30 [3591] [9] DEBUG: Started thread 11 (gw/bb_boxc.c:function)
2007-10-10 14:07:30 [3591] [11] DEBUG: Thread 11 (gw/bb_boxc.c:function) maps 
to pid 3591.
2007-10-10 14:07:30 [3591] [11] DEBUG: setting up systems for new wapbox
2007-10-10 14:07:30 [3591] [11] DEBUG: Started thread 12 
(gw/bb_boxc.c:boxc_sender)
2007-10-10 14:07:30 [3591] [12] DEBUG: Thread 12 (gw/bb_boxc.c:boxc_sender) 
maps to pid 3591.

2007-10-10 14:13:37 [3591] [9] INFO: Client connected from <71.96.130.200> 
2007-10-10 14:13:37 [3591] [9] DEBUG: Started thread 13 (gw/bb_boxc.c:function)
2007-10-10 14:13:37 [3591] [13] DEBUG: Thread 13 (gw/bb_boxc.c:function) maps 
to pid 3591.
2007-10-10 14:13:37 [3591] [13] DEBUG: setting up systems for new wapbox
2007-10-10 14:13:37 [3591] [13] DEBUG: Started thread 14 
(gw/bb_boxc.c:boxc_sender)
2007-10-10 14:13:37 [3591] [14] DEBUG: Thread 14 (gw/bb_boxc.c:boxc_sender) 
maps to pid 3591.

2007-10-10 14:16:08 [3591] [13] INFO: Connection closed by the box 
<71.96.130.200>
2007-10-10 14:16:08 [3591] [14] DEBUG: send_msg: sending msg to box: 
<71.96.130.200>
2007-10-10 14:16:08 [3591] [14] DEBUG: Thread 14 (gw/bb_boxc.c:boxc_sender) 
terminates.
2007-10-10 14:16:08 [3591] [13] DEBUG: Thread 13 (gw/bb_boxc.c:function) 
terminates.


WAP box logs
=========

[EMAIL PROTECTED] ~]# wapbox -v 0 /etc/kannel.conf 
2007-10-10 14:07:30 [3676] [0] INFO: Debug_lvl = 0, log_file = <none>, log_lvl 
= 0
2007-10-10 14:07:30 [3676] [0] DEBUG: Kannel wapbox version `1.4.1'.
Build `Oct 16 2006 10:48:15', compiler `4.1.1 20061011 (Red Hat 4.1.1-30)'.
System Linux, release 2.6.22.2-42.fc6, version #1 SMP Wed Aug 15 12:34:26 EDT 
2007, machine i686.
Hostname host.home.bogus, IP 127.0.0.1.
Libxml version 2.6.26.
Using OpenSSL 0.9.8b 04 May 2006.
Using native malloc.

2007-10-10 14:07:30 [3676] [0] DEBUG: Dumping Cfg 0x8b26c88
2007-10-10 14:07:30 [3676] [0] DEBUG:   filename = </etc/kannel.conf>
2007-10-10 14:07:30 [3676] [0] DEBUG:   dumping group (wapbox):
2007-10-10 14:07:30 [3676] [0] DEBUG:     <log-level> = <0>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <bearerbox-host> = <127.0.0.1>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <group> = <wapbox>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <http-interface-name> = <ether1>
2007-10-10 14:07:30 [3676] [0] DEBUG:   dumping group (core):
2007-10-10 14:07:30 [3676] [0] DEBUG:     <wapbox-port> = <13002>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <log-level> = <0>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <log-file> = 
</var/log/kannel/bearerbox.log>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <admin-password> = <admin>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <group> = <core>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <wdp-interface-name> = <*>
2007-10-10 14:07:30 [3676] [0] DEBUG:     <admin-port> = <13000>
2007-10-10 14:07:30 [3676] [0] DEBUG: Dump ends.
2007-10-10 14:07:30 [3676] [0] DEBUG: map_url_max = -1
2007-10-10 14:07:30 [3676] [0] DEBUG: no syslog parameter
2007-10-10 14:07:30 [3676] [0] INFO: 
------------------------------------------------------------
2007-10-10 14:07:30 [3676] [0] INFO: Kannel wapbox version 1.4.1 starting up.
2007-10-10 14:07:30 [3676] [1] DEBUG: Thread 1 (wap/wsp_session.c:main_thread) 
maps to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 1 
(wap/wsp_session.c:main_thread)
2007-10-10 14:07:30 [3676] [2] DEBUG: Thread 2 (wap/wsp_unit.c:main_thread) 
maps to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 2 
(wap/wsp_unit.c:main_thread)
2007-10-10 14:07:30 [3676] [3] DEBUG: Thread 3 
(wap/wsp_push_client.c:main_thread) maps to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 3 
(wap/wsp_push_client.c:main_thread)
2007-10-10 14:07:30 [3676] [4] DEBUG: Thread 4 (wap/timers.c:watch_timers) maps 
to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 4 
(wap/timers.c:watch_timers)
2007-10-10 14:07:30 [3676] [5] DEBUG: Thread 5 (wap/wtp_resp.c:main_thread) 
maps to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 5 
(wap/wtp_resp.c:main_thread)
2007-10-10 14:07:30 [3676] [6] DEBUG: Thread 6 (gw/wap-appl.c:main_thread) maps 
to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 6 
(gw/wap-appl.c:main_thread)
2007-10-10 14:07:30 [3676] [7] DEBUG: Thread 7 
(gw/wap-appl.c:return_replies_thread) maps to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 7 
(gw/wap-appl.c:return_replies_thread)
2007-10-10 14:07:30 [3676] [0] INFO: Connected to bearerbox at 127.0.0.1 port 
13002.
2007-10-10 14:07:30 [3676] [8] DEBUG: Thread 8 
(gw/heartbeat.c:heartbeat_thread) maps to pid 3676.
2007-10-10 14:07:30 [3676] [0] DEBUG: Started thread 8 
(gw/heartbeat.c:heartbeat_thread)

Thx.




Climb to the top of the charts!  Play Star Shuffle:  the word scramble 
challenge with star power. Play Now!

_________________________________________________________________
Climb to the top of the charts!  Play Star Shuffle:  the word scramble 
challenge with star power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct

Reply via email to