Topic: Ghost IP

[tb]

Interestingly, my e-smith box appears to have a "ghost" IP listening for connections. I have not investigated this completely, but upon initial inspection, can find no reason for this behaiour --

my local network is a 24 bit RFC 1918 network (192.168.0.0/24)

a 'netstat -a' shows an address of 192.168.65.17 listening on ports 80 and 443.
(This subnet (192.168.65) has never existed anywhere within my infrastructure)

I have not configured any "ibays" on this box, but I'm wondering, is there maybe a configuration detail left in place on the install iso that is instructing my box to listen on an IP that was a default in some other environment?

Any clues as to the location of this erroneous setting?

thanks,
-tb

[tb]

found my own problem!

i hadn't dug down far enough into the /etc/httpd/conf/httpd.conf file to see the following directives:

Listen 192.168.65.17:80
Listen 192.168.65.17:443

anybody know why these were there in the first place?

-tb

[Scott Smith]

> i hadn't dug down far enough into the
> /etc/httpd/conf/httpd.conf file to see the following
> directives:
>
> Listen 192.168.65.17:80
> Listen 192.168.65.17:443
>
> anybody know why these were there in the first place?

Assuming 4.1.2...

I'm guessing your are running in server only mode. The ExternalIP that would be used in a gateway mode remains set (to the default if you've never messed with it, or to whatever the last value you used was) in the configuration file. There is a bug that allows ExternalIP templates to be expanded even though there is no external interface. Hence the entries in httpd.conf for the non-existant interface.

[tb]

cool...

that answers my question even better.

do you know of any other 'residual' left in place for the external interface or from gateway mode that may also be buried in an active configuration file? if so, i'd love to know, as i'm trying to prune this box down as much as possible...

thanks...

-tb

[Scott Smith]

You could have primary and secondary DNS entries floating about. In a nutshell, if you setup the server in dialup mode, define the pri/sec DNS, then change the server back to server only or server/gateway dedicated mode, the pri/sec DNS entries will not be blanked. If you take a look at the named.conf template, specifically 15forwarders, you'll see that non-blank pri/sec DNS entries will get expanded into the DNS config.

Bug? Maybe. But it also comes in handy if you NEED to specify a DNS forwarder.

You can stop the template expansion by blanking the entries in the configuration file. Something like:  /sbin/e-smith/db configuration set PrimaryDNS ""

Are there others like this? Maybe. These are the only two that I know of.

[Ahmad Hamzah]

Hi Scott,

I' having a similar problem. I changed my server setting from server and gateway to server only. Then httpd would not start because there were duplicate "Listen" and "NameVirtualHost" and "VirtualHost" entries. For example:

Listen 127.0.0.1:80
Listen 202.x.x.x:80
Listen 202.x.x.x:80 --> duplicate
.
.
Listen 127.0.0.1:443
Listen 202.x.x.x:443
Listen 202.x.x.x:443 --> duplicate
.
.
NameVirtualHost 127.0.0.1:80

...


NameVirtualHost 127.0.0.1:80 --> duplicate
--> duplicate
...


NameVirtualHost 202.x.x.x:443

...


NameVirtualHost 202.x.x.x:443 --> duplicate
--> duplicate
...


When I removed the duplicate lines, httpd runs OK. What caused it? How do I fix it w/o reinstalling? The template seems to generate the entries from a list of IP addresses and virtual hosts but I'm not sure it is getting the list from.

Appreciate for your help.

ash.