41–50 of 64 posts
Earlier quoted context omitted.
You have a static ip4 but not a static ip6? Or does bittrex not allow whitelisting an ip6?
Static IPv6 are rare by default because computers for end users should use IPv6 privacy extensions. In Ubuntu 16.04 LTS timeframe privacy extension was still broken a bit, so it did not work on every network adapter. Nowadays it just works, unless a crazy network gives you only /128. I have no idea about Windows and MacOS.
like the incumbant cable network in germany (vodafone) ...
Earlier quoted context omitted.
Before I start I must say, I built IPv6 only datacenters and enterprise networks. I am saying from experience. > Can’t just simply put one IPv6 router/firewall behind another. Not all IPv6 routers support DHCP-PD, and even if they did, you could have 2-3-4 levels of routers/firewalls at a business. You cannot do this with IPv4 either. Routing has to work. It works for both IPv4 and In But if you are saying, you add 2…
>You cannot do this with IPv4 either. Routing has to work. It works for both IPv4 and In But if you are saying, you add 2-3-4 layers of NAT, this is just crazy. Is it? I'm behind two layers of nat and everything works fine.
I do not know who needs inbound connections to all of their devices in a corporate network, nor at home, since we solved that shit long time ago.
Both of my ISPs offer IPv6 gateways. I set them up and visited several IP6 websites. I crypto exchange I use frequently, Bittrex, allows to whitelist an IP address. Since I have a static IPv4, I did so. Problem is, my request to bittrex always goes out the IP6 gateway and Bittrex does not recognize me. I had to shut down the IP6 gateway to get into the account.
Taken from a previous comment I’ve made re IPv6: IPv6 is fundamentally not ready for real world use within small/medium businesses and homes IMO. At least not without NAT. Why? - Can’t just simply put one IPv6 router/firewall behind another. Not all IPv6 routers support DHCP-PD, and even if they did, you could have 2-3-4 levels of routers/firewalls at a business. I’m not making this up- retail/gas/food industries oft…
I learned IPv4 from blog posts written by people who read other blog posts and HOWTOs. It worked because I came along when everyone had (and needed) the experience.
IPv6 is harder because it’s the upgrade path, not a necessity. For that, I needed good professional source material. As do you: treat yourself!
Earlier quoted context omitted.
>You cannot do this with IPv4 either. Routing has to work. It works for both IPv4 and In But if you are saying, you add 2-3-4 layers of NAT, this is just crazy. Is it? I'm behind two layers of nat and everything works fine.
That NAT "does not work" is an old myth that certain people love to use. If you show it does work, their final reply is always: but inbound connections are hard. I do not know who needs inbound connections to all of their devices in a corporate network, nor at home, since we solved that shit long time ago.
And wanting inbound connections is really not that strange a request. Maybe I want to host some website at home? How about a weather station/other IoT.. How about multiplayer gaming?
There are so many things that would benefit from being able to poke some holes in the firewall. With carrier grade NAT becoming more and more common you can forget about that, since you have no control over their infrastructure to forward any ports.
It seems that no one is actually debating the book itself. So I ask: - is it good as a first book on ipv6? - does it require Cisco hardware or is it generic enough?
Taken from a previous comment I’ve made re IPv6: IPv6 is fundamentally not ready for real world use within small/medium businesses and homes IMO. At least not without NAT. Why? - Can’t just simply put one IPv6 router/firewall behind another. Not all IPv6 routers support DHCP-PD, and even if they did, you could have 2-3-4 levels of routers/firewalls at a business. I’m not making this up- retail/gas/food industries oft…
router that do BGP are cheap, especially if you're only taking a default route which is all you're going to need for using multiple ISPs for redundancy.