iBurst & IPCop

freakalad

Member
Joined
Apr 23, 2005
Messages
16
Reaction score
0
I've been using IPCop quite successfully for a few years now, and extremely satisfied.

I use IPCop to connect to iBurst via UTP PPoE. IPCop does such a god job of managing my connection, I get better speeds than I'd get by other means.

A couple of problems seem to arise later on:

Even though I've tried throttling the maximum speeds, the connection seems to fall over when I start to get a bit 'heavy' in my bandwidth usage (around 50k). This problem seems to originate from my ISP, though I'm sure I can do something on my end to improve the connection. Setting the MTU settings in the rc.red file from 1500 to 1392 (or some such, but IPCop doesn't like this) has not improved my connection, and in fact created more instability.

My second, & probably bigger, issue is that I have trouble reconnecting. If the connection drops, for whatever reason, I cannot reconnect unless I do a full reboot of the system. I've tried disconnecting, resetting all network connections, but this is very hit-&-miss.

Example of a typical RED log failed segment:
21:49:53 red: Connectioncheck RED fail to connect
21:49:52 pppd[3185] Exit.
21:49:52 pppd[3185] Unable to complete PPPoE Discovery
21:49:52 pppd[3185] Timeout waiting for PADS packets
21:49:17 pppd[3185] pppd 2.4.2 started by root, uid 0
21:49:17 pppd[3183] RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
21:49:17 pppd[3183] Plugin rp-pppoe.so loaded.
21:49:17 red: Connectioncheck Restarting 12/500

Has anyone have any ideas on how to resolve this issue?

Any help would be appreciated

Thanks
- Jaco
 
In the dialup preferences, select the PPPoE mode and not the PPPoE Plugin option, that may help you, I had issues using the later.
 
ipcop

I've been using IPCop quite successfully for a few years now, and extremely satisfied.

I use IPCop to connect to iBurst via UTP PPoE. IPCop does such a god job of managing my connection, I get better speeds than I'd get by other means.

A couple of problems seem to arise later on:

Even though I've tried throttling the maximum speeds, the connection seems to fall over when I start to get a bit 'heavy' in my bandwidth usage (around 50k). This problem seems to originate from my ISP, though I'm sure I can do something on my end to improve the connection. Setting the MTU settings in the rc.red file from 1500 to 1392 (or some such, but IPCop doesn't like this) has not improved my connection, and in fact created more instability.

My second, & probably bigger, issue is that I have trouble reconnecting. If the connection drops, for whatever reason, I cannot reconnect unless I do a full reboot of the system. I've tried disconnecting, resetting all network connections, but this is very hit-&-miss.

Example of a typical RED log failed segment:
21:49:53 red: Connectioncheck RED fail to connect
21:49:52 pppd[3185] Exit.
21:49:52 pppd[3185] Unable to complete PPPoE Discovery
21:49:52 pppd[3185] Timeout waiting for PADS packets
21:49:17 pppd[3185] pppd 2.4.2 started by root, uid 0
21:49:17 pppd[3183] RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
21:49:17 pppd[3183] Plugin rp-pppoe.so loaded.
21:49:17 red: Connectioncheck Restarting 12/500

Has anyone have any ideas on how to resolve this issue?

Any help would be appreciated

Thanks
- Jaco



Seen that before, it started after the "deathbycap" days of Iburst. once you are throttled to 64 after reaching your allocated cap, si that your experience?
Also had that hassle but yes i use iburst on ipcop and have done for a long time, infact i use ipcop on just about anything :)
 
Progress

Thanks, n1hilist

Think that might do the trick. Seems like an arbitrary setting

As for dropping the connection, it happens even before I run out of my (soft) cap.
According to my traffic graph, I've hit a max down speed of 66.6 kB/s In the last year (whoo-hoo, BROADband!), but it seems to drop the connection around 40-50 kBps, just when I start having fun. About 10 kBps after my cap's run out.

Granted, I'm running around 20 clients on my network; that would not have been possible without IPCop.

If the PPPoE setting keeps working, I don't really care if iBurst keeps dropping me, since IPCop will just keep my connection alive.

I'm just wondering if I shouldn't set up some sort of script to to send a tiny ping to the iBurst gateway every few seconds to somehow 'force open the pipe'; keep a static route alive. Seems to work great for clients on my wireless network (like this laptop).

In my opinion, the IPCop & iBurst (pro-cobtract) combo beats Hellkom (customer no-service hassle) & mobile service providers (cost).
 
Do a tracert to google.com, obtain the iBurst gateway 41.208.232.1, then write a bat file with ping 41.208.232.1 -t -l 1

Search the iBurst forum, has been mentioned before by seburn...
 
Last edited:
My connection dies from time to time, though it seems to be related more to tower hopping.

My pings to iBurp's gateway are in the 90-150ms range, which is good. Though it will randomly drop and reconnect, even though my UTD constantly shows 5/5 signal.

And I hardly get more than 40k/s throughput during office hours, so we're going to give them the finger and go for ADSL.
 
resolution

Thanks guys. Think I've got it licked

I use a mix of clients: Windoze, Linux :) , and Mac (my laptop).
Tracert is windows, though I get your drift.

I understand the ADSL reasoning, though I refuse to deal with Hellkom; too many bad experiences. I'd rather pay twice as much for half the connection than hearing another minute of Hellkom's background music & inept call-center.
Besides, losing numerous machines to spikes over phone lines, I prefer not to be tied down to a single wall-point. Large corporates' another story.

On another point, I seem to be experiencing DNS issues with the Mac's. But that's a topic for another thread.
 
My connection dies from time to time, though it seems to be related more to tower hopping.

My pings to iBurp's gateway are in the 90-150ms range, which is good. Though it will randomly drop and reconnect, even though my UTD constantly shows 5/5 signal.

And I hardly get more than 40k/s throughput during office hours, so we're going to give them the finger and go for ADSL.

A directional antenna, Yagi from Poynting (H-plane 44 degree beamwidth) is the better solution with the Grid (H-plane 8 degree beamwidth) being best but expensive or to shield the UTD's antenna from receiving a signal from unwanted towers. Tinfoil works well, but do not allow it to come into contact with the antenna...

Have had the same problem up against the hill in CTN as omni's hop from Gardens to Blouberg.

You need at least -15dB separation in signals; (wanted/unwanted) if not it will cause you to lose more than 50% in access speeds.
 
Last edited:
Found a 'cantenna' works well.
Back in the day when Sentech was the only alternative to Hellkom, I had very poor signal where I lived. Take a Pringles can (or another tin can), punch a hole an inch from the base, & stick the areal through. Point n a direction & play :)
Other famed fixes include woks, a siv, spagetti strainer or a coke can cut long it's length & folded at the bottom. Old sat elite dish should work best, but might be overkill.
Found to improve signal by a few factors.
 
On the topic of reliability.. the main issue we have is the throughput during the day is just appauling. I can log in from home into work and it'll push 60-120k/s easily, but during the day it's utter shyte.

So I'm lead to believe that it's a problem on their side. Perhaps another tower is needed?
 
Boils down to shared bandwidth. True about additional transmission/relay towers. Same holds true for 3G/HSDPA connections, though there are far more mobile towers. Latency's another issue.
Really depend on your needs: for mail & rudimentary browsing, iBurst is great. In-house hosting & streaming media's another story.
I suppose I'm biased: I've just had too many bad experiences will Hellkom to be willing to go that route. Any telekom it out to screw their customers (had similar experiences in NZ), but I'd rather have double root-canal work without anaesthetic than dealing with Hellkom: helluva lot less painful!
On the balance, I've found iBurst's uptime to be much better than Telkom's over the span of a year, and their support & turnaround time is much better, though I've heard other people telling me the opposite. Just depends if you're a large enterprise with substantial legal clout, or an SME.
 
Boils down to shared bandwidth. True about additional transmission/relay towers. Same holds true for 3G/HSDPA connections, though there are far more mobile towers. Latency's another issue.
Really depend on your needs: for mail & rudimentary browsing, iBurst is great. In-house hosting & streaming media's another story.
I suppose I'm biased: I've just had too many bad experiences will Hellkom to be willing to go that route. Any telekom it out to screw their customers (had similar experiences in NZ), but I'd rather have double root-canal work without anaesthetic than dealing with Hellkom: helluva lot less painful!
On the balance, I've found iBurst's uptime to be much better than Telkom's over the span of a year, and their support & turnaround time is much better, though I've heard other people telling me the opposite. Just depends if you're a large enterprise with substantial legal clout, or an SME.

Mostly agree, depending on towers...
 
Top
Sign up to the MyBroadband newsletter
X