Hi
I've been experiencing a problem with my connection since 21 August at about 13:43 according the the IPCOP logs. Connection keeps dropping intermittently. A connection does not stay active for more than 40 minutes except on a few occasions lasting over 4 hours.
I keep getting these type of messages "Session 120 terminated -- received PADT from peer"
True, I went over the cap but was over earlier in the month already.
Searching around I got this from another German forum.
Now for the weird.
Connecting the modem to Windows XP using the Ethernet port and dialing up I get the same problem.
Connecting the modem to Windows XP using the USB port (and installing the software) the problem appeard to be gone.
Now the questions...
Could this indicate a problem with the actual modem possibly the ethernet port?
PADT - Could this indicate a problem with IBurst?
I'm now pulling at 3 call references and a week later.
To see if the problem persists I'm prepaired to take my setup to work and hopefully different iBurst receivers. Tomorrow would be a bad test as it's the 1st and cap would be reset.
Within some forums I seen mentioned that some ISP's would intermediately cause connections drops when clients are over the cap.
I've been experiencing a problem with my connection since 21 August at about 13:43 according the the IPCOP logs. Connection keeps dropping intermittently. A connection does not stay active for more than 40 minutes except on a few occasions lasting over 4 hours.
I keep getting these type of messages "Session 120 terminated -- received PADT from peer"
True, I went over the cap but was over earlier in the month already.
Searching around I got this from another German forum.
5.5 The PPPoE Active Discovery Terminate (PADT) packet
This packet may be sent anytime after a session is established to
indicate that a PPPoE session has been terminated. It may be sent by
either the Host or the Access Concentrator. The DESTINATION_ADDR
field is a unicast Ethernet address, the CODE field is set to 0xa7
and the SESSION_ID MUST be set to indicate which session is to be
terminated. No TAGs are required.
Now for the weird.
Connecting the modem to Windows XP using the Ethernet port and dialing up I get the same problem.
Connecting the modem to Windows XP using the USB port (and installing the software) the problem appeard to be gone.
Now the questions...
Could this indicate a problem with the actual modem possibly the ethernet port?
PADT - Could this indicate a problem with IBurst?
I'm now pulling at 3 call references and a week later.
To see if the problem persists I'm prepaired to take my setup to work and hopefully different iBurst receivers. Tomorrow would be a bad test as it's the 1st and cap would be reset.
Within some forums I seen mentioned that some ISP's would intermediately cause connections drops when clients are over the cap.