Topic: cgi-bin problems

[craig halliday]

I have a problem with cgi-bin access on a e-smith 4.0 box.

Recently I installed a script in /home/e-smith/files/primary/cgi-bin and tested it via http://192.168.0.69/cgi-bin (the address of the netcard attached to the local network) it worked fine.  

Now if I try and test the same script via the external interface connected to the net I cannot access that script.  Any access to http:///cgi-bin  actually points to /home/e-smith/files/primary/html/cgi-bin   I cannot run scripts from there(not that I want to)

Why the difference between the two interfaces?

It looks like the cgi-bin access has been disabled for the external interface for some reason, I dont know where to look to change this.

Any ideas?

[Garret]

I'm just going to give a shot in the dark here....

I run CGI scripts like crazy on my e-smith server. I have had no problems unless they were mine. I think you're getting the /html/cgi-bin thing bacause your on the url side of things your e-smith server automatically looks for your html directory (which it should) then of course the cgi-bin of that directory. Insted of using your ip address try using a url address http://www.your_domain.com/cgi-bin/script.pl.

Works for me.

Garret

[craig halliday]

The problem is only experienced when the server is accessed from the net.  If I access the server from the internal network the CGi-bin works fine whether I access it via the DNS name or the IP address.

It seems like some security setting somewhere.  I just have no idea where to look.

[LowellF]

Take a look at the permissions within the script itself.  I've seen some really strange tags from time to time that keep unwanted users out of the scrupts path.  It's worth a look any way.

[Yves LAVANANT]

I've exactly the same problem, and I didn't find any solution yet. Did you?

I insist on the fact that it works from the inside network => I don't think it's a protection problem on the CGIs.
The logs show that httpd looks for .../html/cgi-bin/.... The ScriptAlias /cgi-bin directive seems to have no effect.
Why?

I use a pptp (Sort of ppp over Ethernet) connexion. Are you in a similar case?

Regards,
Yves

[Gordon Rowell]

Yves LAVANANT wrote:

> I've exactly the same problem, and I didn't find any solution
> yet. Did you?

Have you updated to e-smith-4.0.1?

> I insist on the fact that it works from the inside network
> => I don't think it's a protection problem on the CGIs. The
> logs show that httpd looks for .../html/cgi-bin/.... The
> ScriptAlias /cgi-bin directive seems to have no effect. Why?
> [...]

i-bays were not supported on the external interface for dynamic
addresses prior to 4.0.1

Gordon

[Yves LAVANANT]

Gordon Rowell wrote:

>
> Have you updated to e-smith-4.0.1?

Yes, I have, but I didn't try 4.1b1 yet.

>
> i-bays were not supported on the external interface for dynamic
> addresses prior to 4.0.1

My understanding of the problem is this one...
It seems e-smith understand two case:
- dialup with dynamic address
- dedicated with an external interface and a static public address.

And I am in a third one: external interface with static private address and a dynamic public address over it (PPoE). It doesn't seem to be supported by the httpd configuration...
I configured e-smith in dedicated mode (because I have an external card). And give a private IP address for the external card (with a gateway! This is important... except for a private network). E-smith use this external address for the httpd configuration.
=> NameVirtualHost 10.0.0.10
and
=>

I have change this to:
=> NameVirtualHost *
=>
( because the external address can change )

And now it works... But I might be wrong in my comprehension.
Will e-smith 4.1b1 solve this?
Let me know, and thanks again.

> Gordon
Yves

[Gordon Rowell]

Yves LAVANANT wrote:

> Gordon Rowell wrote:
>
> > > Have you updated to e-smith-4.0.1?
>
> Yes, I have, but I didn't try 4.1b1 yet.

4.1 beta 1 is a developer release only. It should only be discussed
on the devinfo mailing list at this stage.

> > > i-bays were not supported on the external interface
> for dynamic > addresses prior to 4.0.1
>
> My understanding of the problem is this one... It seems e-smith
> understand two case: - dialup with dynamic address - dedicated
> with an external interface and a static public address.

Until 4.0.1, when they were (mostly) merged.

> And I am in a third one: external interface with static private
> address and a dynamic public address over it (PPoE).
> [...]

PPPoE is not supported under 4.0 or 4.0.1 The contributed add-on
works, but probably suffers from exactly the problem you have seen.
The module needs some work to be properly supported.

> And now it works... But I might be wrong in my comprehension.

No, your fix is fine, but means that virtual hosts are not tied to
interfaces, so is not the way we need to solve it in the longer term.

>   Will e-smith 4.1b1 solve this?

The official 4.1 release will support PPPoE and this will work. We
don't make any statements about how functional the developer
preview is at this stage.

>   Let me know, and thanks again.

Gordon