Further poking reveals that mbuni is trying to connect before the link is properly established and routing set up.
Using a 'fiddle' lockfile invoked by ip-up as described in : http://www.mail-archive.com/users@mbuni.org/msg02098.html (also need to remove it in ip-down) and putting 'nodetach' in the pppd peers file vastly improves things. [@@THALES GROUP RESTRICTED@@] De : users-boun...@mbuni.org [mailto:users-boun...@mbuni.org] De la part de HARLOW Peter Envoyé : 04 July 2012 15:29 À : users@mbuni.org Objet : Re: [Users] Connection to MMSC fails - MM1 De : users-boun...@mbuni.org [mailto:users-boun...@mbuni.org] De la part de HARLOW Peter Envoyé : 04 July 2012 13:53 À : users@mbuni.org Objet : Re: [Users] Connection to MMSC fails - MM1 > On further investigation this appears to be a local routing problem - I think > the data for http://mms.bouyguestelecom.fr/mms/wapenc is going through > eth0<http://mms.bouyguestelecom.fr/mms/wapenc%20is%20going%20through%20eth0>, > not ppp0. On turning off eth0, the problem now shifts to reaching the network. Starting the network with pon and then accessing the mmsc with a web browser with the proxy set appropriately works. Mbuni frequently, but not always, fails to connect. 2012-07-04 15:16:37 [3118] [5] DEBUG: WSP: Mapping `Content-ID', WSP 1.3 to 0x0040. 2012-07-04 15:16:37 [3118] [5] DEBUG: WSP: Mapping `Content-Type', WSP 1.3 to 0x0011. 2012-07-04 15:16:37 [3118] [5] ERROR: mmsbox_mm1.c:681 <fetch_content> [mmsbox-mm1] [n/a] failed to fetch/post content to host http://mms.bouyguestelecom.fr/mms/wapenc [proxy: 62.201.129.226:8080] [http_status=7] : Failed to connect to 62.201.129.226: Network is unreachable 2012-07-04 15:16:38 [3118] [5] DEBUG: Octet string at 0x112ad4f8: 2012-07-04 15:16:38 [3118] [5] DEBUG: len: 0 2012-07-04 15:16:38 [3118] [5] DEBUG: size: 0 2012-07-04 15:16:38 [3118] [5] DEBUG: immutable: 0
_______________________________________________ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
