Sorry, a bit irrelevant maybe: I upgraded my internet connection to ADSL: EthernetCard --> PPPoE --> ADSL modem. My eth card has a local 169.* IP. How can i set-up a web server? How can somebody access my web server? Thanks, antonis. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com
You''ll need a /28 or better IP address range from you ISP (at least 8 IP addresses). Of the 8, the bottom and top are gone for network and broadcast addresses. You''ll need one inside your ADSL router, one on the outside interface of your PPoE box, and one dedicated to your web server. And you will need the appropriate NAT entries setup in either an iptables or ipchains script on the PPoE box. Oh - and your PPoE box or somebody will need to supply DHCP for systems in your internal network. Don''t use DHCP for your web server. - Greg Scott -----Original Message----- From: Antonis Lazaridis [mailto:antonis_san@hotmail.com] Sent: Sunday, February 24, 2002 7:58 AM To: lartc@mailman.ds9a.nl Subject: [LARTC] Web server with ADSL Sorry, a bit irrelevant maybe: I upgraded my internet connection to ADSL: EthernetCard --> PPPoE --> ADSL modem. My eth card has a local 169.* IP. How can i set-up a web server? How can somebody access my web server? Thanks, antonis. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
On Sun, Feb 24, 2002 at 08:42:18AM -0600, Greg Scott wrote:> You''ll need a /28 or better IP address range from you ISP > (at least 8 IP addresses). Of the 8, the bottom and top > are gone for network and broadcast addresses. You''ll needeh? While not a real on-topic question, Antonis can setup a webserver just by starting one. All he needs to do is know what hus outside IP address is and if it is stable. You don''t need a /28 for that. Regards, bert -- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
On Sunday 24 February 2002 14:58, you wrote:> Sorry, > a bit irrelevant maybe: > I upgraded my internet connection to ADSL: > EthernetCard --> PPPoE --> ADSL modem. > > My eth card has a local 169.* IP. > How can i set-up a web server? > How can somebody access my web server?I have the same setup. I forward port80 from my firewall to the web-server. The web-server has a normal 169.* address. I do this with iptables : iptables -A INPUT -p tcp --dport 80 -j ACCEPT iptables -t nat -A PREROUTING -p tcp -d $EX_IP --dport 80 -j DNAT --to 192.168.1.253:80 iptables -A FORWARD -p tcp -d 192.168.1.253 --dport 80 -j ACCEPT Stef -- stef.coene@docum.org More QOS info : http://www.docum.org/ Title : "Using Linux as bandwidth manager"
Hi All, I just want to inform all HTB users that after two month of planning I finally tested new HTB algorithm which should be able to handle 50.000 packets/sec sustained even with thousands of classes. The first tests are successfull only thing which is not working correctly is ratio between borrowed bandwidth. I hope to solve it soon .. (if it can be solved at all ..) regards, devik
Maybe I made some bogus assumptions:> I upgraded my internet connection to ADSL: > EthernetCard --> PPPoE --> ADSL modem.So I was thinking there were three separate boxes: 1 - An ADSL router 2 - A PPPoE box doing firewall stuff 3 - a web server inside the LAN Next time, I''ll try to wake up a little more before typing. - Greg -----Original Message----- From: bert hubert [mailto:ahu@ds9a.nl] Sent: Sunday, February 24, 2002 9:01 AM To: Greg Scott Cc: ''Antonis Lazaridis''; lartc@mailman.ds9a.nl Subject: Re: [LARTC] Web server with ADSL On Sun, Feb 24, 2002 at 08:42:18AM -0600, Greg Scott wrote:> You''ll need a /28 or better IP address range from you ISP > (at least 8 IP addresses). Of the 8, the bottom and top > are gone for network and broadcast addresses. You''ll needeh? While not a real on-topic question, Antonis can setup a webserver just by starting one. All he needs to do is know what hus outside IP address is and if it is stable. You don''t need a /28 for that. Regards, bert -- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
Carles Pina i Estany
2002-Feb-26 00:18 UTC
Web Server with ADSL (continued) or something similar
Hi, I have tried it: iptables -t nat -A PREROUTING -p tcp -i eth2 --dport 1000 -j DNAT --to \192.168.1.2:80 And doesn''t work: carles@pinux:~$ telnet SERVER 1000 Trying IP_SERVER... And if I do it with redir command works fine. What is the problem? And the solution? My network is something like: INTERNET IP_EXT <- |Server| -> IP_INT (192.168.1.x) NAT Thank you very much! ---- Carles Pina i Estany | Nick: Pinux / Pine / Teufeus E-Mail: carles.pina@salleURL.edu / is08139@salleURL.edu / cpina@cat-linux.com http://www.salleURL.edu/~is08139/
Stef Coene
2002-Feb-26 06:32 UTC
Re: Web Server with ADSL (continued) or something similar
> I have tried it: > > iptables -t nat -A PREROUTING -p tcp -i eth2 --dport 1000 -j DNAT --to > \192.168.1.2:80 > > And doesn''t work: > > carles@pinux:~$ telnet SERVER 1000 > Trying IP_SERVER... > > And if I do it with redir command works fine. > > What is the problem? > And the solution?Have you also used the other lines I sended? You must be sure you are not blocking incoming port 1000. And you must be sure you can forward to port 80. And I miss a -d option with the ip of your firewall/ This works fine for me. This is a copy-paste from my firewall-script : iptables -A INPUT -p tcp --dport 8088 -j ACCEPT iptables -t nat -A PREROUTING -p tcp -d 192.168.1.254 --dport 8080 -j DNAT --to 192.168.1.253:80 iptables -t nat -A PREROUTING -p tcp -d $EX_IP --dport 8080 -j DNAT --to 192.168.1.253:80 iptables -A FORWARD -p tcp -d 192.168.1.253 --dport 8080 -j ACCEPT $EX_IP is the internet-ip of my firewall. 192.168.1.254 is the LAN-ip of my firewall 192.168.1.253 is the ip of my webserver I hope this can help. Stef