Paul Nash

My feedback

  1. 52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Compute Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Paul Nash commented  · 

    (Issue imported from https://code.google.com/p/google-compute-engine/issues/detail?id=66)

    The real problem here is that GCE networking does not currently support GRE.

  2. 89 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Compute Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Paul Nash commented  · 

    The 1460 MTU is configured due to additional header space required inside Google's network. It is a difficult thing to change, but something that we're looking at.

    Note that unfortunately due to the complex nature of software and network topologies where this sometimes becomes a problem, we likely won't be able to diagnose or debug individual use cases in this forum.

  3. 20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Compute Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Paul Nash commented  · 

    A user on code.google.com notes:

    This feature would be nice. You can work around it with ip-tables entries on the target pool instances.

    For example:

    iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 8080
    iptables -t nat -I OUTPUT -p tcp -o lo --dport 80 -j REDIRECT --to-ports 8080

    An error occurred while saving the comment
    Paul Nash commented  · 
  4. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Compute Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Paul Nash commented  · 
  5. 223 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  13 comments  ·  Compute Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Paul Nash commented  · 

    Imported from https://code.google.com/p/google-compute-engine/issues/detail?id=72

    Could we have the ability to rename static IP addresses?

    For example, you may have reserved a static ip address to use as your production ip for your web server, and names it "Production Web IP". Then later on the use of that server may change, and it is no longer used as your production web server, but you need to keep the same IP address (maybe it is registered with some external service as an allowed origin for some service that you will still be using.

    In this case you will end up with a Static IP Address called "Production Web IP", that is not what is says it is. Whilst functionally it will work fine, it may become confusing for the purpose of administration in the future.

    Therefore it would be useful to be able to rename that static ip address, for example:

    gcutil setaddress "Production Web IP" --new_name "SMS Server"

1 3 Next →

Feedback and Knowledge Base