hello all, I had previously posted this problem to ilug and got very good help from many. some one had asked me to post the log messages (I can't recall who it was, sorry ). so here is an abstract from my recent 3 days of usage. I have tried time and time again to connect over pppoe. my lan cards are eth 0 and eth1, but my internet cable is connected to eth1. here goes the log messages. Jan 1 14:59:29 csslab kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000 Jan 1 14:59:29 csslab kernel: ip_tables: (C) 2000-2002 Netfilter core team Jan 1 14:59:29 csslab kernel: NET: Registered protocol family 10 Jan 1 14:59:29 csslab kernel: Disabled Privacy Extensions on device c039b000(lo) Jan 1 14:59:29 csslab kernel: IPv6 over IPv4 tunneling driver Jan 1 14:59:29 csslab pppd[7730]: pppd 2.4.3 started by root, uid 0 Jan 1 14:59:29 csslab pppd[7730]: Using interface ppp0 Jan 1 14:59:29 csslab pppd[7730]: Connect: ppp0 <--> /dev/pts/1 Jan 1 14:59:30 csslab pppd[7730]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access Jan 1 15:00:00 csslab pppd[7730]: LCP: timeout sending Config-Requests Jan 1 15:00:04 csslab pppd[7730]: Modem hangup Jan 1 15:00:04 csslab pppd[7730]: Using interface ppp0 Jan 1 15:00:04 csslab pppd[7730]: Connect: ppp0 <--> /dev/pts/2 Jan 1 15:00:04 csslab pppd[7730]: Connection terminated. Jan 1 15:00:09 csslab pppd[7730]: Exit.
as you might have noticed the connection times out. I don't know what is the actual problem. my eth 0 is used to connect another computer which is now shareing internet via windows. but that's not what I intend to do. never the less my eth 1 has internet cable connected and I had used ./go command to configure pppoe for the same lan card. I had configured it to come up on demand and had not specified the time for which the link should stay up. is that the problem? if that is the case, how do I answer the question asked by ./go command for "should the connection come up on demand?" or some thing similar? thanking all. Krishnakant.
On 12-Oct-06, at 12:57 AM, krishnakant Mane wrote:
Jan 1 15:00:00 csslab pppd[7730]: LCP: timeout sending Config- Requests
looks like cable fault - get all connections tightened and checked
On 12/10/06, Kenneth Gonsalves lawgon@au-kbc.org wrote:
On 12-Oct-06, at 12:57 AM, krishnakant Mane wrote:
Jan 1 15:00:00 csslab pppd[7730]: LCP: timeout sending Config- Requests
looks like cable fault - get all connections tightened and checked
no, if it was a cable falt then it wont work on windows as well. my internet connection is right now working very well with windows. it was working with my gnu/linux setup too, but now it is not working. Rony had set the connection for me and the next day it stopped working. regards, Krishnakant.
On 12-Oct-06, at 9:14 AM, krishnakant Mane wrote:
looks like cable fault - get all connections tightened and checked
no, if it was a cable falt then it wont work on windows as well. my internet connection is right now working very well with windows. it was working with my gnu/linux setup too, but now it is not working. Rony had set the connection for me and the next day it stopped working.
i have found that sometimes linux is less tolerant of faulty cabling than windoze - and in the old days less tolerant of faulty modems than in doze.
On Thursday 12 October 2006 09:14, krishnakant Mane wrote:
On 12/10/06, Kenneth Gonsalves lawgon@au-kbc.org wrote:
On 12-Oct-06, at 12:57 AM, krishnakant Mane wrote:
Jan 1 15:00:00 csslab pppd[7730]: LCP: timeout sending Config- Requests
looks like cable fault - get all connections tightened and checked
More likely a mangled ras at the isp. Check your /etc/ppp/options file for lcp timeout settings. disable if neccessary and check.
hello all. tried all means to get my internet connection on. but I am not getting connected to internet. jtd suggested to change the configuration in the /etc/ppp/options. now please tell me how to get the connection up. by the way how to turn of iptables from the root prompt? jtd was suggesting some thing similar. Krishnakant.
krishnakant Mane wrote:
Rony had set the connection for me and the next day it stopped working.
Wow what a reputation! We did not change the rj45 for the cable. We only did the local networking on eth0 and setup pppoe on the cable eth1. I have a feeling, the server side software needs to be studied more.
Regards,
Rony.
___________________________________________________________ Try the all-new Yahoo! Mail. "The New Version is radically easier to use" The Wall Street Journal http://uk.docs.yahoo.com/nowyoucan.html
krishnakant Mane wrote:
I had configured it to come up on demand and had not specified the time for which the link should stay up. is that the problem? if that is the case, how do I answer the question asked by ./go command for "should the connection come up on demand?" or some thing similar?
Krish, the problem you face and my client faced earlier was of the access concentrator itself was not detected or responding. Then the connection times out.
Regards,
Rony.
___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html
On Wednesday 11 October 2006 19:27, krishnakant Mane wrote:
never the less my eth 1 has internet cable connected and I had used ./go command to configure pppoe for the same lan card. I had configured it to come up on demand and had not specified the time for which the link should stay up. is that the problem? if that is the case, how do I answer the question asked by ./go command for "should the connection come up on demand?" or some thing similar?
What ISP do you use? How is the connection configured in Windoze? Do you need to use any dialers? Please give details.
On 13/10/06, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
What ISP do you use? How is the connection configured in Windoze? Do you need to use any dialers? Please give details.
yes indeed I need to use a dialer. my interface is RS PPPOE and access concentrater is sainet1234. I have to use a dialer that is on the desktop to connect. regards. Krishnakant.
On Thursday 12 October 2006 17:19, krishnakant Mane wrote:
yes indeed I need to use a dialer. my interface is RS PPPOE and access concentrater is sainet1234. I have to use a dialer that is on the desktop to connect.
is it a default PPPoE dialer? or is it something that those guys have supplied? Have they installed any kind of drivers / softwares on your PC ( Windoze )?
Dinesh Joshi wrote:
On Thursday 12 October 2006 17:19, krishnakant Mane wrote:
yes indeed I need to use a dialer. my interface is RS PPPOE and access concentrater is sainet1234. I have to use a dialer that is on the desktop to connect.
is it a default PPPoE dialer? or is it something that those guys have supplied? Have they installed any kind of drivers / softwares on your PC ( Windoze )?
On M$ it uses the simple raspppoe package. In linux we used rp-pppoe. The penguin roared for one night after that it could take no more. :D
Regards,
Rony. Send instant messages to your online friends http://uk.messenger.yahoo.com
On Friday 13 October 2006 00:00, Rony wrote:
On M$ it uses the simple raspppoe package. In linux we used rp-pppoe. The penguin roared for one night after that it could take no more. :D
See if you can use the pppoe kernel module.
On Thursday 12 October 2006 18:30, Rony wrote:
On M$ it uses the simple raspppoe package. In linux we used rp-pppoe. The penguin roared for one night after that it could take no more. :D
Have they changed something on the server side?
Dinesh Joshi wrote:
On Thursday 12 October 2006 18:30, Rony wrote:
On M$ it uses the simple raspppoe package. In linux we used rp-pppoe. The penguin roared for one night after that it could take no more. :D
Have they changed something on the server side?
No idea but my client's overhead switch was only replaced as claimed by the cable guy. However they changed over from static ip to dhcp without actually having a dhcp service running. Same setup at Krish's place too.
I found this link given below, on google. Krish should also try to disable his firewall too as suggested by someone else on the net. iptables -F will flush the tables.
http://www.linuxquestions.org/questions//showthread.php?t=482438
Regards,
Rony. Send instant messages to your online friends http://uk.messenger.yahoo.com
hello, tried all possible options I will now just try iptables removal and see weather it works. can any one suggest me the way to remove iptable from my system till I desire. roni, I have also given a fake ip address to eth1 now and tried again, but same result. jtd tried to solve the problem over phone and still nothing seams to success. I get a number of "....." and then the connection times out. jtd rightly pointed out that my eth1 is not getting hold of the remote server. please refer to my first email on this thread to find the sample log I have posted after trying to connect. Krishnakant.
krishnakant Mane wrote:
tried all possible options I will now just try iptables removal and see weather it works. can any one suggest me the way to remove iptable from my system till I desire.
Atleast flush the table using sudo iptables -F
roni, I have also given a fake ip address to eth1 now and tried again, but same result. jtd tried to solve the problem over phone and still nothing seams to success. I get a number of "....." and then the connection times out. jtd rightly pointed out that my eth1 is not getting hold of the remote server.
Can you get some info on the server side software?
Regards,
Rony. Send instant messages to your online friends http://uk.messenger.yahoo.com
On 13/10/06, Rony ronbillypop@yahoo.co.uk wrote:
Can you get some info on the server side software?
oh, what Information do you want? may be you, jtd and othres can point out what exact information I should search for? rony, can you come over to my place some time in the evening on Sat or Sun or even today? we can visit the cable guy and may be work out some thing. if some thing really works out fine, we can put this as a case study for every one. please contact me on my mobile or email me off the list. regards. Krishnakant.