I have Solaris Nevada build 79 (also happened with build 87) and I am using a Huawei E220 modem with T-mobile. I made the necessary configuration changes and most networking tools/protocols work fine. I can ssh, scp, traceroute, ping, nslookup, etc on external servers. However, as soon as I open a browser and use http, the connection is totally broken and get an RTM_LOSING error when using "route monitor".
At first I thought the error was a browser related one, but that happens not to be the case. I have trussed the output of firefox, opera and lynx and there are no errors in there. They are just waiting on tcp packets that will never arrive. After a few minutes I would see the "192.168.1.1 address disappeared from kernel" error in /var/adm/messages and a bit later I would see that the routes have disappeared. I have had ssh sessions running for hours and launched nslookups, traceroutes, etc. Everything is rock solid. It just happens with http traffic. So my guess is that there might be a bug somewhere in the driver usbsacm or in the networking stack that breaks the connection when using the 3G network of T-mobile. This is the cat'ed output of /etc/ppp/peers/t-mobile: /dev/term/0 mtu 8192 debug 460800 idle 3600000 modem noauth lock crtscts defaultroute user "user" password "pass" noipdefault usepeerdns updetach noccp nobsdcomp #novj pap-max-authreq 32 pap-restart 16 pap-timeout 0 ipcp-restart 32 ipcp-accept-local ipcp-accept-remote lcp-restart 32 lcp-echo-interval 32 lcp-echo-failure 1000000 lcp-max-configure 32 lcp-max-failure 32 lcp-max-terminate 32 #kdebug 4 #proxyarp connect "/usr/bin/chat -v -f /etc/ppp/t-mobile-chat" And this is the one from /etc/ppp/t-mobile-chat: ABORT BUSY ABORT 'NO CARRIER' ABORT 'NO ANSWER' ABORT ERROR REPORT CONNECT SAY 'Calling t-mobile...\n' "" 'ATZ' OK 'ATE0V1&D2&C1S0=0+IFC=2,2' SAY 'Modem reset.\n' SAY 'Setting APN...' OK 'AT+cgdcont=1,"IP","general.t-mobile.uk"' SAY 'APN set\n' SAY 'Dialling...\n' OK 'ATDT*99#' TIMEOUT 30 CONNECT "" Could somebody shed some ideas as to what the cause of this might be? What should I trace and how should I trace it to give developers more of an idea as to what is failing? Thanks in advance for your help! Marc Torres _______________________________________________ networking-discuss mailing list [email protected]
