Jacques,
Thanks, will implement in appropriate packages. Please add into
your Postinstall Howto, if it is not there already.
MarvS
On Thu, Mar 26, 2009 at 4:56 AM, Jacques Goldberg
<Jacques.Goldberg@xxxxxxx> wrote:
> Marv, Antonio,
>
> With all due respect it would be much better to add to file /etc/wvdial.conf
> the following two lines:
>
> Auto DNS = on
>
> Check Def Route = on
>
>
> If browsing (or whatever else) still does not work, see the option Check DNS
> in "man wvdial.conf"
>
>
> This approach will make sure that wvdial creates a temporary replacement
> file to /etc/resolv.conf set to use the connection with the DNS server(s)
> displayed on the wvdial log (screen).
>
>
> Adding names into /etc/resolv.conf will considerably slow down the response
> from the modem connection if the names are placed at the END of the file, or
> the response of any alternate networking if placed at the BEGINNING of the
> file. DNS queries have a waiting timeout which is used in the order of
> appearance in the file and cumulates waiting until one address replies with
> the wait time.
>
>
> On that ground Marv's brute force suggestion is better except that the user
> must remember to do it before launching wvdial and undo it (i.e. restart
> alternate network) after completing the wvdial session. This could be made
> automatically with a script yet to be written embedding command wvdial:
> before writing such a script, better design the way the script will handle
> CTRL-C which terminates wvdial, so that the after-session part has a chance
> to be executed.
>
>
> I have not yet met (which proves nothing but is encouraging) any case where
> enabling the two built in options above did not solve the problem.
>
>
> Last word: man wvdial.conf , for these options, says that "there were added
> by SuSE and are On by default".
>
> I have field experience of distributions where the "default" is Off!
>
>
> Jacques
>
>
> Marvin Stodolsky wrote:
>
>> It may suffice to shutdown other COMM channels before dialing out.
>> $ ifconfig
>>
>> If there is a channel like:
>> eth0 Link encap:Ethernet HWaddr 00:13:d3:00:6e:91
>> inet addr:12.144.185.35 Bcast:12.144.185.255 Mask:255.255.255.0
>> inet6 addr: fe80::213:d3ff:fe00:6e91/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:13853 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:2002 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:3605590 (3.4 MB) TX bytes:386457 (377.3 KB)
>>
>> Then:
>> $ sudo ifconfig eth0 down
>>
>> Afterward, do the dialout and the ppp0 DNS will be used.
>> Otherwise the System will try to use the eth0 cogent DNS, and this
>> will not work,
>> i.e. browing will fail.
>>
>> MarvS
>>
>> On Wed, Mar 25, 2009 at 8:31 PM, Antonio Olivares
>> <olivares14031@xxxxxxxxx> wrote:
>>
>>>
>>> Morris,
>>>
>>> Add to the file /etc/resolv.conf the nameservers:
>>>
>>> --> primary DNS address 198.6.100.98
>>> --> pppd: ���
>>> --> secondary DNS address 198.6.1.98
>>>
>>> please do a
>>> $ sudo gedit /etc/resolv.conf
>>> and add
>>>
>>> nameserver 198.6.100.98
>>> nameserver 198.6.1.98
>>>
>>> and try to surf again
>>>
>>> when you do a cat /etc/resolv.conf you should see
>>>
>>> $ cat /etc/resolv.conf
>>> nameserver 198.6.100.98
>>> nameserver 198.6.1.98
>>>
>>> Report back if this helped to connect. If the machine does not connect,
>>> then your ISP might change these numbers so a different configuration will
>>> be needed.
>>>
>>> Regards,
>>>
>>>
>>> Antonio
>>>
>>> --- On Wed, 3/25/09, flydog_38@xxxxxxxxx <flydog_38@xxxxxxxxx> wrote:
>>>
>>>
>>>>
>>>> From: flydog_38@xxxxxxxxx <flydog_38@xxxxxxxxx>
>>>> Subject: The daemon works but...
>>>> To: discuss@xxxxxxxxxxxxx
>>>> Date: Wednesday, March 25, 2009, 5:26 PM
>>>> I tried the suggestion of putting "sudo" in front
>>>> of wvdial, and I got the modem to connect with my ISP.
>>>> However, I can't get Firefox to open my home page yet.
>>>> Here's the text of my last login session:
>>>> morris@morris-laptop:~$ sudo wvdial
>>>> [sudo] password for morris:
>>>> --> WvDial: Internet dialer version 1.60
>>>> --> Cannot get information for serial port.
>>>> --> Initializing modem.
>>>> --> Sending: ATZ
>>>> ATZ
>>>> OK
>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
>>>> OK
>>>> --> Modem initialized.
>>>> --> Sending: ATDT85969757
>>>> --> Waiting for carrier.
>>>> ATDT85969757
>>>> CONNECT 44000
>>>> --> Carrier detected. Waiting for prompt.
>>>> UQKT2 an3.rdu6.da.uu.net
>>>> Login:
>>>> --> Looks like a login prompt.
>>>> --> Sending: usuns@xxxxxxxxx
>>>> usuns@xxxxxxxxx
>>>> Password:
>>>> --> Looks like a password prompt.
>>>> --> Sending: (password)
>>>> Entering PPP Session.
>>>> IP address is 63.19.160.220
>>>> MTU is 1500.
>>>> --> Looks like a welcome message.
>>>> --> Starting pppd at Tue Mar 24 20:22:42 2009
>>>> --> Pid of pppd: 9105
>>>> --> Using interface ppp0
>>>> --> pppd: ���
>>>> --> pppd: ���
>>>> --> pppd: ���
>>>> --> pppd: ���
>>>> --> local IP address 63.19.160.220
>>>> --> pppd: ���
>>>> --> remote IP address 63.3.11.2
>>>> --> pppd: ���
>>>> --> primary DNS address 198.6.100.98
>>>> --> pppd: ���
>>>> --> secondary DNS address 198.6.1.98
>>>> --> pppd: ���
>>>>
>>>> What are the question marks? What do I need to do now?
>>>>
>>>> Thanks to everyone for their help!
>>>>
>>>> Morris
>>>>
>>>
>>>
>>>
>
>
