IRC SASL Auth borked over Sprint 4G

Both WiMax and LTE, as far as I can tell, block SASL auth somehow, such that
while tethered through my Galaxy S4 (and my old Evo 4G), I can't log into
Freenode.

Does anyone here know why, or of a workaround?

This is -- According To Google -- a well known, pervasive problem.

Cheers,
-- jra

We had an IBM Proventia IPS system on one network that I was responsible for. Despite our best configuration efforts it insisted on sending TCP resets to both sides with the counterparties IP address in the source whenever we tried SASL. I never did get a firm answer as to why. Perhaps it's a similar issue?
Sam Moats

Ashworth.. Are you a loyal bitchx user or are you willing to use webchat Irc? I wish they had such magical things when I was on Irc.. We were stuck trying to make winsock functiom so mIRC would work.. :wink:

You can always setup a bip irc box then point your clients at bip so they can stay in sync using one irc handle and central logging on the server.

https://projects.duckcorp.org/projects/bip

Should be able to configure bip to use 443 with SSL for client connections to by pass the block.

--Cody

Pidgin on both Windows and SuSE; AndroIRC on my phone.

I can use the webchat facility, yes, but hate losing the local logging;
I would prefer -- as befits this list -- to figure out why the network
won't cooperate.

Verizon LTE, for a datapoint, has no trouble with this.

Cheers,
-- jra

My cousin is the VP Of Mobility Data at AT&T. I'll forward to see what he
thinks.

You can always setup a bip irc box then point your clients at bip so they can stay in sync using one irc handle and central logging on the server.

https://projects.duckcorp.org/projects/bip

Should be able to configure bip to use 443 with SSL for client connections to by pass the block.

"pass the block"? Isn't 4G globally promoted as "Internet access." Me
missing subtleties? :slight_smile:

Cheers,
mh

Try reaching out to Bob Azzi?

low blow capt wall... you know mr azzi will simply call ashworth the
criminal he is for stealing that bandwidth.

in all seriousness, it's possible (absent tcpdump evidence of tcp
resets) that this is a fairly well known sprint-wireless dns problem.