Once, long ago--actually, on Thu, Aug 30, 2012 at 11:24:58AM CDT--Marko Vojinovic (vvmarko@xxxxxxxxx) said: > which dhcp servers are out there (DHCPDISCOVER), and asks anyone for > an IP assignment (DHCPREQUEST). Three servers respond: 137.138.16.6 > and 137.138.17.6 refuse (DHCPNAK), while 192.168.0.1 accepts (DHCPACK) > and gives you an internal IP, which doesn't seem to be able to access > the outside world. I am not sure if this is a misconfiguration or > implemented on purpose, ... I would bet dollars to donuts they don't intend for that RFC1918 address to be out there. It'd be extremely sloppy to have it on the same segment as the 137.138 addresses; it's more likely something they don't intend to run a DHCP server that's doing so anyway. > ...but the CERN admins need to figure out why both of the two 137.138 > dhcp servers have refused to give you an IP. This is the problem on > their end of the wall outlet. Your machine seems to be configured > correctly and also behaves correctly. It's very common these days to have the switches require a new MAC address to be authorized. Whatever segment you're plugging into probably doesn't "know" the MAC address of your machine. > The guys at CERN usually know what they are doing, ... You'd certainly hope so! > ...so the best bet would be to ask them for help, they should certainly > be able to fix this. And they'd probably be happy to know about that RFC1918 DHCP server, too. Cheers, -- Dave Ihnat dihnat@xxxxxxxxxx -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
