HTTP Access to Routers and Switches - It starts here

So, just been looking at ways to get into my Lab with HTTP.

Joy, just turn on the http server function with:

ip http server

In configuration mode.

The default is exec login i.e. ip http authentication exec. When I gained access by using the IP address of any of my routers it works fine. Try using a defined host name and it fails - the browser tries to resolve it via DNS and I get a search result.  Didn't find how to disable this on Safari for the Mac or via IE8 and didn't want to try too hard. One can waste a lot of time solving issues like that.

Finished off the session with a look at how a 'reflexive' static route affects routing. The answer was not at all:

ip route 35.2.35.2 255.255.255.255 101.101.0.0

ip route 101.101.0.0 255.255.0.0 10.0.0.1

where 10.0.0.1 is the only route to the loopback address 35.2.35.2.

When pinged (35.2.35.2) from elsewhere I could easily stop the routing by removing the 101.101.0.0 route (as there's no 101.101.0.0/16 network in the lab).

This means the routes I've been seeing on the work's RTRs are either legacies of routing changes or just mistakes - probably mistakes as I've seen plenty of shoddy work done by the consultants.  Isn't it true that ''In the land of the blind, the one-eyed man is king''?

Tomorrow is looming, more to think about.