![]() I'm not an networking expert by any means, but in my forced crash course this weekend I've learnt that 10.0.0.1 is becoming common in residential routers, and is common in business networking. Set your router's IP gateway to 10.0.0.1, and try to run a. The equipment they're using is the Comcast xFi Gateways, which also use 10.0.0.1, so it's not just a local issue. ![]() After shutting down docker entirely I was finally able to access the gateways settings and change my IP gateway to 10.1.1.1, but this is likely going to cause issues when I work elsewhere where I don't have the luxury of changing the local IP, as all gateways provided by Shaw Communications (largest internet provider in Western Canada) in the last year use the 10.0.0.1 gateway. Turns out I learnt the hard way that not all routers use .x for local IP addresses, and 10updocker has hardcoded the docker gateway as 10.0.0.1. Maybe not a bug per say, but I spent hours this past weekend banging my head against my desk and swearing at my internet provider when I couldn't access any of my development sites.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |