On 1/22/06, K MS <[EMAIL PROTECTED]> wrote: > Hi, > Dec 23 21:57:23 localhost pppd[4727]: Plugin rp-pppoe.so loaded. > Dec 23 21:57:23 localhost pppd[4728]: pppd 2.4.3 started by root, uid 0 > Dec 23 21:57:23 localhost pppd[4728]: PPP session is 7279 > Dec 23 21:57:23 localhost pppd[4728]: Using interface ppp0 > Dec 23 21:57:23 localhost pppd[4728]: Connect: ppp0 <--> eth0 > Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MTU to 1500 > Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MRU to 1500 > Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MTU to 1500 > Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MRU to 1500 > Dec 23 21:57:24 localhost pppd[4728]: CHAP authentication succeeded: > Authentication success,Welcome! > Dec 23 21:57:24 localhost pppd[4728]: peer from calling number > 00:E0:FC:39:92:4A authorized > Dec 23 21:57:24 localhost pppd[4728]: not replacing default route to eth0 > [192.168.1.1] > Dec 23 21:57:24 localhost pppd[4728]: Cannot determine ethernet address > for proxy ARP > Dec 23 21:57:24 localhost pppd[4728]: local IP address 59.92.133.88 > Dec 23 21:57:24 localhost pppd[4728]: remote IP address 59.92.128.1 > Dec 23 21:57:24 localhost pppd[4728]: primary DNS address > 218.248.255.145 > Dec 23 21:57:24 localhost pppd[4728]: secondary DNS address 61.1.96.69
above lines indicate you are connected. > 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. -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
