Hi, My friend has been using iburst on Ubuntu 9.04 using the new drivers since May, however all of a sudden she is getting an error that says PPPOE: Timeout waiting for PADO packets.
I searched for some explanation for that error and a few people noted communication errors between the pc and modem, so I tried changing cables and the error persists. I have even tried re-installing the drivers but still cannot get a connection.
Does anyone maybe have any hints as to what I can check to resolve this error?
Thanks
JMR
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've seen PAD0 timeouts for apparently a range of reasons. Basically some or all of the basic PPPoE communication packets aren't being seen.
I've seen this just come and go - apparently a problem with the iBurst servers; I've seen this happen when reception was poor - and been worse when it rained; I've seen it happen when performance was really poor - apparently overloaded network or servers.
Personally cables would not be high on my list of likely causes. And in fact, while it seems possible, my experience is that PAD0 timeouts problems are not normally associated with driver problems.
(i) I *would* check that the ethernet device (normally ib0) was available and not reporting errors.
(1a) Make sure nothing (such as NetworkManager) has grabbed ib0 and is trying to start it, or is trying to get a DHCP address for it.
(1b) remember, ib0 should *NOT* require being started, and should normally be in the *DOWN* state for ibdriver to use it properly.
(ii) I would check to see if the problem seems to be associated with some OS operation. Does it occur after thee machine has been suspended or hibernated?
(My eeePC's wireless driver gets lost after a resume, so I have to reboot to reactivate it.)
(iii) check the system log to see if any other errors are being reported.
(iv) does a reboot have any effect on the problem?
(v) can you check the reception independently? Do you have access to a Windows machine you can test for reception and connectivity?
(vi) check with the iBurst provider/ISP to see if there are any known problems, and also to find out what errors (if any) are being reported at their end when you get the PAD0 timeouts. For instance, are the PAD0 packets being sent from the ISP server?
Cheers!
Nik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I went to my friends house (because my house doesn't have iburst coverage) I tested the connection and got the PADO timeout. However with a windows pc the dashboard shows 90% signal and connects immediately when I press connect. The Linux machine however still errors out. The error appears, and has been appearing solidly for about 3 weeks now, the machine does not get hibernated or suspended as it is shut down.
Where can I find the log files to see if I can find any different, more friendly errors?
Thanks
JMR
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't normallyy run Ubuntu, but on most distros the log files are in /var/log
First up, do an ls in /var/log, and see what you find. The logging system is usually configured to put general messages into a single file, and then more specific messages into a separate file for each subsystem.
If the log files are being kept somewhere other than /var/log, you will need to find where they are. The Syslog system has a config file that specifies where log mesages go, so search in /etc for the config file:
ls /etc/*syslog*
**Note: You usually require admin priviledges to view the log files, so on Ubuntu, you will normally need to use "sudo" when viewing the files.
So look first for /var/log/messages, and see what you find in there.
Try something like sudo grep PAD0 /var/log/messages | tail
Each log message has an associated "subsystem" name which is included in the message. Once you've found this name (from the grep above) you can perform a more general search:
sudo <subsystem-name> /var/log/messages | tail
eg: sudo grep pppoe /var/log/messages | tail
(assuming that the subsystem name you saw in the PAD0 messages was "pppoe".)
It is also possible that Ubuntu has been configured to put the network messages into a separate log file. If you have trouble finding it, try:
sudo find /var/log -exec grep -H PAD0 {} \;
That should tell you the name(s) of all file(s) that contain messages including tthe text PAD0. Change the string "PAD0" to something else to change the search.
There are more detailed instructions on trouble-shooting in the README file that came with the drivers, but in summary consider the following:
(a) You can check the status of the ibdriver drivers using "lsmod":
lsmod | grep ib*
(b) if you suspect that there may an error loading the driver(s), unload them and then load them manually.
(c) You can check the status of the iBurst ethernet device using "ifconfig". Make sure the expected device exists:
ifconfig -a
Look for the device (normally ib0).
(d) read the README that came with the ibdriver distro for more details, and further things to try. The README troubleshooting is ordered in the same way that the events occur, so following the README items in the correct order should identify where the problem is.
Cheers!
Nik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, My friend has been using iburst on Ubuntu 9.04 using the new drivers since May, however all of a sudden she is getting an error that says PPPOE: Timeout waiting for PADO packets.
I searched for some explanation for that error and a few people noted communication errors between the pc and modem, so I tried changing cables and the error persists. I have even tried re-installing the drivers but still cannot get a connection.
Does anyone maybe have any hints as to what I can check to resolve this error?
Thanks
JMR
Hi,
This is just a quick response between flights.
I've seen PAD0 timeouts for apparently a range of reasons. Basically some or all of the basic PPPoE communication packets aren't being seen.
I've seen this just come and go - apparently a problem with the iBurst servers; I've seen this happen when reception was poor - and been worse when it rained; I've seen it happen when performance was really poor - apparently overloaded network or servers.
Personally cables would not be high on my list of likely causes. And in fact, while it seems possible, my experience is that PAD0 timeouts problems are not normally associated with driver problems.
(i) I *would* check that the ethernet device (normally ib0) was available and not reporting errors.
(1a) Make sure nothing (such as NetworkManager) has grabbed ib0 and is trying to start it, or is trying to get a DHCP address for it.
(1b) remember, ib0 should *NOT* require being started, and should normally be in the *DOWN* state for ibdriver to use it properly.
(ii) I would check to see if the problem seems to be associated with some OS operation. Does it occur after thee machine has been suspended or hibernated?
(My eeePC's wireless driver gets lost after a resume, so I have to reboot to reactivate it.)
(iii) check the system log to see if any other errors are being reported.
(iv) does a reboot have any effect on the problem?
(v) can you check the reception independently? Do you have access to a Windows machine you can test for reception and connectivity?
(vi) check with the iBurst provider/ISP to see if there are any known problems, and also to find out what errors (if any) are being reported at their end when you get the PAD0 timeouts. For instance, are the PAD0 packets being sent from the ISP server?
Cheers!
Nik
Hi Nik
I went to my friends house (because my house doesn't have iburst coverage) I tested the connection and got the PADO timeout. However with a windows pc the dashboard shows 90% signal and connects immediately when I press connect. The Linux machine however still errors out. The error appears, and has been appearing solidly for about 3 weeks now, the machine does not get hibernated or suspended as it is shut down.
Where can I find the log files to see if I can find any different, more friendly errors?
Thanks
JMR
Hi JMR,
I don't normallyy run Ubuntu, but on most distros the log files are in /var/log
First up, do an ls in /var/log, and see what you find. The logging system is usually configured to put general messages into a single file, and then more specific messages into a separate file for each subsystem.
If the log files are being kept somewhere other than /var/log, you will need to find where they are. The Syslog system has a config file that specifies where log mesages go, so search in /etc for the config file:
ls /etc/*syslog*
**Note: You usually require admin priviledges to view the log files, so on Ubuntu, you will normally need to use "sudo" when viewing the files.
So look first for /var/log/messages, and see what you find in there.
Try something like sudo grep PAD0 /var/log/messages | tail
Each log message has an associated "subsystem" name which is included in the message. Once you've found this name (from the grep above) you can perform a more general search:
sudo <subsystem-name> /var/log/messages | tail
eg: sudo grep pppoe /var/log/messages | tail
(assuming that the subsystem name you saw in the PAD0 messages was "pppoe".)
It is also possible that Ubuntu has been configured to put the network messages into a separate log file. If you have trouble finding it, try:
sudo find /var/log -exec grep -H PAD0 {} \;
That should tell you the name(s) of all file(s) that contain messages including tthe text PAD0. Change the string "PAD0" to something else to change the search.
There are more detailed instructions on trouble-shooting in the README file that came with the drivers, but in summary consider the following:
(a) You can check the status of the ibdriver drivers using "lsmod":
lsmod | grep ib*
(b) if you suspect that there may an error loading the driver(s), unload them and then load them manually.
(c) You can check the status of the iBurst ethernet device using "ifconfig". Make sure the expected device exists:
ifconfig -a
Look for the device (normally ib0).
(d) read the README that came with the ibdriver distro for more details, and further things to try. The README troubleshooting is ordered in the same way that the events occur, so following the README items in the correct order should identify where the problem is.
Cheers!
Nik