Le lun, 21/06/2004 à 16:48 -0700, Melkor Ainur a écrit : > i'm currently using streamyx in malaysia. their url is > http://isp.tm.net.my/ thanks... a localization page is available here to translate messages to your language (double click to edit, click button "Sauver" to save your work) : http://dev.eagle-usb.org/wakka.php?wiki=LocalizationScriptsMy
> Badness in wait_ms, the modem does eventually become > operational. I agree that this is now also true for > me. fine, this means our *.bnm files may be compatible with your modem (that's most of the time the case) > symlinked to /sbin/pppoe. btw, I'm using ppp-2.4.2 and > rp-pppoe-3.5-14 as comes with fc2. it should work what is the content of your config file for pppd ? could you try to launch pppd in debug mode ? (startadsl -d should do it, then have a look at /var/log/messages for results which should be more precise). to increase timeout, have a look at man pppd and change parameters lcp- echo-failure and lcp-echo-interval > Based on eaglestat, I presume that the modem's > training and signaling works since eaglestat reports > the expected 384/128 speed. if i understand correctly, > pppd forms the LCP config request and passes it to > pppoe which then encapsulates it and sends it on the > line right? so a timeout wating for the LCP config > request response would indicate that either we are > failing to send out the LCP config request to pppoe or > that the isp is not responding. yes > i confirmed that it's not the isp not responding > because i was able to test right after using the same > modem and windows xp to establish a valid session. your analysis seems correct hope this helps. debug output from pppd should provide more info (maybe it's related to mru/pdu... for Brazil we had to set them to 1440 to get it to work, 1492 was too high) Ben'. aka baud123
