I'm currently with AT&T Uverse in California, US for my small office space and they've been giving me considerably less bandwidth than what I'm paying for with ping times to yahoo.com or google.com hovering around an unacceptable 1000 ms. I've been considering running a pinging cronjob like the guy who sued his ISP in WA and using his logs to prove his point. In the process, I've discovered that the gateway modem/router combo that they're renting out to me, the Pace 5268AC is capable of feeding its activity info via syslog.
Before I get too removed from the point, my question is pretty identical to the question in the thread below:
http://www.snbforums.com/threads/communicating-amongst-subnets.20788/
except my reasons for using the gateway's dhcp AND the one on my Asus RT-AC68U are different: Uverse will not take ownership for their poor service unless I can demonstrate that the modem and everything else behind that are what's causing my high ping times and the fact that I can only get 3.0Mbps down while my suite-neighbor whom I share a wall with can get 6.0Mbps from the same ISP.
And while I was going to run the tests within one of my hosts, I've decided to get a little "fancy" by using the tools built-into the Pace 5268AC against them. While there wouldn't be a material discrepancy between the results generated by a client behind the gateway or even logging ping tests within the Asus router itself, I felt there to be something poetic about using their own tools against them, since it's AT&T's practice to avoid taking ownership of their service. In fact, in one of my lengthy discussions with the remote tech, I was advised that AT&T demonstrates their ownership by dispatching an on-site tech. Even though I let him know that I've had visits from five techs in the last week alone with no improvement, that accountability occurs when a problem reaches resolution -- not when the buck is passed onto an equally, if not less interested, on-site tech who will tell you "you should be good now" not more than a minute before the connection is dead completely. True story.
So the syslog feature has an ip field for non-dns addresses and a port field. I tried entering my WAN/public ip since there's no straightforward passthrough and the recommended workaround is to use the DMZ feature so that the Pace gateway merely serves as a bridge. Not surprisingly, the rsyslog server didn't pick up the messages from the gateway until I plugged the server in directly into one of the ports from the gateway. I've also been having a number of VOIP issues, which is insane given how undemanding the transmission of SIP and RTP packets is.
So I'm trying to bypass the Asus RT-AC68U at least with the VOIP devices and the logging server to minimize their already shoddy alibi that it's probably the Asus router giving me the high ping times etc despite the tests that they ran which proved otherwise (details of said tests can be given upon request) and to effectively use the gateway's tools, while at the same, I would like for the clients behind the LAN managed by the Asus (with subnet 192.168.2.0/24) to talk to the logging server and VOIP devices connected directly to the gateway(with subnet 192.168.1.0/24).
After all this, I wouldn't blame you if you wondered why I'm still with AT&T. And despite the already lengthy nature of this post, I've barely scratched the surface with what they've done. I've explored my other options only to find that I'm limited to Uverse and a handful of T1 providers that are completely out of my budget($400/month). Verizon, Time Warner, Charter, all of those are just names with no small business presence in the part of downtown Los Angeles I'm in. So at this point, collecting data and threatening litigation are the only options that remain for me; while normally I'm not that triggerable, AT&T has been excellent at pushing the right buttons with the consistence with which they have shown that they're more in the business of issuing apologies, excuses, and threats rather than results.
I moved literally fifteen blocks away from my old office space due to the building management converting the building from a commercial building a residential one and that seemingly trivial move completely disrupted my already poor but tolerable speed of 6Mbps.
Sorry if I buried the headline in all of this and I'd be more than happy to tease out the part that matters, but as all of the above seem inextricably entangled, this entire thing is the headline.
Before I get too removed from the point, my question is pretty identical to the question in the thread below:
http://www.snbforums.com/threads/communicating-amongst-subnets.20788/
except my reasons for using the gateway's dhcp AND the one on my Asus RT-AC68U are different: Uverse will not take ownership for their poor service unless I can demonstrate that the modem and everything else behind that are what's causing my high ping times and the fact that I can only get 3.0Mbps down while my suite-neighbor whom I share a wall with can get 6.0Mbps from the same ISP.
And while I was going to run the tests within one of my hosts, I've decided to get a little "fancy" by using the tools built-into the Pace 5268AC against them. While there wouldn't be a material discrepancy between the results generated by a client behind the gateway or even logging ping tests within the Asus router itself, I felt there to be something poetic about using their own tools against them, since it's AT&T's practice to avoid taking ownership of their service. In fact, in one of my lengthy discussions with the remote tech, I was advised that AT&T demonstrates their ownership by dispatching an on-site tech. Even though I let him know that I've had visits from five techs in the last week alone with no improvement, that accountability occurs when a problem reaches resolution -- not when the buck is passed onto an equally, if not less interested, on-site tech who will tell you "you should be good now" not more than a minute before the connection is dead completely. True story.
So the syslog feature has an ip field for non-dns addresses and a port field. I tried entering my WAN/public ip since there's no straightforward passthrough and the recommended workaround is to use the DMZ feature so that the Pace gateway merely serves as a bridge. Not surprisingly, the rsyslog server didn't pick up the messages from the gateway until I plugged the server in directly into one of the ports from the gateway. I've also been having a number of VOIP issues, which is insane given how undemanding the transmission of SIP and RTP packets is.
So I'm trying to bypass the Asus RT-AC68U at least with the VOIP devices and the logging server to minimize their already shoddy alibi that it's probably the Asus router giving me the high ping times etc despite the tests that they ran which proved otherwise (details of said tests can be given upon request) and to effectively use the gateway's tools, while at the same, I would like for the clients behind the LAN managed by the Asus (with subnet 192.168.2.0/24) to talk to the logging server and VOIP devices connected directly to the gateway(with subnet 192.168.1.0/24).
After all this, I wouldn't blame you if you wondered why I'm still with AT&T. And despite the already lengthy nature of this post, I've barely scratched the surface with what they've done. I've explored my other options only to find that I'm limited to Uverse and a handful of T1 providers that are completely out of my budget($400/month). Verizon, Time Warner, Charter, all of those are just names with no small business presence in the part of downtown Los Angeles I'm in. So at this point, collecting data and threatening litigation are the only options that remain for me; while normally I'm not that triggerable, AT&T has been excellent at pushing the right buttons with the consistence with which they have shown that they're more in the business of issuing apologies, excuses, and threats rather than results.
I moved literally fifteen blocks away from my old office space due to the building management converting the building from a commercial building a residential one and that seemingly trivial move completely disrupted my already poor but tolerable speed of 6Mbps.
Sorry if I buried the headline in all of this and I'd be more than happy to tease out the part that matters, but as all of the above seem inextricably entangled, this entire thing is the headline.
