I may be wasting peoples time here.
toggle quoted message
Show quoted text
The use of a 44 address on the 'public internet' needs co-operation from your ISP. I own an ISP and kind of know the deep detail of BGP and RR adverts that need to be made. Think about how a packet for a 44.whatever.you.are gets back to you..... It leaves the recipient - perhaps to the default gateway. The default gateway has to get it to the right place in your ISP core network - so that they can route it to you. That means the ISP has to advertise your IP bank - (needs to be a /24 for any of my transit providers) - from their kit. When they get the packet back they have to route it to you - ah wait when you login you will get an ip address in the range that the ISP owns, not a 44.x.y.z one. So they need to overlay a 2nd route for you (and your kit needs to know how to handle 2 or more IP arriving at your doorstep). You could NAT/PAT everything and then lose the benefit of having a 44. Find a friendly ISP and see whether you can persuade their tech support to get you to somebody who understand BGP.? I think that is a forlorn hope for most big ISPs. even having a server wont help - unless you have a BGP agreement with some peer/transit provider..... This is a UK based answer.? No idea how other countries do it.? I suspect it is just as hard elsewhere. On 02/04/2025 10:40, Chuck Gelm wrote:
On 4/1/25 16:26, Alan wrote:The problem is I cannot talk to the 44.x.x.x network,? even though I have a 44 addressHi, Alan: |