3 ms·
What is truly disturbing here... who wrote these firmwares? You'd think something as widely distributed as an Internet gateway for a major ISP would be written
by chx 9y ago
What is truly disturbing here... who wrote these firmwares? You'd think something as widely distributed as an Internet gateway for a major ISP would be written by someone who at least know some Internet basics (like which IP ranges are public and which are private). And, how do you test if this can happen. And if they made this mistake then what else is lurking in that particular piece of software?
- voltagex_ 9y agoWait til you find out what Cisco has been doing for years http://www.revolutionwifi.net/revolutionwifi/2011/03/explaining-dhcp-server-1111.html http://www.revolutionwifi.net/revolutionwifi/2011/03/explain...
- chx 9y ago"The WLC intercepts client DHCP discovery packets, inserts it's own IP address configured on the egress interface into the relay agent field, and unicasts the DHCP packet to the configured DHCP server." Mess with DHCP packets, that's a paddlin'.
- pathseeker 9y agoThat's DHCP relay...
- noselasd 9y agoIt might be a config issue, not a firmware issue. There are numerous guides/howtos floating around for configuring cisco/juniper/etc. equipment that uses 1.1.1.1,2.2.2.2 for things like loopback addresses(these are used for very different things than the lo device of 127.0.0.1), or uses such addresses for peer to peer links etc. People just copy paste these configs without thinking, I'm not at all surprised 1.1.1.1 breaks left and right.
- zentiggr 9y agoWait, you weren't aware that most equipment manufacturers' software teams leave every edge case and design decision to a coin toss between 'fastest to code' and 'least effort to code' and let the rest of us bitch and scream about the stupidest of egregious bs for years until that piece of gear isn't sold anymore, then do it again with the next model?