Timothy Wood wrote: > On Tuesday 27 April 2010 10:11:18 pm Dallin Terry wrote: >> Yes, the hostname is the same thing and it should be automatically >> passed through your router. Counter-Strike ftw. > > On Wednesday 28 April 2010 05:45:22 am Brian Phillips wrote: >> I haven't seen a commercial firmware that doesn't allow you to set >> the hostname of your router. Some ISPs require the indentification >> of a hostname for access to their network (weird), so it's a setting >> that is easily configurable through the web setup screens. It's >> usually a default "linksys", "cisco", "dlink" etc. and found on the >> same pages as your DHCP/Static IP Address configuration pages. > > So if there was a network service running on my router or my > computer, I could just type in myhostname.rn.byu.edu to access it? > And which one, the router's or the computer's?
Myhostname.rn.byu.edu will access your router's external (WAN) interface. It's up to you to forward the ports/applications to the NATed computers behind the router. This assumes you set your router's hostname to "myhostname". The address is only accessible from on-campus computers. > > Ok, here's a new chapter in my story: > Since I authenticated on Sunday with my computer directly plugged in > (my router wasn't set up), I had assumed that I needed to access the > network using the same MAC address that authenticated (my computers' > MAC). So until now, I had set my router to use my computer's MAC to > access the network. Today, I wondered if that was necessary, and set > the router back to it's default MAC. I did have to reauthenticate, > but after I entered my netID and password, I didn't have to go > through any checks. The system logs the MAC address of the authenticated interface. In this case, you authenticated from behind the router, so even though the router is running it's own firmware, the system believes that the router is a computer running whatever OS the authenticated computer was running. Once a router is authenticated, all devices behind the router are assumed to be authenticated. Once a MAC address is authenticated, the OS can change and it won't require you to reauthenticate until the MAC expires a week later. So if you dual-boot, you only need to authenticate in one of the Oses, and the other one will be authenticated. > > Which brings me to another question: How did the network know that > I'm not on Windows? The browser identification? Yes, your browsers user agent tells the system what OS you are on (and a bunch of other information). Technically, you could run windows and change your user agent to tell the authentication system that you are running linux. You would then not have to scan your computer with the java utility, and instead just authenticate as you have done under linux. http://whatsmyuseragent.com/ Brian -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
