Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Luke Drumm on May 25, 2001, 07:24:15 AM

Title: Maybe it wasn't BPALogin
Post by: Luke Drumm on May 25, 2001, 07:24:15 AM

Howdy,

I'm one of those lucky (???) souls who requires BPALogin to access the net.
Just like the thousands before me, I'm finding the connection a little... troubled.

Side Note: I've got one cleanly installed 4.1.2 system with BPALogin 1.3 and the associated e-smith-bpalogin script installed.

The connection works perfectly for a varying length of time (usually measured in minutes) from server start-up (or reboot) and then promptly dies.

Now I'd be more than happy to blame BPALogin for this little failure except for the following points:
 - The connection is always okay just after a startup (ie. BPALogin logins just fine).
 - After a loss of connection, the NSW authserver is un-pingable by either name or IP. (This leads to BPALogin failing to be able to reuathorise).
 - The length of time before connection death seems vaugely dependant on what traffic is flowing. (eg. HTTP as opposed to News etc)

If it *is* BPALogin then I would of expected a restart of the BPALogin service to restart the connection (Maybe not all of the time but at least most of it).

So the question comes down to what causing it and how do I find it?

As some possible starting points, I'm wondering if there's any tests I can perform on IPChains or NameD that might give some hints.

Does anybody have any ideas?

Regards,
Luke

Title: Re: Maybe it wasn't BPALogin
Post by: Lloyd Keen on May 26, 2001, 07:57:47 PM

Hi Luke,
I dunno whether this helps or not but I put an entry in /etc/hosts file (done via a custom template) with the following:
61.9.192.13   dce-server.nsw.bigpond.net.au   dce-server
I was having trouble pinging the auth-server as well until I put this entry in the hosts file. It works for me.