Maybe when we cut over to IPv6 the ISPs will revert to the golden age of
putting all their gear on publicly addressable space :)
Conversely, an enjoyable network design is where you route public IPs from
a private network to a private network, and the public IP has different
services on the intern
Because private addresses have no global meaning, routing information
about private networks shall not be propagated on inter-enterprise
links, and packets with private source or destination addresses
should not be forwarded across such links. Routers in networks not
using private address
The idea behind private IP space is it doesn't leave the ISPs AS via BGP to
the rest of the internet.
On the topic of routing if you're router doesn't have a directly connected
route or specific route for 172.x.x.x/whatever it will automatically send
information to the default 0.0.0.0 route.
Ther
Virgin at least use the 172.16.x.x internally to their infrastructure
- and they suggest you use 192.168.x.x for your personal use.
Traceroutes to any "external" address outside of their network go
through a 172.16.x.x
___
Full-Disclosure - We believe in
On 2013.05.18. 10:34, Alexander Georgiev wrote:
It is sad, that many people don't understand network basics. BTW, your
internet router should not forward rfc1918 addresses to the outside,
shouldn't he?
It should. Private address ranges are not marked "magic cows" inside a
classical router's fi
It is sad, that many people don't understand network basics. BTW, your
internet router should not forward rfc1918 addresses to the outside,
shouldn't he?
Am 18. Mai 2013 04:09:48 schrieb Gary Baribault :
There is no reason for that, you can use the same address inside as
outside so long as y
There is no reason for that, you can use the same address inside as
outside so long as you don't try and reach a 10.0.0.0/8 in their
network, and that should never happen. I have seen some networks where
the inside address range is 192.168.0.0/16 or /8 and the outside is as
well, so long as your tr
If they use the 10.0.0.0/8 there's no harm, if they use a DOD range or
another 'public' routable range, there is definitely a risk.
Gary B
Gary Baribault
Courriel: g...@baribault.net
GPG Key: 0x685430d1
Fingerprint: 9E4D 1B7C CB9F 9239 11D9 71C3 6C35 C6B7 6854 30D1
On 05/17/2013 03:22 PM, Julius
AT&T won't let you use 10.0.0.0/8 inside your home network on their devices
for the same reason. You will get an error if you try to configure their
device with it.
On Friday, May 17, 2013, sec wrote:
> **
> On 2013-05-17 16:17:35 (-0400), Gary Baribault wrote:
>
> The only problem is that anyo
Many ISPs do this, usually they hijack DoD ranges. It shouldn't cause any
issues.
2013/5/17 kyle kemmerer
> So today when trying to access a device on my network (172.30.x.x range) I
> was taken to the web interface of a completely different device. This
> baffled me at first, but after a bit
There are many ISP that route IP traffic through networks with private
addresses, my ISP to do the same thing and has 10.0.0.0 class A addresses
routable.
May be it is a miss of IP addresses or may be a NAT that was published due
to some network need.
regards,
On Fri, May 17, 2013 at 8:08 PM, ky
>From a security standpoint, I agree with you, but whether their using
public or private IPs the problem is the same, but this was a routing
question .. and I see no problem with their using 'private' IPs on their
'inside' routing gear so long as they give me a routable public IP on my
gateway devi
On 2013-05-17 16:17:35 (-0400), Gary Baribault wrote:
The only problem is that anyone on a cable modem could access their
10.x.x.x/8 address space and frankly who cares.
Me, if they're still not signing (much less encrypting) packets on the
local loop, and continuing to wish real hard that no on
I'm having a little trouble understanding the problem here .. my ISP
uses public addresses for our cable modems. I host an SSH server at
home, and given my nightly logs, I can guarantee that it's accessible
from the wide wed ;-), if the intermediate routers in the ISP's network
use 10.x.x.x/8 space
This is pretty common practice for ISPs to use private RFC IP space and
route it via iBGP/OSPF/ISIS on their network.
However they don't export this space to the rest of the internet
On Fri, May 17, 2013 at 4:04 PM, sec wrote:
> **
> [At least] TWC has a vast mishmash of vendors and models and
[At least] TWC has a vast mishmash of vendors and models and device
types, depending on what they were bidding for and when, and how much
outdated CPE they've been able to or even attempted to reclaim /
replace. I would hesitate to endorse a blanket statement that they
don't do this any more.
Th
Time Warner Cable (roadrunner) used to have this problem. They used the
10.x.x.x in various subnet masks for backend management IP addresses on all
of their customer cable modems, plus whatever other network equipment they
had. 2600 mag had an article a few years ago discussing this very issue. I
a
I'm with a largish cable provider in Quebec, and they use the 10.x.x.x
network throughout theirs, but if you're trying to access a 172.30
device inside your private home or work network why is that traffic
escaping to your ISP? If you're trying to access 172.30.x.x devices over
the Internet, it's n
So today when trying to access a device on my network (172.30.x.x range) I
was taken to the web interface of a completely different device. This
baffled me at first, but after a bit of poking around, I determined that my
ISP was actually routing traffic to these addresses. See the trace below
T
19 matches
Mail list logo
