I did not see the problem directly myself, it was based on a customer
report. After letting me know about the problem, they switched to
using FreeBSD and MP, so I was not able to examine the problem myself.
This was with 3.8b21, and when I originally posted about it, nobody
else reported seeing any similar problems. Since I had no easy way
to test/verify the problem, and nobody else chimed in at the time,
I didn't open a ticket with support. [Support would likely have said
"update to the official 3.8 release (which came out one week after my
initial report) and see how it works for you" before passing it on to
engineers. I went through that route enough times during 3.8 beta
with ongoing problems, and was not particularly interested in doing
so for a problem that didn't affect me, didn't seem to affect others,
and that I could not easily retest.]
When somebody else reported similar problems a few weeks later, at
least two other people indicated they were going to open tickets on
the problem, and since I still had no setup to test the problem, I
didn't open a ticket of my own. Apparently the other people never
opened a ticket, either, although I have no idea why.
I suppose I should have at least sent a note to support about it. But
there were more important things to deal with during the 3.8 betas, and
it just wasn't a priority item for me, especially since I would not
have been able to give any additional info/testing to support, nor
would I have been able to test it on the official 3.8. Sorry.
BTW, my original post is here:
http://www.livingston.com/tech/archive/portmaster-users/9809/0883.html
I had long since forgotten, but apparently the symptoms my customer saw
indicated that traffic directly to the dialup IP address was properly
balanced, but traffic for any routed subnets would only go over the
first connection. I did not have a chance to verify that, but if you
are in a position to test that now, you might do so, and if that is the
case let Lucent know about it. It would almost certainly help them
isololate the cause and find a fix.
The second round of discussions started here, after the official release
of ComOS 3.8, if anybody is interested in seeing what others said at that
time:
http://www.livingston.com/tech/archive/portmaster-users/9810/0409.html
Michael Bryan
pmu@ursine.com
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>