Super Newbie Questions Please provide Linux/windows translations :)
How can I see my servers ip address. (it is handed out dhcp). Windows is ipconfig /all. Linux is.......
Why is the system name localhost.localhost. Why the dot abbreviated name. Can I change this? How can I reference it. For instance from a M$ workstation if I wanted to ping it how could I ping without having to enter the IP.
Samba lets me set a server name up but is this just for samba or can I then reference this same name for telnet, ftp, mail settings????
Paul Kraus
Network Administrator
PEL Supply Company
216.267.5775 Voice
216-267-6176 Fax
www.pelsupply.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
When asking even basic questions like these, it is helpful to mention which Linux distro you are using. Since you didn't, I will try to give you generic Linux responses. But the major distros have their own config sustems, and their own peculiar kinks, so you might find some of this either slightly off the mark or less helpful than it might be if we knew more.
Quoted 2 lines · Paul Kraus
How can I see my servers ip address. (it is handed out dhcp). Windows is ipconfig /all. Linux is.......
"ifconfig" is the usual command for this.
Without arguments, it reports on all configured interfaces. With the -a argument, it reports on all interfaces. For more, try "man ifconfig".
Some distros use the command "ip" instead. I believe "ip link" is the way to get interface info.
Quoted 1 line
Why is the system name localhost.localhost.
During installation, distros assign a default hostname and a default domain name. Some ask you if you want to change it; ithers don't.
Quoted 2 lines
Why the dot abbreviated
name.
Not sure what you mean by "dot abbreviated". I don't see any abbreviations in "localhost.localhost".
Actually, I would have expected it to read "localhost.localdomain", with the first part the hostname, the second part the domain (network) name.
Quoted 1 line
Can I change this?
Depends on what exactly you want to change. On the system itself, this name is in the file /etc/hostname. Possibly you can just edit this, but that might not survive a reboot, since on some distros, this file gets overrwritten by one of the boot/init scripts.
Quoted 3 lines
How can I reference it. For instance from a M$
workstation if I wanted to ping it how could I ping without having to enter the IP.
In this context, "reference" is a meaningless word. So I'm only replying to your "for instance".
It depends on how the "M$" workstation resolves names. Either put it in the Windows workstations hosts file (which translates between hostnames and IP addresses locally) or add it to the appropriate file on your DNS server. Without knowing more about your LAN (or your Internet conenction, if you are talking about pinging from teh Internet), I can't be more specific.
Quoted 2 lines
Samba lets me set a server name up but is this just for samba or can I then reference this same name for telnet, ftp, mail settings????
I'm not a big Samba user, but I believe this name entry is just for Samba. For standard Internet services, like the list you gave, you need to provide a namaddress pairing that the resolver on any host you want to "reference" the name from can access. This means either that system's equivalent of the /etc/hosts file ("man hosts" will explain this file on Linux systems) or an entry on whatever DNS server the system uses to resolve FQNs [Fully-Qualified Names, like the parts of normal e-mail addresses after the @ sign).
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Responses below
--------------
When asking even basic questions like these, it is helpful to mention which
Linux distro you are using. Since you didn't, I will try to give you generic Linux responses. But the major distros have their own config sustems, and their own peculiar kinks, so you might find some of this either slightly off the mark or less helpful than it might be if we knew more.
-------
RedHat 7.3
Actually, I would have expected it to read "localhost.localdomain", with
the first part the hostname, the second part the domain (network) name.
-----------
It Does. So the names on an internal network are meaningless. For instance it could be set to myserver.mynetwork.
Does the windows workgroup mean anything to Linux?
In this context, "reference" is a meaningless word. So I'm only replying to
your "for instance".
----------------
I do not see how reference is meaningless in this context. I wish to "reference" the server by name rather then by ipaddress.
It depends on how the "M$" workstation resolves names. Either put it in the
Windows workstations hosts file (which translates between hostnames and IP
addresses locally) or add it to the appropriate file on your DNS server.
Without knowing more about your LAN (or your Internet conenction, if you
are talking about pinging from teh Internet), I can't be more specific.
-----------------
This server resides on a peep-to-peer network. In the windows environment there is a master-browser that maintains a list of all the computers so they can be "referenced" by name rather the IP. This browser can change by standard M$ election rules. I do not want to add this server to every workstations hosts file especially because the ip is handed out from a router using dhcp. Which is also why I don't want to have to always do it by ip address. This is all for an internal network not the internet.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 7 lines · Paul Kraus
[...]
In this context, "reference" is a meaningless word. So I'm only replying to
your "for instance".
----------------
I do not see how reference is meaningless in this context. I wish to "reference" the server by name rather then by ipaddress.
I'm not going to get in an argument with you. Let's just leave it that I don't know what you mean, to the extent that you meant anything more than the "for instance" you gave. Perhaps someone else will be able to help here.
Quoted 8 lines
It depends on how the "M$" workstation resolves names. Either put it in the
Windows workstations hosts file (which translates between hostnames and IP
addresses locally) or add it to the appropriate file on your DNS server.Without knowing more about your LAN (or your Internet conenction, if you
Quoted 10 lines
are talking about pinging from teh Internet), I can't be more specific.
-----------------
This server resides on a peep-to-peer network. In the windows environment there is a master-browser that maintains a list of all the computers so they can be "referenced" by name rather the IP. This browser can change by standard M$ election rules. I do not want to add this server to every workstations hosts file especially because the ip is handed out from a router using dhcp. Which is also why I don't want to have to always do it by ip address. This is all for an internal network not the internet.
This is really a Windows networking question now, not a Linux question as such ... and I'm not expert on Windows-based networks. How does this Windows "master-browser" handle resolving the names of *any* device other than a Windows workstation or server (e.g., a Macintosh or a router)? Handle this Linux host the same way. (Doing this might involve getting more help with Samba than I can give you.)
In a Linux framework, BTW, the usual solution would be for the DHCP server to handle it. It would include a hostname assignment in the lease info (or it would use a MAC-address tie-in to associate a static address with the host - usually, you want *servers* to stay put with respect to their IP addresses anyway). And it would run a DNS resolver that provided the name-address translation on-LAN.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
IP command, was SuperNwebie.
In reply to Ray OlszewskiQuoted 2 lines · Ray Olszewski
Some distros use the command "ip" instead. I believe "ip link" is the way to get interface info.
Ray, i dont want to conradict you but, "ip" is a linux command so i cant see how it could be a distro spesific command, mind you i am not saying that it is not either.
ip which used to be a seperate linux routing command it was first implimented in an archive called iproute2 it is now included in slackware and AFAIK some other distro's.
One uses 'ip' mainly for routing via tunnels.
ip -V returns;
ip utility, iproute2-ss990824
--
Regards Richard
[email protected]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: IP command, was SuperNwebie.
Quoted 9 lines · At 05:52 AM 9/18/02 +0000, pa3gcu wrote:
Quoted 2 lines · Ray Olszewski
Some distros use the command "ip" instead. I believe "ip link" is the way to get interface info.
Ray, i dont want to conradict you but, "ip" is a linux command so i cant see how it could be a distro spesific command, mind you i am not saying that it is not either.
Quoted 8 lines
ip which used to be a seperate linux routing command it was first implimented in an archive called iproute2 it is now included in slackware and AFAIK some other distro's.
One uses 'ip' mainly for routing via tunnels.
ip -V returns;
ip utility, iproute2-ss990824
We are not really disagreeing, Richard, just saying the same thing a bit differently.
As far as I know, the iproute package is available for all the major distros, and some of the minor ones. But Debian, to choose the example I know best, does not include it as part of a default install. You need to install it separately. The "ip" command also requires that the kernel have some options enabled, options that not all stock kernels use (I forget the exact ones right now or I'd be more precise here).
At least one specialized distribution, LEAF, uses ip *instead* of ifconfig (and route); those two commands are not part of a default LEAF install. Since I don't know what ALL the major distros are up to these days, I didn't want to leave the original poster high and dry if he happened to be using a distro that did not include ifconfig (it wasn't until a later posting that he mentioned using Red Hat, so I didn't know at the time what he had installed). So I mentioned ip just in case.
The "ip" command can almost completely replace ifconfig and route. (I say "almost" because I haven't found an equivalent for "ifconfig -a".) In at least one specialized distro I am familiar with, it does replace them. In environments where both choices are available, I expect you are right about the usual use of "ip".
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: IP command, was SuperNwebie.
In reply to pa3gcu:/share/tmp# ip -V bash: ip: command not found
on my Slackware v8.0 install
(A-AP-D-K-N disksets).
:-|
Chuck
p.s. Thanks, Ray & Richard & others, for the years of helpful advice on this list. :-)
Quoted 9 lines · pa3gcu wrote:
Quoted 2 lines · Ray Olszewski
Some distros use the command "ip" instead. I believe "ip link" is the way to get interface info.
Ray, i dont want to conradict you but, "ip" is a linux command so i cant see how it could be a distro spesific command, mind you i am not saying that it is not either.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: IP command, was SuperNwebie.
Quoted 4 lines · Chuck Gelm
:/share/tmp# ip -Vbash: ip: command not found
Quoted 8 lines
on my Slackware v8.0 install
(A-AP-D-K-N disksets).:-|
Chuck
p.s. Thanks, Ray & Richard & others, for the years of helpful advice on this list. :-)
You wont find it on slackware-8.0 if i remember correctly, it was first included in the most recent release, 8.1.
Cheers.
Signature · 9 lines
Regards Richard [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Re: IP command, was SuperNwebie.
In reply to Chuck GelmIt may be there but not in your path:
[jdr@pyro2 jdr]$ ip -V
bash: ip: command not found
[jdr@pyro2 jdr]$ /sbin/ip -V
ip utility, iproute2-ss001007
-jdr-
Quoted 22 lines · Chuck Gelm
:/share/tmp# ip -Vbash: ip: command not found
on my Slackware v8.0 install
(A-AP-D-K-N disksets).:-|
Chuck
p.s. Thanks, Ray & Richard & others, for the years of helpful advice on this list. :-)Quoted 7 lines · pa3gcu wrote:
Quoted 2 lines · Ray Olszewski
Some distros use the command "ip" instead. I believe "ip link" is the way to get interface info.
Ray, i dont want to conradict you but, "ip" is a linux command so i cant see how it could be a distro spesific command, mind you i am not saying that it is not either.
Quoted 5 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs