Access Concentrator Did Not Respond

email.listen at googlemail.com email.listen at googlemail.com
Fri Aug 24 10:00:31 UTC 2007


Am Fr, 24. August 2007 10:29:35 schrieb Arnold Pietersen:
> email.listen at googlemail.com wrote:
> > Am Do, 23. August 2007 14:01:44 schrieb Arnold Pietersen:
> >> I am trying to setup PPPoE.  I get the message: Access Concentrator did
> >> not respond.  There is also a "Timeout waiting for PADO packets"
> >> message.
> >>
> >> How do I solve this?
> >
> > [...]
> >
> > You may trace the connection / dial-in from a terminal.
> > First open a terminal and type:
> >  sudo tail -f /var/log/messages
> >
> > So you will see all messages during a connect.
> >
> > Then open another terminal and type:
> >  sudo pon dsl-provider
> >
> > Now you can see the communication between your provider and the pppoe
> > process running on your machine.
> >
> > Please post the output in your next answer.
> >
> >
> > Background:
> > A message "Timeout waiting for PADO packets" is often the result of a
> > missing "return-ping" from your ISPs hardware during a connection.
> > The Problem is windows machines don't expect such a "return-ping" and so
> > the connection works for them. But Linux machines wait for this
> > return-ping. By this it often needs to ask your ISP fo a manual
> > port-reset of your line. This is a common problem here in germany for
> > those who use Telekom Germany as ISP.
[...]
>
> The following is the output:
>
> arnold at arnold-laptop:~$ sudo tail -f /var/log/messages
> Aug 23 21:42:39 arnold-laptop kernel: [ 2454.668000] IN= OUT=eth0
> SRC=169.254.6.164 DST=169.254.255.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64
> ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=58
> Aug 23 21:42:39 arnold-laptop kernel: [ 2454.668000] IN= OUT=eth0
> SRC=169.254.6.164 DST=192.168.177.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64
> ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=58
> Aug 23 21:42:53 arnold-laptop gconfd (arnold-7955): starting (version
> 2.18.0.1), pid 7955 user 'arnold'
> Aug 23 21:42:53 arnold-laptop gconfd (arnold-7955): Resolved address
> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
> configuration source at position 0
> Aug 23 21:42:53 arnold-laptop gconfd (arnold-7955): Resolved address
> "xml:readwrite:/home/arnold/.gconf" to a writable configuration source
> at position 1
> Aug 23 21:42:53 arnold-laptop gconfd (arnold-7955): Resolved address
> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
> configuration source at position 2
> Aug 23 21:42:53 arnold-laptop gconfd (arnold-7955): Resolved address
> "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only
> configuration source at position 3
> Aug 23 21:42:53 arnold-laptop gconfd (arnold-7955): Resolved address
> "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration
> source at position 4
> Aug 23 21:42:54 arnold-laptop gconfd (arnold-7955): Resolved address
> "xml:readwrite:/home/arnold/.gconf" to a writable configuration source
> at position 0
> Aug 23 21:42:59 arnold-laptop kernel: [ 2473.608000] NETDEV WATCHDOG:
> ib0: transmit timed out
> Aug 23 21:43:18 arnold-laptop kernel: [ 2493.608000] NETDEV WATCHDOG:
> ib0: transmit timed out
> Aug 23 21:43:38 arnold-laptop kernel: [ 2513.608000] NETDEV WATCHDOG:
> ib0: transmit timed out
> Aug 23 21:43:45 arnold-laptop pppd[8143]: Plugin rp-pppoe.so loaded.
> Aug 23 21:43:45 arnold-laptop pppd[8146]: pppd 2.4.4 started by root, uid 0
> Aug 23 21:43:58 arnold-laptop kernel: [ 2533.608000] NETDEV WATCHDOG:
> ib0: transmit timed out
> Aug 23 21:44:18 arnold-laptop kernel: [ 2553.608000] NETDEV WATCHDOG:
> ib0: transmit timed out
> Aug 23 21:44:20 arnold-laptop pppd[8146]: Timeout waiting for PADO packets
> Aug 23 21:44:38 arnold-laptop kernel: [ 2573.608000] NETDEV WATCHDOG:
> ib0: transmit timed out
> Aug 23 21:44:58 arnold-laptop kernel: [ 2593.608000] NETDEV WATCHDOG:
> ib0: transmit timed out
>
> Can you make any sense of it.

Hello Arnold 

Above ib0 stands for an iBurst modem.
And the message 'ib0: transmit timed out' shows that there is no response at 
all during a connect. For me this looks like the device is not set-up / 
configured properly.

I'm sorry to say I have never seen such a device till now.

But there is a howto on help.ubuntu.com how to set up an iBurst modem:
https://help.ubuntu.com/community/MobileWirelessBroadband

May be this HowTo will help.

regards,
thomas




More information about the ubuntu-users mailing list