[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Internet access problem with Debian Sarge + BSNL Dataone



On Sun, Jan 22, 2006 at 05:49:34PM -0800, L.V.Gandhi wrote:
> On 1/22/06, K MS <debianmeister@gmail.com> wrote:
> > Hi,
> 
> >    The DNS server addresses are worrying because the address reported
> >    in the log as secondary is exactly what I supplied to pppoeconf as
> >    the *primary* DNS address. The primary reported in the log output
> >    doesn't ring a bell at all...
> 
> Primary or sec DNS, I tink shouldn't matter.
> 
> >    After the first time I ran pon the file /etc/resolv.conf contained
> >    the primary and the secondary nameserver addresses as per the log
> >    above (218.248.255.145 & 61.1.96.69).
> >    When these were edited to be 61.1.96.69 & 61.1.96.71 (the correct
> >    values supplied by ISP), the log still showed the same output and
> >    nameservers were the same (they get reset!).
> 
> DNS addresses are changed dynamically by default by ppp.
> 
> >    Some other information...
> >   debian:~# route -n
> >   Destination     Gateway         Genmask         Flags Metric Ref    Use
> > Iface
> >   192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0
> > eth0
> >   0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0
> > eth0
> >
> >    debian:~# ping 218.248.255.145
> >    PING 218.248.255.145 ( 218.248.255.145) 56(84) bytes of data.
> >   From 192.168.1.1 icmp_seq=1 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=2 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=3 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=4 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=5 Destination Net Unreachable
> >
> Normally your bsnl fellow would have configured for windows. As I have
> seen one connection in Chennai, the modem is also a router. Only that
> need to be configured. Once it is configured, you can use lines in
> /etc/network/interfaces as
> auto eth0
> iface eth0 inet dhcp
> that should connect. You can have /etc/resolv.conf with bsnl supplied DNS.
> To check your modem/router which is web server connect to http://192.168.1.1/
> and login. you can see info about router and search in google for details.
> --
If this is a broadband cable modem for ADSL or equivalent. As supplied,
it should have a setup disk. Look on there for any installation guide
for Windows for a start. If it is something like the Alcatels common
here in Europe, it will have telephone line in and USB out. Google for
(model number) and Linux and work from there. If you have something like the 
Linksys/Netgear modem/ethernet switch/wifi all in one box - they have an 
inbuilt web server. Point your browser at the web interface and go. 
Total time to setup for any OS about three minutes. If broadband with a dynamic IP for one PC, use dhclient on the PC to pick up info. 
A stanza in /etc/network/interfaces something like

auto eth0
iface eth0 inet dhcp

should do it.
> 
> L.V.Gandhi
> http://lvgandhi.tripod.com/
> linux user No.205042



Reply to: