Topic: ibays

[Stone Linton]

If we set up an ibay for say, me, called "stone" then we have a new directory created called "stone" with subfolders of "cgi, files, and html".  In addition, there is the default, "Primary" with the same subfolders.  Is "stone" created under "Primary"'s "html" folder?  If we use "www.domainname.com" and hit "Primaryhtml" then how is it that we use "www.domainname.com/stone" and hit the "Stone" directory?  If there was a "bob" folder under "Primaryhtmlob" then we could use "www.domainname.com/bob" and get that, right?
 
I don't get these ibays at all.  My problem is I've created on, can access it from my network, but not from the internet.  It comes back with a 404 error.
 
What should my ibay settings be for 4.0b6 to enable an ibay full access for network, password access for internet?  Alternatively, full access for network, and read access, no password, for internet?

[Paul Nesbit]

Hi Stone,

     Congratulations, you've found a bug!  I'll first answer your questions then explain how you can work around this bug temporarily until we release a fix.

Stone Linton wrote:

> If we set up an ibay for say, me, called "stone" then
> we have a new directory created called "stone" with
> subfolders of "cgi, files, and html".  In addition,
> there is the default, "Primary" with the same
> subfolders.  Is "stone" created under
> "Primary"'s "html" folder?

No.  The i-bay "stone" and associated folders (html, cgi and files) is created under /home/e-smith/files/ibays/stone.


> If we use
> "www.domainname.com" and hit "Primaryhtml"
> then how is it that we use "www.domainname.com/stone"
> and hit the "Stone" directory?  

Have a look at /etc/httpd/conf/srm.conf - you'll see how aliases are used.  Note you should not make any changes to this file.  

> If there was a
> "bob" folder under "Primaryhtmlob" then we
> could use "www.domainname.com/bob" and get that,
> right?

Right.  

> I don't get these ibays at all.  My problem is I've created on,
> can access it from my network, but not from the internet.  It
> comes back with a 404 error.

This is a result of a bug in the e-smith software that we are looking into right now.  The bug will only affect clients using DHCP to obtain an IP for the external interface.  For a quick workaround, follow these steps:

1) find out what the assigned IP address is. To do this, run the command ifconfig (interface configuration) on the e-smith server and gateway.  You should be able to determine which interface is external and what it's IP addy is.

2) Reconfigure the e-smith server and gateway to use this IP as a static IP address.

You will now be able to access you i-bays from the outside world.  I am assuming for the moment you are using the server and gateway in dedicated mode.  I realise this isn't the best fix, just a temporary workaround.

Some cable-modem access providers require that you must use DHCP.  If this is your case, set the e-smith server and gateway back to using DHCP - more than likely will be assigned the same IP and your i-bays should work.

As soon as we fix the problem we'll post it on the developers mailing list.  Thanks for pointing this out!

pkn