Re: Setting up network
On Thu, Mar 31, 2005 at 10:26:13PM -0500, Anthony M. Agelastos wrote: > Hello all, > > While we are on the topic, after the hostname and domain have been > setup from the initial installation, how can they be changed? I went > through the FreeBSD manual and some Google searching and did not come > up with anything that made any sense. I assume there are files to be > edited, probably under /etc. I am just not sure what all of them are. > Any assistance (or reference to a site that will explain this to me) > will be greatly appreciated (I am a newbie to UNIX and especially > FreeBSD). In /etc/rc.conf, the variable $hostname sets the machine's name at startup. Simply edit the value set here, and next time the machine starts up, the new hostname will be set. To change it in a running system without rebooting, use hostname(1): # hostname new.machine.name HTH Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgplLaAmHil85.pgp Description: PGP signature
Re: Setting up network
Hello all, While we are on the topic, after the hostname and domain have been setup from the initial installation, how can they be changed? I went through the FreeBSD manual and some Google searching and did not come up with anything that made any sense. I assume there are files to be edited, probably under /etc. I am just not sure what all of them are. Any assistance (or reference to a site that will explain this to me) will be greatly appreciated (I am a newbie to UNIX and especially FreeBSD). Regards, Anthony On Mar 31, 2005, at 5:13 PM, Tomas Quintero wrote: Essentially, the host is the 'name of the machine' if you will. So if you want, you can name it betty, or uberserver1. It doesn't matter. For that fact, as far as I really know, nor does the domain matter. However commonly when naming servers and such, they have corresponding names and domains so that they can be labeled and people who need to know, know what these machines do. In short, no, the names do not matter for your internal home network. On Thu, 31 Mar 2005 16:52:52 -0500, Jonathan Arnold <[EMAIL PROTECTED]> wrote: Something I've never been able to figure out. When installing a new machine, and you come to the "Network Configuration" dialog, what do you put in for the Host: and Domain: if it is a machine on an internal network (ie., 192.168.1.149)? Does it matter? Just give it a simple hostname and be done with it? Make something up? -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Setting up network
At 05:13 PM 3/31/2005, Tomas Quintero wrote: In short, no, the names do not matter for your internal home network. I would just add that on your internal network you may literally use any valid name. I have an office network and several of the boxes run apache, providing me with a web development environment. But I have a self made rule of not naming my websites anything which is legal on the WWW. Because you can create your own yahoo.com on your network, but the problem is that if you create thisnameisnotbeingused.com on your network, in the future that site may exist but you'll only see your own internal version. So my internal sites have domains like yoyomaplayscello raycharles nosoup4you-next and the like. Marty Marty Landman, Face 2 Interface Inc. 845-679-9387 Search & Sort Easily: http://face2interface.com/Products/FormATable.shtml Web Installed Formmail: http://face2interface.com/formINSTal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Setting up network
On Mar 31, 2005, at 4:52 PM, Jonathan Arnold wrote: Something I've never been able to figure out. When installing a new machine, and you come to the "Network Configuration" dialog, what do you put in for the Host: and Domain: if it is a machine on an internal network (ie., 192.168.1.149)? Does it matter? Just give it a simple hostname and be done with it? Make something up? If you're using DHCP via one of the ubiquitous broadband firewall/gateway thingies from Linksys or D-Link or whoever, it really doesn't matter. However, most people like to give their machines a name, anyway, even if they don't have a domain to attach it to. You might want to get your own domain, in which case you control the names in it, or one can use dyndns.org or one of the similar sites to obtain a reversible hostname in a domain like homeip.net, even when using a dynamic IP. "Making stuff up" is ok, so long as you don't make stuff up that conflicts with properly configured names. Pretending to be a host in a domain you don't belong to is considered impolite at best, and if you have a local config problem than ends up generating errors or messages sent to the real host (think bounced mail), you will not thrill whoever it is that has to clean up the mess -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Setting up network
Essentially, the host is the 'name of the machine' if you will. So if you want, you can name it betty, or uberserver1. It doesn't matter. For that fact, as far as I really know, nor does the domain matter. However commonly when naming servers and such, they have corresponding names and domains so that they can be labeled and people who need to know, know what these machines do. In short, no, the names do not matter for your internal home network. On Thu, 31 Mar 2005 16:52:52 -0500, Jonathan Arnold <[EMAIL PROTECTED]> wrote: > Something I've never been able to figure out. When installing a > new machine, and you come to the "Network Configuration" dialog, > what do you put in for the Host: and Domain: if it is a machine > on an internal network (ie., 192.168.1.149)? Does it matter? > Just give it a simple hostname and be done with it? Make something > up? > > -- > Jonathan Arnold (mailto:[EMAIL PROTECTED]) > Daemon Dancing in the Dark, a FreeBSD weblog: > http://freebsd.amazingdev.com/blog/ > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Setting up network
Something I've never been able to figure out. When installing a new machine, and you come to the "Network Configuration" dialog, what do you put in for the Host: and Domain: if it is a machine on an internal network (ie., 192.168.1.149)? Does it matter? Just give it a simple hostname and be done with it? Make something up? -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up network virtual hosts (ifconfig)
Jason Williams wrote: That seemed to have done the trick, manually. Im guessing, I could put the same thing in my rc.conf file, but with proper syntax: ifconfig_fxp0_alias0="inet 192.168.2.222 netmask 0xff On a side note, if you set something up in rc.conf, how can you manually start it without having to reboot? The rc.conf configuration above could be manually done via: ifconfig fxp0 alias 192.168.2.222 netmask 0xff Other changes to rc.conf may require you to to run a startup script-- check /usr/local/etc/rc.d-- or do something else, depending on what the change is. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up network virtual hosts (ifconfig)
On Mon, Mar 08, 2004 at 04:50:47PM -0800, Jason Williams wrote: > >e.g. something like this works fine here : > > > ># /etc/rc.local : > >ifconfig fxp0 alias 192.168.2.222 netmask 0x > > That seemed to have done the trick, manually. Im guessing, I could put the > same thing in my rc.conf file, but with proper syntax: > > ifconfig_fxp0_alias0="inet 192.168.2.222 netmask 0xff The proper syntax for the netmask on the second and subsequent interface addresses from each distinct network block is to use the all-ones netmask: you can express that either as 255.255.255.255 or as 0x or as /32, whichever suit you best. This is a FAQ on this list but it still keeps tripping people up -- despite being clearly documented in ifconfig(8): alias Establish an additional network address for this interface. This is sometimes useful when changing network numbers, and one wishes to accept packets addressed to the old interface. If the address is on the same subnet as the first network address for this interface, a non-conflicting netmask must be given. Usually 0x is most appropriate. However you look at it, 0xff could never be a correct netmask. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: setting up network virtual hosts (ifconfig)
> What if you are doing this remotely? :) > Any other way to get around that? Not unless you're connected to another machine and connected to the target box through a serial console. In this case you're probably better of making the change manually. What is it you want to reconfigure? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up network virtual hosts (ifconfig)
Well that depends on what it is, but if you want to just go through everything you can do this: # shutdown now This will put you in single-user mode. Hit enter for the default shell, then just log out (Ctrl-D) and that will fire up init and run through the rc system again. What if you are doing this remotely? :) Any other way to get around that? Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up network virtual hosts (ifconfig)
> On a side note, if you set something up in rc.conf, how can you manually > start it without having to reboot? Well that depends on what it is, but if you want to just go through everything you can do this: # shutdown now This will put you in single-user mode. Hit enter for the default shell, then just log out (Ctrl-D) and that will fire up init and run through the rc system again. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up network virtual hosts (ifconfig)
e.g. something like this works fine here : # /etc/rc.local : ifconfig fxp0 alias 192.168.2.222 netmask 0x That seemed to have done the trick, manually. Im guessing, I could put the same thing in my rc.conf file, but with proper syntax: ifconfig_fxp0_alias0="inet 192.168.2.222 netmask 0xff On a side note, if you set something up in rc.conf, how can you manually start it without having to reboot? Thanks, Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up network virtual hosts (ifconfig)
On Mon, 08 Mar 2004 16:07:41 -0800 Jason Williams <[EMAIL PROTECTED]> wrote: > For instance, I had this in my rc.conf: > > ifconfig_fxp0="inet 192.168.1.91 netmask 255.255.255.0" > and tried to add this: > ifconfig_fxp0_alias0="inet 192.168.1.75 netmask 255.255.255.0" e.g. something like this works fine here : # /etc/rc.local : ifconfig fxp0 alias 192.168.2.222 netmask 0x ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
setting up network virtual hosts (ifconfig)
Hello everyone, Just was wondering about setting up virtual hosts on NIC cards on my FreeBSD box. I read the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-virtual-hosts.html Seems simple enough, but I seemed to be having a bit of a problem. For instance, I had this in my rc.conf: ifconfig_fxp0="inet 192.168.1.91 netmask 255.255.255.0" and tried to add this: ifconfig_fxp0_alias0="inet 192.168.1.75 netmask 255.255.255.0" Two questions here: After you made a change like this, how do you restart it without having to reboot? There a way to do this using ifconfig? Secondly, I rebooted my machine after testing this out, and it appeared to hang. When I looked at the console, it was stuck on the 'hostname' part. I'm currently looking for additional information to see what I did wrong, but thought i'd ask here to see if someone can point out my error. I appreciate the help. Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
