
This file should NOT be sent to Discuss@Linmodems.org
It has common guidance for modem usage after setup.


  Interfererce with browser naviagation:
  -------------------------------------
  Other COMM channels can interfere with browsing under dialout.
   Suspect channels set during your scanModem run were shown by:  ifconfig
  eth0      Link encap:Ethernet  HWaddr 00:16:d3:ff:a5:52  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1684 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1684 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:84200 (82.2 KB)  TX bytes:84200 (82.2 KB)

  A block with "lo" is an internal loopback test and harmless.

  However, other COMM channels such as ethernet "eth0" will block browser function
  through dialout connections. Domain Name Services (DNS) needed for browsing
  will be blocked by an ineffective default usage of the eth0 assigned DNS.

  If is wisest to disable bootup establishment of alternate channels in your Control Center.
  Depending on your Linux distribution,
  one of the following root/admin commands may alternatively be effective:
  # ifdown eth0
  # ifconfig eth0 down
  # /etc/init.d/network stop
  # /etc/init.d/networking stop
  Be wary that some Systems will periodically try to re-establish internet.
  So if browsing should suspiciously fail, recheck with
    ifconfig
---------------------------- end COMM Channels --------------------------
  Ubuntu is not yet providing pre-compiled drivers for WinModems

 The Modem/DOCs/DriverCompiling.txt  is a MUST READ,
 if you are not experienced in configuring kernel-source/
 or get "unresolved symbols" upon driver insertion.

  Most recent WinModem fixes are in:  http://linmodems.technion.ac.il/FAQ.html
  
(4) For guidance on automation see  http://linmodems.technion.ac.il/archive-fourth/msg03734.html
and the scripts in the slmodem-2.9.n/scripts folder/

