Topic: BPALogin IPTables Problems

[zzygan]

I've got my cable connection working with BPA Login using the instructions on synapticserver.com. The connection works fine, but in /var/log/messages i'm getting the folloing

May  5 13:47:33 gamma bpalogin[12198]: Timed out waiting for heartbeat - logging on
May  5 13:47:33 gamma bpalogin[12198]: Logged on as xxxxxx - successful at Thu May  5 13:47:33 2005

it keeps doing this every 5 -7 minutes, which then it just reconnects

I've tried using the folloing iptables command, but it still keeps disconnecting.
iptables -I INPUT 9 -s 61.9.208.13 -i eth1 -p udp --dport 5050 -j ACCEPT

I noticed also that when BPALogin starts up it says "Listening on 1065", but the port number in bpalogin.conf is 5050. Becasue of this i've tried changing the port number in the iptables command to be 1064, but it still does the same.

I'm confused, can anyone help?

[KelvinLee]

If you searched the forums for bpalogin, you will find many posts with issues such as the one you face. I was using bpalogin for some time until the limitations from it (mostly to do with recovery after an outage) made me decide to dump it in favour of a hardware router. Netgear routers with bpa clients appear to be amongst the most stable around and I've used Linksys, D-Link and even a few lesser known ones with varying levels of success. My Netgear router's been going without needing a reboot for more than half a year now (last reboot was due to shutting off power to the house during some electrical works).

Kelvin

[CharlieBrady]

If you searched the forums for bpalogin, you will find many posts with issues such as the one you face. I was using bpalogin for some time until the limitations from it (mostly to do with recovery after an outage) made me decide to dump it in favour of a hardware router. Netgear routers with bpa clients appear to be amongst the most stable around and I've used Linksys, D-Link and even a few lesser known ones with varying levels of success.

If you search here, you'll also find many problems associalted with using (so-called "hardware") routers.

At least some of the routers run linux, and use essentially the same bpalogin (GPL) client. Hence I'm sure it's possible to build a current, bug-fixed bpalogin client and run it directly on the SME server. Obviously someone in Australia would need to develop that support.

If it's an iptables causing the problem, then there'll be log file messages showing the source and destination port numbers.

[KelvinLee]

At least some of the routers run linux, and use essentially the same bpalogin (GPL) client

And that's probably why they were exhibiting similar problems as the bpalogin contrib ...

Kelvin

[CharlieBrady]

At least some of the routers run linux, and use essentially the same bpalogin (GPL) client

And that's probably why they were exhibiting similar problems as the bpalogin contrib ...

So what's needed is a packet capture and some logs so that someone can fix the bpalogin client - if they have not done so already.

[CharlieBrady]

I've got my cable connection working with BPA Login using the instructions on synapticserver.com. The connection works fine, but in /var/log/messages i'm getting the folloing

May  5 13:47:33 gamma bpalogin[12198]: Timed out waiting for heartbeat - logging on
May  5 13:47:33 gamma bpalogin[12198]: Logged on as xxxxxx - successful at Thu May  5 13:47:33 2005

it keeps doing this every 5 -7 minutes, which then it just reconnects

I've tried using the folloing iptables command, but it still keeps disconnecting.
iptables -I INPUT 9 -s 61.9.208.13 -i eth1 -p udp --dport 5050 -j ACCEPT

I noticed also that when BPALogin starts up it says "Listening on 1065", but the port number in bpalogin.conf is 5050. Becasue of this i've tried changing the port number in the iptables command to be 1064, but it still does the same.

I'm confused, can anyone help?

If you're not seeing any iptables logged packets (and you haven't shown any), then firewalling is not the problem - and you can't fix it by running iptables commands.