Hi, My friend has two machines with winmodems. I have configured hsfmodem on both of them, and now the machines can connect to the internal network of the Bezeq's 132 service. Once connected, user navigates to page http://172.29.24.1/main.html, chooses billing method (per minute or one-time charge) and provider, then some routing magic occurs and the packets can get to the internet (NATed somewhere) and back.
So far, so good. For some reason ping packets are not forwarded though, thus complicating debugging. So I used "host -t any google.com NAMESERVER_IP" command to track the connection aliveness. The NAMESERVER_IP is taken from /etc/resolv.conf file. On the first computer connection is reliable, and DNS resolution always work (for the duration of the connection). On the second computer, DNS is available only for couple of minutes only, and then I get "Connection timeout" on DNS queries. IP based connections continue operating though, e.g. if I start long download during first minutes, the download continues even after DNS queries start falling. Does anyone have any explanations on the phenomenon? What are yours experiences with 132 service? -- Arie
