Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 490
  • Last Modified:

Weird ISP Routing

Hey Guys,

We are in the process of re-subnetting our network and have found that our internet traffic gets routed through a private network address. (A range that we potentially may use.)

88.211.5xx.xxx is our gateway and as you can see traffic goes through 10.18.100.1 and 10.18.0.1 which are devices owned by our ISP.

I find this very strange as our traffic gets routed from public to private then to public again, is this a routing config problem on those devices or is it normal behaviour ? and what does this mean if we use the 10.18.0.0/16 as part of our internal subnet ?


Tracing route to 74.125.235.49 over a maximum of 30 hops

  1     1 ms     2 ms     5 ms  88.211.5xx.xxx
  2     1 ms     1 ms     1 ms  10.18.100.1
  3    22 ms     3 ms     5 ms  10.18.0.1
  4     4 ms     5 ms     3 ms  88.211.4xx.xx1
  5     4 ms     4 ms     3 ms  88.211.4xx.xx2
  6     5 ms     5 ms     3 ms  135.196.104.57
  7     5 ms     5 ms     5 ms  so-7-2-0-0.core-02.egh.uk.mdnx.net [135.196.65.106]
  8     5 ms     5 ms     5 ms  ge-1-0-0-0.jprg-02.thn.uk.mdnx.net [135.196.154.58]
  9     5 ms     5 ms     5 ms  195.66.226.125
 10     5 ms     5 ms     7 ms  209.85.252.76
 11    89 ms    83 ms    77 ms  216.239.43.192
 12   103 ms   125 ms    97 ms  209.85.251.9
 13   151 ms   149 ms   149 ms  64.233.174.146
 14   361 ms   246 ms   251 ms  64.233.174.179
 15   250 ms   249 ms   245 ms  209.85.255.57
 16   254 ms   249 ms   277 ms  64.233.175.0
 17   414 ms   340 ms   317 ms  66.249.94.105
 18   316 ms   317 ms   317 ms  72.14.233.145
 19   322 ms   318 ms   315 ms  74.125.235.49

Trace complete.
0
supportemea
Asked:
supportemea
4 Solutions
 
robocatCommented:

It is possible that your ISP uses private address, though this is commonly only seen in closed WAN networks (e.g. in MPLS networks).

This doesn't need to be a problem, even if you use these adresses internally. You won't be able to ping these external routers any more if your route these addresses to your internal network. But traffic should flow without any problems.

However to avoid confusion, you may want to avoid using these addresses yourself.
0
 
mrklaxonCommented:
Definately exclude them.  I would also check with the ISP to see what other ranges they use to make sure you don't end up with a config change on their end down the road creating an issue.

As robocat mentioned it SHOULDN'T create an issue - as long as you're firewalled/NATed between your net and the ISP.  If your routers are able to see or retain any sort of route path showing the ISP subnet you could have issues though.

At the very least, you don't want to be wondering later when trying to trace packets.
0
 
vivek_tech2003Commented:
This is not a routing configuration issue since your ISP is using private IP address after your gateway 88.211.5xx.xxx.

You can happily use 10.18.0.0/16 within your intranet until & unless you are not advertising it to ISP.
0
 
SanjeevlokeCommented:
What ISP does it at there end is not lookout of ours.

Technically thinking ..if ur using same subnet when packet goes out from ur router ur private IP gets
natted to public ..so when remote peer replies back it responds to ur public IP and not private IP.

So u need not worry ....
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now