Re: [luau] dhcp-146-41
You are a total Ass and a disgrace to the Linux Community. Warren Togami wrote: Nobody cares. You clearly have not been reading a word we said, like usual. Joe Linux wrote: Today I'm still [EMAIL PROTECTED] jl]$ W. Wayne Liauh wrote: Red Hat: "Your computer is being controlled by a server . . ." Joe Linux previously wrote: Respectfully yours, [EMAIL PROTECTED] root]# ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
Nobody cares. You clearly have not been reading a word we said, like usual. Joe Linux wrote: Today I'm still [EMAIL PROTECTED] jl]$ W. Wayne Liauh wrote: Red Hat: "Your computer is being controlled by a server . . ." Joe Linux previously wrote: Respectfully yours, [EMAIL PROTECTED] root]#
Re: [luau] dhcp-146-41
Today I'm still [EMAIL PROTECTED] jl]$ W. Wayne Liauh wrote: Red Hat: "Your computer is being controlled by a server . . ." Joe Linux previously wrote: Respectfully yours, [EMAIL PROTECTED] root]#
Re: [luau] dhcp-146-41
W. Wayne Liauh wrote: I don't think you understand the seriousness of this issue. As I mentioned in my very first post, RoadRunner changed the host name of MY computer without my permission. (As a result, I was unable to load my printer driver even as a root.) The succeess of internet age depends on trust, i.e., whether we can trust bandwidth providers. If you think this is OK, then perhaps you should get your brain examined. Jimen, you have always demonstrated yourself as one of the more knowledgeable Linux experts on our island. I am interested in sending out a message. Nothing personal. Wayne, I really appreciate your contributions to the community, but sometimes I truly question your logic. I do not understand where you are coming from quite often. In this case, you are taking this issue way too personally and your understanding of the technical side is flawed. DHCP itself is designed set your hostname if your configuration is set to allow this. Red Hat's default configuration has done this for years. I remember it happening to me from as far back as Red Hat 5.2. I suspect this is the default because many organizations use a DHCP naming scheme for their machines. For example this is how Microsoft's Active Directory and several other directory services works. The clients by default allow themselves to be named by the network administrators in order for Intranet resources to be accessable by name rather than IP address. The problems that we experience with hostnames are mostly because of a design problem with regard to hostname resolution and applications in Linux. It is counterproductive to complain about it here and assert that it is a violation of your rights. Pointing fingers of blame wont help the situation either, because vendors and especially volunteers who work on these projects are much less likely to listen and help you when they're turned off by such unprofessional behavior. Somebody else mentioned that Mandrake always handled this particular issue properly. I sometimes heard people complain about this in Red Hat, but that is all it was, annoying complaints that only pissed off developers. If somebody would calmly spell out the problems in the proper channels I am sure it will be fixed. I will personally look into this issue during Red Hat 8.1 beta that I am currently spending about 8 hours a day in debugging. Sorry I haven't been around lately, but now I'm back. Could you please explain in detail in one e-mail so I can quickly analyze this problem? Quite frankly I'm surprised by your behavior in this instance. It seems ridiculous to me that you would quit this list over this. You have taken this way too personally. This is NOT a violation of your rights, you simply just didn't understand it fully. I'm sorry you disagreed and quit. I still consider you to be a valued member of our community. Warren Togami [EMAIL PROTECTED]
Re: [luau] dhcp-146-41
On Tue, Dec 24, 2002 at 08:44:56PM -1000, Eric Hattemer wrote: > I concur 100%. There's an IP standard of sorts that says that > all IP addresses should have a hostname attached. I only wish it were a standard. Most of the ISPs I run into do not have all their assigned IP space resolvable. > There are many services that do forward and reverse DNS lookups > on your IP/hostname to make sure they match. That is probably due to the paranoid option in tcpwrappers. It is a flawed concept. Avoid it if you can. [1] > Now maybe you're worried that your IP doesn't change too much. Some ISPs made the argument that by using DHCP, customers become a moving target and hopefully less likely to get compromised. I agree that it makes a targetted attack more difficult, but most customers are likely to be hit by automated attacks. > You could even buy a real domain name, and just update it every > time it changes. Services like dyndns.org even provide agents you can run that automatically updates your domain to resolve to your current IP address. -Vince [1] This might sound like I am contradicting myself. If you use only IP ranges in your /etc/hosts.allow, then the paranoid option is never needed and you avoid the cost of having to perform 2 lookups (IP -> hostname, hostname -> IP). If DNS is not setup properly, you have to wait for _both_ lookups to timeout.
Re: [luau] dhcp-146-41
I concur 100%. There's an IP standard of sorts that says that all IP addresses should have a hostname attached. There are many services that do forward and reverse DNS lookups on your IP/hostname to make sure they match. One such service is some ssh servers. If you didn't have a hostname (and some ISP's are broken enough not to assign them), then certain servers won't allow you connections into them. Now maybe you're worried that your IP doesn't change too much. Now to most people, this is wonderful. People pay lots and lots of money for static IP addresses. With any of the dynamic dns services available, you can get your own DNS name, and it will be correct over 99% of the time. You could even buy a real domain name, and just update it every time it changes. That takes a day or two, but since it only changes every couple of months, you could probably actually make a webserver on there and everything (Oceanic wouldn't be too thrilled if they found out, though). Now apparently you consider it a security risk. However, if someone were to randomly pick your IP to attack, it wouldn't really matter whether it never changed or changed everyday. They'd have an equal chance of randomly picking your address. Of course its possible that people could track you and whatnot, but considering that theoretically Oceanic is the only one who has any idea of your real identity, this should not be an issue. However, if you really want to change your IP address, you could probably do so by unplugging your cable modem for long periods of time. Hopefully it will eventually grab another IP because someone took yours. That's the way it works on many other networks, anyway. Otherwise, the oly other input I have is to make sure that your domain and your default dns suffixes search order are set to hawaii.rr.com, and that might help fix your problems. -Eric Hattemer - Original Message - From: "Dustin Cross" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 24, 2002 7:29 PM Subject: Re: [luau] dhcp-146-41 > Wayne, > > You do not have a permenant hostname. The IP address has a permenant > hostname in DNS. You have a temporary IP address that is almost never > changed. > > Would you please go read about IP addresses, dhcp, and DNS so that you can > speak inteligbly on the subject and stop trying to make something into > nothing. > > Here is a place for you to start: > http://www.linux.org/docs/ldp/howto/Net-HOWTO/index.html > > Dusty > > > > > I believe many cable modem users will not be thrilled when they realize > > that their computers, instead of having a changing ip, are actually > > assigned a permanent hostname. Of course, our local dhcp experts are > > telling me that having a permanent hostname don't make no difference, > > and are implicitly accusing me of spreading FUD. You make your own > > call. > > > > ___ > LUAU mailing list > [EMAIL PROTECTED] > http://videl.ics.hawaii.edu/mailman/listinfo/luau > >
Re: [luau] dhcp-146-41
uh, that was supposed to be "nothing into something" :) > make something into nothing.
Re: [luau] dhcp-146-41
Wayne, You do not have a permenant hostname. The IP address has a permenant hostname in DNS. You have a temporary IP address that is almost never changed. Would you please go read about IP addresses, dhcp, and DNS so that you can speak inteligbly on the subject and stop trying to make something into nothing. Here is a place for you to start: http://www.linux.org/docs/ldp/howto/Net-HOWTO/index.html Dusty > I believe many cable modem users will not be thrilled when they realize > that their computers, instead of having a changing ip, are actually > assigned a permanent hostname. Of course, our local dhcp experts are > telling me that having a permanent hostname don't make no difference, > and are implicitly accusing me of spreading FUD. You make your own > call.
Re: [luau] dhcp-146-41
It appears that I never had this problem because I either was running Windows or always had an external firewall. In this regard, I think Red Hat is actually doing us a big favor. An external firewall is a must if you use a broadband connection. With Windows, you probably will never receive the warning until it is too late. However, this also illustrates the potential peril of trying to enlist your friends in the fight against Microsoft monopoly. I don't think anyone would like this message when logging out from Red Hat: "Your computer is being controlled by a server . . ." Joe Linux wrote: I have Earthlink Cable which still comes on Oceanic lines and the host name changes all the time. It just so happens that Mandrake doesn't care, but Redhat does. I know the members of Denver Linux Club (CLUE) were discussing the issue at some length during an install fest. Everyone seems to know it is a problem except the people who created RedHat. Respectfully yours, [EMAIL PROTECTED] root]#
Re: [luau] dhcp-146-41
I thought about posting a comment asking if anyone in this forum has ever used RedHat 8.0 on a machine with RoadRunner without an external firewall, but decided against it, as doing this would have been too tasteless, even to someone as gross as I. I had a dhcp server installed at home a few years ago. It had been working continuously for over one year and half until I decided to change the kernel. This is a great testimonial to the stability of Linux. Although this was based on a beta version of dhcp, I believe the architecture still stays pretty much the same. One of the key features of dhcp, as far as I was concerned, is that the ip address is temporary which will expire upon disconnection or be renewed after a pre-set period of time (with a new ip), depending on the server configuration. I believe many cable modem users will not be thrilled when they realize that their computers, instead of having a changing ip, are actually assigned a permanent hostname. Of course, our local dhcp experts are telling me that having a permanent hostname don't make no difference, and are implicitly accusing me of spreading FUD. You make your own call. Kevin Goad wrote: -Original Message- It's not only Redhat that changes the Hostname. I used to have that problem when I first installed Mandrake 8.0 until I manually entered my own hostname. To even the score I recall playing around with snort one time and sniffing packets from my XP box when I came across a name something like this, mycomputername(somenumbers).hawaii.rr.com. It concerned me for a while that my computers name was exposed to the outside, that Roadrunner knew it and used it to identify me, but then I figured with two firewalls I shouldn't worry too much. ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
I have Earthlink Cable which still comes on Oceanic lines and the host name changes all the time. It just so happens that Mandrake doesn't care, but Redhat does. I know the members of Denver Linux Club (CLUE) were discussing the issue at some length during an install fest. Everyone seems to know it is a problem except the people who created RedHat. Respectfully yours, [EMAIL PROTECTED] root]# Charles Lockhart wrote: Darned tootin' (totally unsure what that means). I say vote with your wallet and cancel their service. Go Team! -Charles, who wishes everybody would quit using RR and leave all the bandwidth to him.
RE: [luau] dhcp-146-41
-Original Message- It's not only Redhat that changes the Hostname. I used to have that problem when I first installed Mandrake 8.0 until I manually entered my own hostname. To even the score I recall playing around with snort one time and sniffing packets from my XP box when I came across a name something like this, mycomputername(somenumbers).hawaii.rr.com. It concerned me for a while that my computers name was exposed to the outside, that Roadrunner knew it and used it to identify me, but then I figured with two firewalls I shouldn't worry too much.
Re: [luau] dhcp-146-41
On Mon, 23 Dec 2002, W. Wayne Liauh wrote: >I don't think you understand the seriousness of this issue. As I >mentioned in my very first post, RoadRunner changed the host name of MY >computer without my permission. Ok Wayne, I'll submit. There are two issues here. First, your friend had trouble installing and configuring RH 8.0. If this is still a problem, you know we're always ready to help. The second issue you brought up was with the setting of the host name by the DHCP server. If Dusty's response is not enough to convince you, perhaps a pointer to the authority might help. ;-) http://www.ietf.org/internet-drafts/draft-ietf-dhc-host-option-considerations-01.txt This link will take you to a draft standard that describes what the IETF thinks about setting host names for DHCP clients. You only have to read the introduction. I hope this is now clear that setting YOUR system's host name is not only safe but also something that the Internet community considers useful. Let this be the end of this thread. Thanks. --jc -- Jimen Ching (WH6BRR) [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [luau] dhcp-146-41
Wayne, WRONG! Your rights have not been violated. You are using software that askes your internet service provider for information. Your service provider gives you all of the information it has to offer. You are asking for something and then crying when you get it. Road Runner is not invading your system. How do you see your rights being breached? Road runner is letting you BORROW an IP address. They have that IP address listed in their DNS with that hostname. Your computers DHCPCD (client deamon) is configured to ask for and accept the hostname assigned by your ISP. Please explain how Road Runner is violating your computer. Several people have tried to tell you that you need to change YOUR configuration to solve YOUR problem. Road Runner has their system properly configured and working exactly how they want it to. If you want a specific hostname assigned to the IP address Road Runner lets you use, then you need to get a static IP and pay for a DNS entry. Please use your negative energy on something that can use it, like stoping SPAM. Start reading the man pages and FAQs before yelling conspiracy. Dusty > You seem to have totally ignored the fact that it is my right that is > being breached, my computer that is being invaded. > > Of course, I have to 'warn" you that I am now speaking as a politician. > > > Dustin Cross wrote: > >>Wayne, >> >>Road Runner has always assigned hostnames to all of their DHCP clients >>and so does every other ISP that uses DHCP that I know of. This is >>standard practice and is how they track the systems on their network. >>You can override this functionality, but it sounds like your problem is >>with a Redhat configuration. The hostname of your system should have >>no effect on its operation. The name localhost is ment to be assigned >>to 127.0.0.1 and not your external IP address. When your system >>communicates with localhost it is talking to 127.0.0.1 and not the IP >>address Road Runner assigned, unless you have changed something or >>Redhat's default config is wrong. You are making a big deal out of >>nothing. >> >> >>Dusty >> >> > > > ___ > LUAU mailing list > [EMAIL PROTECTED] > http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
Darned tootin' (totally unsure what that means). I say vote with your wallet and cancel their service. Go Team! -Charles, who wishes everybody would quit using RR and leave all the bandwidth to him. On Mon, 23 Dec 2002, W. Wayne Liauh wrote: > You seem to have totally ignored the fact that it is my right that is > being breached, my computer that is being invaded. > > Of course, I have to 'warn" you that I am now speaking as a politician.
Re: [luau] dhcp-146-41
You seem to have totally ignored the fact that it is my right that is being breached, my computer that is being invaded. Of course, I have to 'warn" you that I am now speaking as a politician. Dustin Cross wrote: Wayne, Road Runner has always assigned hostnames to all of their DHCP clients and so does every other ISP that uses DHCP that I know of. This is standard practice and is how they track the systems on their network. You can override this functionality, but it sounds like your problem is with a Redhat configuration. The hostname of your system should have no effect on its operation. The name localhost is ment to be assigned to 127.0.0.1 and not your external IP address. When your system communicates with localhost it is talking to 127.0.0.1 and not the IP address Road Runner assigned, unless you have changed something or Redhat's default config is wrong. You are making a big deal out of nothing. Dusty
Re: [luau] dhcp-146-41
Wayne,
Road Runner has always assigned hostnames to all of their DHCP clients and
so does every other ISP that uses DHCP that I know of. This is standard
practice and is how they track the systems on their network. You can
override this functionality, but it sounds like your problem is with a
Redhat configuration. The hostname of your system should have no effect on
its operation. The name localhost is ment to be assigned to 127.0.0.1 and
not your external IP address. When your system communicates with localhost
it is talking to 127.0.0.1 and not the IP address Road Runner assigned,
unless you have changed something or Redhat's default config is wrong. You
are making a big deal out of nothing.
Dusty
> Again, most discussions seem to have missed my point that this is not a
> technical issue, but something of a much broader significance.
>
>
> [EMAIL PROTECTED] wrote:
>
>>I may have missed something in context here but I do not believe this
>>is some conspiracy.
>>
>>Setting a hostname is something normal in DHCP operation. It is a
>>configuration option on a DHCP server and overrideable option on a DHCP
>> client.
>>
>>This option is useful if you need it but can be equally a pain if you
>>don't. That is why it can be overriden on the client end.
>>
>>Here is a typicial config entry in a DHCP server and one I use on my
>>local network:
>>
>> host printsrv {
>>option host-name "printsrv.sux2beu.ml.org";
>>hardware ethernet 00:A0:C9:95:53:DD;
>>fixed-address 192.168.0.20;
>>}
>>
>>In fact I use this configuration for a majority of workstations on my
>>local network (not the servers) as I think its easier to set the
>>hostname on windows machines that way without having to rely or hope
>>that the netbios name is set the same which can cause many problems.
>>This works great and helps maintain your hostnames and DNS records in
>>sync across your network like Whatever stated.
>>
>>You CAN override or basically 'ignore' this DHCP server sent
>>parameter on the client end with the -h and -R.
>>
>>There are more DHCP server options that can be sent down the wire to
>>the client. Anyone interested read the dhcpd and dhcpcd man pages or
>>search Google for "dhcpd.conf" and "options" search goolge or even the
>>dhcpd man page
>>
>>On Mon, 23 Dec 2002, W. Wayne Liauh wrote:
>>
>>
>>
>>>Changing our own config is no problem. But the main issue is, should
>>>we allow a public utility type dhcp to change our hostname?
>>>
>>>
>>>
>
>
> ___
> LUAU mailing list
> [EMAIL PROTECTED]
> http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
Again, most discussions seem to have missed my point that this is not a
technical issue, but something of a much broader significance.
[EMAIL PROTECTED] wrote:
I may have missed something in context here but I do not believe this is
some conspiracy.
Setting a hostname is something normal in DHCP operation. It is a
configuration option on a DHCP server and overrideable option on a DHCP
client.
This option is useful if you need it but can be equally a pain if you
don't. That is why it can be overriden on the client end.
Here is a typicial config entry in a DHCP server and one I use on my
local network:
host printsrv {
option host-name "printsrv.sux2beu.ml.org";
hardware ethernet 00:A0:C9:95:53:DD;
fixed-address 192.168.0.20;
}
In fact I use this configuration for a majority of workstations on my
local network (not the servers) as I think its easier to set the hostname
on windows machines that way without having to rely or hope that the netbios name
is set the same which can cause many problems.
This works great and helps maintain your hostnames and DNS records in
sync across your network like Whatever stated.
You CAN override or basically 'ignore' this DHCP server sent
parameter on the client end with the -h and -R.
There are more DHCP server options that can be sent down the wire to the
client. Anyone interested read the dhcpd and dhcpcd man pages or
search Google for "dhcpd.conf" and "options" search goolge or even the
dhcpd man page
On Mon, 23 Dec 2002, W. Wayne Liauh wrote:
Changing our own config is no problem. But the main issue is, should we
allow a public utility type dhcp to change our hostname?
Re: [luau] dhcp-146-41
[EMAIL PROTECTED] wrote: Setting a hostname is something normal in DHCP operation. It is a configuration option on a DHCP server and overrideable option on a DHCP client. I agree. There is nothing wrong with dhcp having this capability, but we have a very serious privacy breach when an (at least) pseudo public utility company like RoadRunner turns it on.
Re: [luau] dhcp-146-41
I don't think you understand the seriousness of this issue. As I mentioned in my very first post, RoadRunner changed the host name of MY computer without my permission. (As a result, I was unable to load my printer driver even as a root.) The succeess of internet age depends on trust, i.e., whether we can trust bandwidth providers. If you think this is OK, then perhaps you should get your brain examined. Jimen, you have always demonstrated yourself as one of the more knowledgeable Linux experts on our island. I am interested in sending out a message. Nothing personal. Jimen Ching wrote: Wayne, I think you need to cool down a bit. This problem is getting to you, and it is affecting your interpersonal interactions.
Re: [luau] dhcp-146-41
I may have missed something in context here but I do not believe this is
some conspiracy.
Setting a hostname is something normal in DHCP operation. It is a
configuration option on a DHCP server and overrideable option on a DHCP
client.
This option is useful if you need it but can be equally a pain if you
don't. That is why it can be overriden on the client end.
Here is a typicial config entry in a DHCP server and one I use on my
local network:
host printsrv {
option host-name "printsrv.sux2beu.ml.org";
hardware ethernet 00:A0:C9:95:53:DD;
fixed-address 192.168.0.20;
}
In fact I use this configuration for a majority of workstations on my
local network (not the servers) as I think its easier to set the hostname
on windows machines that way without having to rely or hope that the netbios
name
is set the same which can cause many problems.
This works great and helps maintain your hostnames and DNS records in
sync across your network like Whatever stated.
You CAN override or basically 'ignore' this DHCP server sent
parameter on the client end with the -h and -R.
There are more DHCP server options that can be sent down the wire to the
client. Anyone interested read the dhcpd and dhcpcd man pages or
search Google for "dhcpd.conf" and "options" search goolge or even the
dhcpd man page
On Mon, 23 Dec 2002, W. Wayne Liauh wrote:
> Changing our own config is no problem. But the main issue is, should we
> allow a public utility type dhcp to change our hostname?
>
Re: [luau] dhcp-146-41
>Vince Hoang wrote: >>Would anyone be willing to share privately or publicly how this is done? On Mon, 23 Dec 2002, W. Wayne Liauh wrote: >I don't like you tone. Taking something out of context (in this case, >comment within a comment, even though it is my own comment) is a very >rude and very childish behavior. Wayne, I think you need to cool down a bit. This problem is getting to you, and it is affecting your interpersonal interactions. Concerning setting the hostname by the DHCP client/server, this is an expected behavior. I haven't read the DHCP RFC in a while, but I do remember it specifically allowing a hostname field in the 'ACK' message. Also, setting the hostname should have absolutely no affect on a running system, if the software is written well. If RH 8.0 is trying to install samba and apache when the cable modem is turned on, then that's a RH problem. As for networking tools not working with the hostname set, I think this is a problem with the DNS, not the hostname. No software should be looking at the hostname to determine its behavior. As for the need to set the hostname, that is done for user-friendliness. No one should be required to remember a 16 digit number to use a network. And it shouldn't matter what it is set to. If there is a software that needs localhost defined, try putting the following line in /etc/hosts. 127.0.0.1 localhost localhost.localdomain I'm sure its already there in this file. If you are still having problems, try calmly explaining what behavior you are experiencing. Explain it in as much detail as possible. You'll get more help that way. --jc -- Jimen Ching (WH6BRR) [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [luau] dhcp-146-41
On Mon, Dec 23, 2002 at 05:09:42PM -1000, W. Wayne Liauh wrote: > I don't like you tone. Taking something out of context (in this case, > comment within a comment, even though it is my own comment) is a very > rude and very childish behavior. Another misunderstanding I suppose. I'll take it off line. -Vince
Re: [luau] dhcp-146-41
I don't like you tone. Taking something out of context (in this case, comment within a comment, even though it is my own comment) is a very rude and very childish behavior. Vince Hoang wrote: Would anyone be willing to share privately or publicly how this is done? Thanks, -Vince ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
Changing our own config is no problem. But the main issue is, should we allow a public utility type dhcp to change our hostname? whenever wrote: Since RH 7.2 it changes my hostname, so I alway start dhcpcd with the -h option: dhcpcd -h myhostname eth1 add -R if you don't want it to over write your /etc/resolv.conf (I use my own cache DNS) ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
On Mon, Dec 23, 2002 at 04:36:40PM -1000, W. Wayne Liauh wrote: > "It appears that this particular RR router is doing what it is > NOT supposed to do (trying to take control of the computer but > leaving no host address; and believe me, we have reformatted > the HD several times.) Would anyone be willing to share privately or publicly how this is done? Thanks, -Vince
Re: [luau] dhcp-146-41
Since RH 7.2 it changes my hostname, so I alway start dhcpcd with the -h option: dhcpcd -h myhostname eth1 add -R if you don't want it to over write your /etc/resolv.conf (I use my own cache DNS)
Re: [luau] dhcp-146-41
The following is the comment that I sent to a kind LUAU member who responded to my question in private. I believe the situation is in a total mess (and I envy those Windows cable modem users who are being totally screwed up without an opportunity to realize it). More specifically, as per George's comment, it appears that Red Hat's dhcp client configuration allows the RoadRunner router to alter your hostname (which should be a very big no no, in light of the problems that I had experienced). OTOH, it also appears that, for very strange reasons, some RoadRunner dhcp servers (e.g., the one connected to my house) do not attempt to change the hostname. A public dhcp server is supposed to "lease" you a temporary ip address. No thing more. Anything beyond that and we may have someone committing criminal activities upon us. "It appears that this particular RR router is doing what it is NOT supposed to do (trying to take control of the computer but leaving no host address; and believe me, we have reformatted the HD several times.) "Previously this PC was running Win98 and was "on" all the time (while connected to RR). I suspect whether anyone is trying to take advantage of their vulnerability? Althogh I just don't think how this could be possible. Previously, the Win98 system had deteriorated to a stage that it was almost imoperatable (it is a very powerful system, and its owner was doing nothing but browsing and emailing)." Ray Strode wrote: Not sure why it's causing so many problems, but I can explain a little bit about how the process works on redhat. First, the computer requests an ip from the dhcp server (called DHCP request), then dhcp server returns the computer's ip address and other network information, including the dns server (called DHCP ACK [ACK is for acknowledgment]). Some time during this process the file /etc/sysconfig/network gets sourced and certain environment variables are set. If HOSTNAME is one of the environment variables to get set and it is set to something other than "" or "localhost", then the hostname of the system is set to $HOSTNAME. If HOSTNAME is not set, or it is set to "" or "localhost" then the computer performs a reverse lookup on the ip it was just given (by asking the dns server it was just told about). Whatever results from this reverse lookup is the hostname assigned to the system. If the reverse lookup fails, then the hostname is set to localhost. --Ray ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
hdon't forget that somewhere in the process the dhcp server does a mac address lookup for machine specific config items. The cool part is that my VOIP phones do a dhcp request and get fed to them a bootserver and bootfile config item. This stuff then points them to my call manager for upgrades, menus and services (forwarding, voice mail, etc). /brian chee University of Hawaii ICS Dept Advanced Network Computing Lab 1680 East West Road, POST rm 311 Honolulu, HI 96822 808-956-5797 voice, 808-956-5175 fax - Original Message - From: "Ray Strode" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 23, 2002 12:43 PM Subject: Re: [luau] dhcp-146-41 > > I noticed that, instead of the usual "localhost", the computer was > > designated, out of the blue, a name called "dhcp-146-41". It was > > subsequently concluded that this was the source of all the problems > > (including inability to install printer driver, etc.) > > > Not sure why it's causing so many problems, but I can explain a little > bit about how the process works on > redhat. > > First, the computer requests an ip from the dhcp server (called DHCP > request), then > dhcp server returns the computer's ip address and other network > information, including the dns server > (called DHCP ACK [ACK is for acknowledgment]). Some time during this > process the file > /etc/sysconfig/network gets sourced and certain environment variables > are set. > > If HOSTNAME is one of the environment variables to get set and it is set > to something other than > "" or "localhost", then the hostname of the system is set to $HOSTNAME. > > If HOSTNAME is not set, or it is set to "" or "localhost" then the > computer performs a reverse lookup on the ip > it was just given (by asking the dns server it was just told about). > Whatever results from this reverse lookup is the > hostname assigned to the system. If the reverse lookup fails, then the > hostname is set to localhost. > --Ray > > > ___ > LUAU mailing list > [EMAIL PROTECTED] > http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
I noticed that, instead of the usual "localhost", the computer was designated, out of the blue, a name called "dhcp-146-41". It was subsequently concluded that this was the source of all the problems (including inability to install printer driver, etc.) Not sure why it's causing so many problems, but I can explain a little bit about how the process works on redhat. First, the computer requests an ip from the dhcp server (called DHCP request), then dhcp server returns the computer's ip address and other network information, including the dns server (called DHCP ACK [ACK is for acknowledgment]). Some time during this process the file /etc/sysconfig/network gets sourced and certain environment variables are set. If HOSTNAME is one of the environment variables to get set and it is set to something other than "" or "localhost", then the hostname of the system is set to $HOSTNAME. If HOSTNAME is not set, or it is set to "" or "localhost" then the computer performs a reverse lookup on the ip it was just given (by asking the dns server it was just told about). Whatever results from this reverse lookup is the hostname assigned to the system. If the reverse lookup fails, then the hostname is set to localhost. --Ray
Re: [luau] dhcp-146-41
One of the reasons I never continued to use RedHat is it always says it can't find the "hostname" when I try to use Gnome. I have never had that problem with any other Linux distribution. W. Wayne Liauh wrote: Thanks Warren. What's bothering me is that I have installed dozens of Red Hat 8 with DHCP, and the hostname was always localhost.
Re: [luau] dhcp-146-41
On Mon, Dec 23, 2002 at 01:24:05AM -1000, Warren Togami wrote: > That's the default behavior of DHCP in Red Hat 8.0. It is > probably best to override that with a set hostname when you use > DHCP. However, I wasn't aware that changing hostnames like that > would cause so many problems for those services. I need to take > a closer look at this on my system. I suspect name resolution issues. Sendmail has been notorious for locking up the booting process. If the system is named localhost, name resolution should not fail. I have seen switching hostnames on systems relying on DHCP, but never thought much about why and when that happens. Does the hostname change because a hostname is not set in /etc/sysconfig/network? -Vince
Re: [luau] dhcp-146-41
Thanks Warren. What's bothering me is that I have installed dozens of Red Hat 8 with DHCP, and the hostname was always localhost. Warren Togami wrote: W. Wayne Liauh wrote: I was helping one of my partners installing Red Hat 8.0. This is a stand-alone machine with RR cable modem. I noticed that, instead of the usual "localhost", the computer was designated, out of the blue, a name called "dhcp-146-41". It was subsequently concluded that this was the source of all the problems (including inability to install printer driver, etc.) If I unplug the cable modem and re-install Red Hat, then everything would initially appear normal (i.e., it will be given the "localhost" name). However, as soon as I turn the cable modem back on, the host name would immediately change to "dhcp-146-41". And during booting or re-booting, the system would try to load sendmail and samba server, both of which were never installed. There are also other problems, including the messages of "cannot find server address dhcp-146-41" and "this system is controlled by another computer), etc. If I do the installation with cable modem on, it would automatically install sendmail and samba, even though I only checked on the "personal" packages. Anyone cares to take a crack? I have an identical system at home which never had any problem. That's the default behavior of DHCP in Red Hat 8.0. It is probably best to override that with a set hostname when you use DHCP. However, I wasn't aware that changing hostnames like that would cause so many problems for those services. I need to take a closer look at this on my system. ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] dhcp-146-41
W. Wayne Liauh wrote: I was helping one of my partners installing Red Hat 8.0. This is a stand-alone machine with RR cable modem. I noticed that, instead of the usual "localhost", the computer was designated, out of the blue, a name called "dhcp-146-41". It was subsequently concluded that this was the source of all the problems (including inability to install printer driver, etc.) If I unplug the cable modem and re-install Red Hat, then everything would initially appear normal (i.e., it will be given the "localhost" name). However, as soon as I turn the cable modem back on, the host name would immediately change to "dhcp-146-41". And during booting or re-booting, the system would try to load sendmail and samba server, both of which were never installed. There are also other problems, including the messages of "cannot find server address dhcp-146-41" and "this system is controlled by another computer), etc. If I do the installation with cable modem on, it would automatically install sendmail and samba, even though I only checked on the "personal" packages. Anyone cares to take a crack? I have an identical system at home which never had any problem. That's the default behavior of DHCP in Red Hat 8.0. It is probably best to override that with a set hostname when you use DHCP. However, I wasn't aware that changing hostnames like that would cause so many problems for those services. I need to take a closer look at this on my system.
[luau] dhcp-146-41
I was helping one of my partners installing Red Hat 8.0. This is a stand-alone machine with RR cable modem. I noticed that, instead of the usual "localhost", the computer was designated, out of the blue, a name called "dhcp-146-41". It was subsequently concluded that this was the source of all the problems (including inability to install printer driver, etc.) If I unplug the cable modem and re-install Red Hat, then everything would initially appear normal (i.e., it will be given the "localhost" name). However, as soon as I turn the cable modem back on, the host name would immediately change to "dhcp-146-41". And during booting or re-booting, the system would try to load sendmail and samba server, both of which were never installed. There are also other problems, including the messages of "cannot find server address dhcp-146-41" and "this system is controlled by another computer), etc. If I do the installation with cable modem on, it would automatically install sendmail and samba, even though I only checked on the "personal" packages. Anyone cares to take a crack? I have an identical system at home which never had any problem.
