Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Kevin Lim on September 06, 2000, 08:20:48 AM
-
i worked on this all day and can't figure it out
my ibays are no longer accessible from the internet, they are still accessible from my internal LAN
i tried applying the base patch
i tried going to each ibay in e-smith-manager and going to modify and resaving
what do i try next? should i delete all of them and then remake them? i don't have that much stuff in them yet so this won't take to long.
if that doesn't work is there some config files i should check, i assume this must be a problem with apache, i can still ftp to the ibays from LAN and internet
thank you for any ideas
-
i deleted one of the ibays and created a new one with a different name, still no access from internet (says the page cannot be found), but from LAN it asks for the password, works fine.
this has to be an apache problem, i think
-
ok, i figured out where the logs are, this is from my error_log
i requested a page sch.htm, from two different isp's, below are the error messages result:
[Wed Sep 6 14:30:04 2000] [error] [client 32.97.211.2] File does not exist: /home/e-smith/files/primary/html/iall/sch.htm
[Wed Sep 6 15:10:27 2000] [error] [client 216.126.169.224] File does not exist: /home/e-smith/files/primary/html/iall/sch.htm
looks like it is looking in the wrong place?
iall/sch.htm is under /home/e-smith/files/ibays, not /primary/html
so apache is mixed up? how does apache know where ibays are in relation to /home/e-smith/files?
-
pretty sure i found out what is happening, i don't know how to fix it.
i opened the httpd.conf file in /etc/httpd/conf and looking through i see a section titled:
# Aliases for primary web site and virtual domains (generated
# automatically by e-smith management software).
this has a section for localhost 127.0.0.1 that looks right
a section for my LAN 192.168.0.1 (it is working for my internal users) that looks right
the third section is for the outside world? right?
NameVirtualHost 119.214.40.69
well since i am on dhcp to the internet, my server (external, internet) ip changes randomly, so last week when it was working, my ip was 119.214.40.69, now it is xxx.xxx.xxx.xxx, so effectively, i have no virtual host section for my working ip.
how do i fix it? when is this ip loaded into httpd.conf?
the beginning of the file says:
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# e-smith server and gateway software. Instead, modify the source
# template in the /etc/e-smith/templates directory. For more
i guess i will look through the templates to see where the ip is pulled from
is this going to be a problem everytime i change ip's? or should the ip not really be in that file at all?
-
i believe i have this solved, at least why it is happening (still got to fix it)
i am using e-smith in a non-standard fashion, it is designed to run as a dialup or dedicated. dialup assumes the ip will be dynamic, dedicated assumes the ip will be static. i have dsl with dhcp. so i am set as dedicated (assumes static ip) but have a dynamic ip. the trick to get PPPoE to work was to setup as dialup to get the yi.org username and password in, then switch to dedicated.
well now that my ip has changed (changes on average once a day for various reasons) my old ip is "hardcoded" into the config, httpd.conf (built from the templates? right?)
i look in templates and find 80Aliases00. inside it looks like it is grabbing my external ip address if i am set to dedicated and server/gateway. this file is run to build the httpd.conf file? this is why my external "old" ip is stuck in httpd.conf, hhmmm......
how to fix? guess i will try copying the 80Aliases00 files to templates-custom and mess with it. hhmmm.....
i don't see how this is going to work, how does it work correctly for dialup users? (accesstype not dedicated?)??
-
logon to the console and do
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf
then do
service httpd restart
that should get the proper configuration into the httpd.conf file and the restart apache.
now as to why it didn't do that in the first place - I don't know.
-
that will rebuild the httpd.conf file, but what happens next time my ip changes?
are you suggesting i will have to do this manually each time my ip changes?
that won't work, i will have to add this to the script that updates my ip to my dynamic dns service or else my reliability will be too poor
thanks for the clarification
-
clarification
ExternalIP is set in the configuration file, it isn't "read" in from the actual current setting of eth1 (or whichever is your external nic)
so when i did the above, it didn't update httpd.conf from my current dynamic ip
i will change the configuration file i guess but this isn't a permanent fix
can't i change the 80Aliases00 perl script to somehow read in the current actual ip assigned to eth1?
i guess i will try that
i might have to just buy a hardware router :(
-
Kevin Lim wrote:
> ExternalIP is set in the configuration file, it isn't
> "read" in from the actual current setting of eth1 (or
> whichever is your external nic)
Unless you have a dedicated static IP configuration, it has to be set dynamically in the configuration. This is done automatically if you have a dedicated connection and are using DHCP, but is not currently done for dialup connections. IIRC, you are using PPPoE which is effectively a dialup connection.
If you do:
cp /etc/e-smith/events/ip-change/* /etc/e-smith/events/ip-up
and your problem should be solved.
Regards
Charlie
-
this mostly fixed it, it sent the new ip to yi.org, but didn't update /etc/home/configuration with my new external ip. i tried manually running the S15set-external-ip perl script, and got this error:
Use of uninitialized value at /usr/lib/perl5/site_perl/5.005/esmith/config.pm line 121
looking in configuration afterwards, ExternalIP=
it is blank, that might explain why the error?
does this pull the ip from eth1 (external nic)? if so this explains the problem. my dynamic ip is attached to ppp0 not eth1
-
> If you do:
> cp /etc/e-smith/events/ip-change/* /etc/e-smith/events/ip-up
> and your problem should be solved.
It is :-) Dyndns updates, but on reboot httpd ans squid don't stop. Have to reset :-(
(esmith 4.1 rc4)