Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
10-29-2004, 02:00 PM
|
#1
|
Member
Registered: Sep 2004
Distribution: Mandrake 10
Posts: 48
Rep:
|
Server from inside LAN
Now I have my linux internet gateway going, I'm thinking of setting up a web server. This is what my LAN looks like at the moment:
Code:
--------------
| | -- 192.168.0.1
internet -- | 192.168.0.10 | -- 192.168.0.2
| | -- 192.168.0.20
| | -- 192.168.0.21
--------------
Is is possible to run apache on say, 192.168.0.1, but so it can be 'seen' from the internet?
|
|
|
10-29-2004, 02:12 PM
|
#2
|
Member
Registered: Mar 2004
Location: Boston, MA
Distribution: SuSE Linux Open/Enterprise, Red Hat, Ubuntu
Posts: 147
Rep:
|
You can have your webserver visible on both internal/external networks. You will have to add the IP address going to the internet/modem to your DNS record. Doing that will allow the domain to be resolved by the DNS. Apache will then use IP address that was used to resolve the domain, and forward pages to the requesting computer.
DNS config  not the exact configuration)
A 192.168.0.1 ( IP used for the internal network)
A 138.53.23.1 (IP address assigned to the external NIC. This could be private if your modem is also a router that uses private IP addressing)
When you finish editing the DNS configuration restart apache, then type httpd -s or if your using apache 2 httpd2 -s
This will list the IP addresses that apache will respond to.
|
|
|
10-29-2004, 02:14 PM
|
#3
|
Member
Registered: Oct 2004
Distribution: Mandrake, DSL, SuSE, RedHat
Posts: 71
Rep:
|
Sure it is 
You need to configure NAT/PAT on your router.
You have to redirect anything comming from the web to the TCP port 80 of you router to your PC where you webserver is running.
Check out your router's doc, it should tell you how to. I can give you an example I did with mine if you want
|
|
|
10-29-2004, 02:20 PM
|
#4
|
Member
Registered: Oct 2004
Distribution: Mandrake, DSL, SuSE, RedHat
Posts: 71
Rep:
|
This will probably interest you ==> http://www.dyndns.org/services/dyndns/
You can freely register a hostname for you webserver there. Sth like mywebserver.linuxhome.org
So that you can give your friends sth else than a lame IP@ they'll never remember.
Note that if you didn't ask you ISP for a static IP you'll have to update it on the site regularly.
|
|
|
10-29-2004, 02:27 PM
|
#5
|
Member
Registered: Sep 2004
Distribution: Mandrake 10
Posts: 48
Original Poster
Rep:
|
Thing is it's not really a router. It's just a gateway... or is that the same thing? I don't have any DNS servers set up either. Sorry, but I'm not exactly a networking expert!
|
|
|
10-29-2004, 02:40 PM
|
#6
|
Senior Member
Registered: Sep 2002
Location: CA
Distribution: openSuSE, Cent OS, Slackware
Posts: 1,131
Rep:
|
iptables -t net -A PREROUTING ! -i $EXT_IFACE -p tcp --destination-port 80 -j DNAT --to 192.168.0.1:80
Er something of this nature to forward all requests from the external iface to the internal machine. I just copied pasted this from "Linux Server Hacks"
|
|
|
10-29-2004, 02:49 PM
|
#7
|
Member
Registered: Oct 2004
Distribution: Mandrake, DSL, SuSE, RedHat
Posts: 71
Rep:
|
You don't need no local DNS server if you use the service provided on the site I gave you. They do it for you. They match yourwebserver.linuxhome.org (in my ex  to the public IP address (provided by you ISP) of your router/gateway (whatever, doing the same job).
It works like this:
Internet <=====> Public IP of router --- 192.168.0.10 <======> local LAN
People out there on the web only see you public IP, there is no way they can see 192.168.x.x IP. So each connection from the web to you local LAN will use you gateway's public IP address.
Each service you wanna provide use a diferent TCP port number like for a web server, HTTP uses port 80 (FTP is 21, SMTP (email) use 25 etc...).
So to allow people from the net to reach the port 80 of your PC (the one with the webserver), you need to redirect all the connection reaching the public IP of your gateway on the port 80 to the IP of your webserver.
micxz post up there is showing you how to do it.
Hope my extra explanation will help you understand it 
|
|
|
11-02-2004, 04:57 PM
|
#8
|
Member
Registered: Sep 2004
Distribution: Mandrake 10
Posts: 48
Original Poster
Rep:
|
Yes, that's great. Thanks a lot!
|
|
|
01-08-2005, 10:34 AM
|
#9
|
Member
Registered: Sep 2004
Distribution: Mandrake 10
Posts: 48
Original Poster
Rep:
|
Quote:
iptables -t net -A PREROUTING ! -i $EXT_IFACE -p tcp --destination-port 80 -j DNAT --to 192.168.0.1:80
|
Actually when I said that, I couldn't try it - I just presumed that it was right
I've finally got round to putting a monitor on the computer. But when I type it, I get told that the -p command 'contains wierd characters' 
|
|
|
01-08-2005, 06:07 PM
|
#10
|
Senior Member
Registered: Sep 2002
Location: CA
Distribution: openSuSE, Cent OS, Slackware
Posts: 1,131
Rep:
|
"contains wierd characters" Is that the error?
|
|
|
01-08-2005, 06:11 PM
|
#11
|
Member
Registered: Sep 2004
Distribution: Mandrake 10
Posts: 48
Original Poster
Rep:
|
Yes, that is the error 
|
|
|
01-08-2005, 06:20 PM
|
#12
|
Senior Member
Registered: Sep 2002
Location: CA
Distribution: openSuSE, Cent OS, Slackware
Posts: 1,131
Rep:
|
You are doing this on the gateway computer right? Please paste what you have here.
|
|
|
01-08-2005, 06:25 PM
|
#13
|
Member
Registered: Sep 2004
Distribution: Mandrake 10
Posts: 48
Original Poster
Rep:
|
Yes, 192.168.0.10. Post what exactly?
|
|
|
01-08-2005, 06:33 PM
|
#14
|
Senior Member
Registered: Sep 2002
Location: CA
Distribution: openSuSE, Cent OS, Slackware
Posts: 1,131
Rep:
|
Copy paste the whole line you typed and the error. I'm not sure how else to help.
|
|
|
01-08-2005, 06:46 PM
|
#15
|
Member
Registered: Sep 2004
Distribution: Mandrake 10
Posts: 48
Original Poster
Rep:
|
Okay, I typed:
iptables -t net -A PREROUTING ! -i $EXT_IFACE -p tcp --destination-port 80 -j DNAT --to 192.168.0.1:80
And the computer said:
Warning: wierd character in interface '-p' (no aliases, :, ! or *)
Bad argument 'tcp'
|
|
|
All times are GMT -5. The time now is 01:15 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|