Koozali.org: home of the SME Server

router

frej

router
« on: January 13, 2003, 07:31:40 PM »
hi,

I got from my ISP a routeur instead of the traditional modem. So I set up my e-smith 5.5 box to be server-only instead of a dedicated server and gateway.
The routeur is set to have a default server which is my sme box.
I have access to the internet, so does my sme, but if I try to go on any domain hosted on the sme, it doesn't work.

If anyone has an idea on what's going on, please tell me...

Frej.

Andrew Rosenau

Re: router
« Reply #1 on: January 13, 2003, 08:02:25 PM »
What does work? The DNS? or it wont go to your server when you type in the IP address in the browser field? Or does SME give you an error message? We need more information in order to start diagnosing your problem.

frej

Re: router
« Reply #2 on: January 14, 2003, 03:50:27 PM »
The server gets the requests from the outside (it is correctly recognized as the default server of the router). But I can't get anything to work.

For example, when I type in my browser www.mydomain.com, nothing shows up: it is unreachable, yet on the same network as me. Whereas from the outside, it is reachable. Moreover when I type in the browser www.mydomain.com/myIBay, I get nothing in LAN, and the outside network just get www.mydomain.com page, not the ibay.
From the WAN, if I try to connect to the cvs, I get an error; if I connect through SSH, I get service unavailable, while it works very well from LAN.

Yesterday, as nothing was working correctly, I went back to the original configuration. Today, nothing works, even webmail... this is very annoying for me, as my server is the mail server for my whole family... and it seems to be down.

Let me just add a small word: HELP !!

Frej.

Nate

Re: router
« Reply #3 on: January 14, 2003, 08:27:34 PM »
I had a remotely similiar problem recently with a cable router.  I ended up setting up SME as a server and gateway and hooking the external NIC on the SME to the cable router(nothing else hooked the router) and the internal NIC to the lan.  Now everything on the LAN is handled by the SME server--the bonus for me was the squid proxy that stores up web stuff for the 60 users and more control of dynamic assigned IP's and such.

Bill Talcott

Re: router
« Reply #4 on: January 14, 2003, 09:12:44 PM »
frej wrote:
>
> I got from my ISP a routeur instead of the traditional modem.
> So I set up my e-smith 5.5 box to be server-only instead of a
> dedicated server and gateway.
> The routeur is set to have a default server which is my sme
> box.
> I have access to the internet, so does my sme, but if I try
> to go on any domain hosted on the sme, it doesn't work.

Your router is doing port-forwarding from itself to the SME. Most (All? I think it has to do with routing the outgoing requests too.) NAT routers can only forward ports from the external interface. You need to access the SME via its LAN IP, not the router's IP (forwarded to the SME).

If you have your clients set up to use the SME for DNS, it should catch the requests for stuff hosted on the SME, and never even bother with outside DNS.

http://forums.contribs.org/index.php?topic=15327.msg58859#msg58859 describes this, and sounds like the same thing you're experiencing. See my second reply for a diagram of what should be happening with DNS.

Is there any way to configure the router to not do anything, and just let the SME have the public IP? That's probably going to be the easiest way to get things working, if you can...

Boris

Re: router
« Reply #5 on: January 14, 2003, 10:14:55 PM »
If EVERYTHING forwarded to SME anyway, try to enable on router transparent bridging (sometimes referred as "full bridge") mode and transfer your router's public IP to SME (server-gateway mode). You may need to contact your ISP for this.
Personally I would (and have) done for home is to forward only ports needed for public services (80, 443,22 etc) and leave server inside your network in server-only mode. Use your server for DNS or use "hosts" file (with pointers to your server's private IP) on you workstation to resolve you domain internally.

frej

Re: router
« Reply #6 on: January 15, 2003, 02:53:27 AM »
First I would like to thank everyone : I'll test those configuration as soon as I can.

And I would also like to add something weird happened to me : the configuration of the server was "blocked" in Private server and gateway, after some config changes, whereas I never used this option. To reconfigure properly, I had to effectively set the server in private server and gateway mode and then reboot and go back to the basic server and gateway mode.

Well I'm now back in working state, and I'll tell you more when changes to the config are done

thx again.