Just wondering if these issues should be on PHNOG. PHNOG has been quiet for a long time (except for the occasional APNIC announcements ) compared to some other countries NOG. On Nov 20, 2013 12:51 PM, "John Homer H Alvero" <[email protected]> wrote:
> Anyone still experiencing this issue? I was able to load > console.aws.amazon.com since lastnite. > > > > > > On Wed, Nov 20, 2013 at 1:31 AM, Robert Locke <[email protected]> wrote: > >> >> Yup, that's my understanding as well Fooler. >> >> Tried JP's excellent idea of switching to PLDT's name servers, but no >> dice. Still resolves to same IP, still fails to route. >> >> At this point, I'm not going to hold my breath waiting for a response >> from PLDT and will just use a VPN to get to the console. >> >> Thanks for all the responses guys, much appreciated... >> >> Rob >> >> On Nov 20, 2013, at 12:23 AM, fooler mail <[email protected]> wrote: >> >> the console login that i presented is a sign-in link for a specific >> account... if you have mutlitple aws accounts... that would be easier for >> you to login which account you want to sign-in... the account name is >> stored in cookie and redirect you to console.aws.amazon.com... >> >> aws is using dns route53 latency-based routing.. it will redirect you to >> their nearest endpoint based on network latency.. in this case.. you are >> redirected to us-east-1 region... >> yes.. there might be a firewall isue or routing problem along the >> path... nowadays.. you can't rely on traceroute... window's traceroute is >> using icmp while unix traceroute is using udp... some of the routers are >> blocking icmp type 0, 8 and 11 for security reasons... but some of them are >> misconfigured... >> >> use tcptracroute instead to get more accurate results and pinpoint where >> your packet stops... >> >> fooler. >> On Mon, Nov 18, 2013 at 10:30 PM, Robert Locke <[email protected]>wrote: >> >>> >>> To add a few more details to my previous email: >>> >>> * <account>.signin.aws.amazon.com is a CNAME for signin.aws.amazon.com. >>> >>> * signin.aws.amazon.com in turn resolves to various IP addresses (some >>> sort of round-robin), some of which I *can* access over SSL and some of >>> which I *cannot*. >>> >>> * Adding one of the working IP addresses to my hosts file takes me a >>> step further and my browser redirects me to >>> https://console.aws.amazon.com/console/home. >>> >>> * However, console.aws.amazon.com is completely inaccessible for me on >>> port 443, regardless of which IP address I use from various lookups. >>> Curiously, console.aws.amazon.com is a CNAME for an AWS US-east >>> endpoint, so I'm starting to wonder if it's a connectivity issue between >>> PLDT and US-east. >>> >>> Rob >>> >>> >>> >>> >>> >>> On Nov 19, 2013, at 7:41 AM, fooler mail <[email protected]> wrote: >>> >>> hi rob, >>> >>> basically the correct way to access AWS console is: >>> >>> https://<your_aws_account_name_here>.signin.aws.amazon.com/console >>> >>> replace <your_aws_account_name_here> with your AWS account name. >>> >>> if you think your are still having a problem do the following" >>> >>> 1) "nslookup <your_aws_account_name_here>.signin.aws.amazon.com" in >>> case if you have DNS lookup problem >>> 2) "telnet <your_aws_account_name_here>.signin.aws.amazon.com 443" in >>> case if you have firewall problem. >>> >>> if you have problems with AWS service(s) (eg. cloudformation, ec2, s3, >>> router53, etc), feel free to ask as i'm happy to answer your question(s). >>> >>> fooler. >>> >>> >>> On Mon, Nov 18, 2013 at 3:19 AM, Robert Locke <[email protected]>wrote: >>> >>>> Hi gang, >>>> >>>> Not really a Linux question, but I'm wondering if anyone else is having >>>> problems reaching the AWS console login page on a PLDT DSL connection: >>>> https://console.aws.amazon.com/ >>>> >>>> For the past few weeks I've had to use a VPN to access it. But only >>>> when I'm on my home PLDT DSL connection. Bit of a pain. >>>> >>>> Is PLDT blocking it for any reason? Any ideas who to talk to? >>>> >>>> Cheers, Rob >>>> _________________________________________________ >>>> Philippine Linux Users' Group (PLUG) Mailing List >>>> http://lists.linux.org.ph/mailman/listinfo/plug >>>> Searchable Archives: http://archives.free.net.ph >>>> >>> >>> _________________________________________________ >>> Philippine Linux Users' Group (PLUG) Mailing List >>> http://lists.linux.org.ph/mailman/listinfo/plug >>> Searchable Archives: http://archives.free.net.ph >>> >>> >>> >>> _________________________________________________ >>> Philippine Linux Users' Group (PLUG) Mailing List >>> http://lists.linux.org.ph/mailman/listinfo/plug >>> Searchable Archives: http://archives.free.net.ph >>> >> >> _________________________________________________ >> Philippine Linux Users' Group (PLUG) Mailing List >> http://lists.linux.org.ph/mailman/listinfo/plug >> Searchable Archives: http://archives.free.net.ph >> >> >> >> _________________________________________________ >> Philippine Linux Users' Group (PLUG) Mailing List >> http://lists.linux.org.ph/mailman/listinfo/plug >> Searchable Archives: http://archives.free.net.ph >> > > > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph >
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
