PPPoE ruined my servers, HELP!

I have had bellsouth ADSL for years, with a bridged ethernet connection since
it first came out. I setup my linux box with apache, sendmail, ipop3, and
vsftpd. I use no-ip.com for DNS and MX record for my FQDN and life was
grand...

Tonight while surfing the web, the internet "just stopped". Dialup would work
but not ADSL. I pulled the ethernet cable from my Red Hat 9 box and plugged
the Westell Wirespeed ADSL modem into the XP box, and then called tech help
to see what the problem is. (Bellsouth will not help you if you are running
linux, have to plug the modem into an XP box to troubleshoot the ADSL.)

The tech guy made me shut down everything and reset the modem. This will
default the modem back to PPPoE, I had it set for bridged ethernet. We
accessed the modem from IE and he told me to log in. This should not work
with bridged ethernet. It worked. I hung up. I put the modem back into
bridged ethernet and no dice. The bastards pulled my bridged ethernet away
and put me on PPPoE. <Sob!>

This really sucks because now the modem is going to steal my IP address and
give me a NAT address and that would be the end of the servers. The modem
does have an IP passthrough feature but by trying this, I did not get a valid
IP address on my linux box. Have to configure it manually with an IP address
and PPPoE IP addresses do change all the time so this will not work. Who
knows, maybe it would work, I have my redhat setup for DHCP connection, would
have to put everything in manually to use IP passthrough, I think.

So I leave the modem as bridged ethernet and plug it back into the linux
server/gateway/router and install roaring penguin PPPoE. It installs like a
breeze and is up and running in no time. I got my net back on local LAN and
for the linux machine. I update the IP address at no-ip.com for the DNS
(There is a DNS updater client running on the linux box for this purpose, but
not sure how it will work now with PPPoE, might have to reconfigure it.)

ifconfig now gives my IP address under device ppp0 and no longer for eth0. I
try to reach my web server with my FQDN, times out. I try to reach it with my
IP address, times out. I ping my domain, ftp.domain, and mail.domain. They
all time out, althoug ping does report the IP address accuratly. My mail does
not work, my ftp server does not work, and my web server does not work, they
all time out now.

What the heck is going on here? Am I doomed with PPPoE or is it possible to
make all of the servers work again? Somebody please help, I am crying a river
over here, this really sucks!

--
~Ohmster

On Wed, 25 Feb 2004 06:26:15 GMT, Ohmster <(E-Mail Removed)> wrote:
> I have had bellsouth ADSL for years, with a bridged ethernet connection since
> it first came out. I setup my linux box with apache, sendmail, ipop3, and
> vsftpd. I use no-ip.com for DNS and MX record for my FQDN and life was
> grand...
>
> Tonight while surfing the web, the internet "just stopped". Dialup would work
> but not ADSL. I pulled the ethernet cable from my Red Hat 9 box and plugged
> the Westell Wirespeed ADSL modem into the XP box, and then called tech help
> to see what the problem is. (Bellsouth will not help you if you are running
> linux, have to plug the modem into an XP box to troubleshoot the ADSL.)

(snip about switching from DHCP to PPPoE)

> So I leave the modem as bridged ethernet and plug it back into the linux
> server/gateway/router and install roaring penguin PPPoE. It installs like a
> breeze and is up and running in no time. I got my net back on local LAN and
> for the linux machine. I update the IP address at no-ip.com for the DNS
> (There is a DNS updater client running on the linux box for this purpose, but
> not sure how it will work now with PPPoE, might have to reconfigure it.)

You can run the no-ip.com update client once from /etc/ppp/ip-up (or
ip-up.local) which will automatically run it whenever you get a pppoe IP.
For example: /usr/local/bin/noip2 -i $4

> ifconfig now gives my IP address under device ppp0 and no longer for eth0. I
> try to reach my web server with my FQDN, times out. I try to reach it with my
> IP address, times out. I ping my domain, ftp.domain, and mail.domain. They
> all time out, althoug ping does report the IP address accuratly. My mail does
> not work, my ftp server does not work, and my web server does not work, they
> all time out now.
>
> What the heck is going on here? Am I doomed with PPPoE or is it possible to
> make all of the servers work again? Somebody please help, I am crying a river
> over here, this really sucks!

Did you update your firewall for the change from eth0 to ppp0? Also you
should update it from /etc/ppp/ip-up (or ip-up.local) so your firewall
also updates if your IP changes. Works for me with no-ip.com names for
sshd, smtp and www (vhosts), but I am on SBC Yahoo which does not block
any ports (except blaster port 135).

One other note if an smtp server is port forwarded behind a router
(instead of on the router) is to change its LAN nic to match mtu of your
pppoe connection (typically mtu 1492 max due to 8 byte pppoe header). But
do NOT change the mtu of eth to bridge/modem.

--
David Efflandt - All spam ignored http://www.de-srv.com/

(E-Mail Removed) (David Efflandt) wrote in
news:(E-Mail Removed):

> You can run the no-ip.com update client once from /etc/ppp/ip-up (or
> ip-up.local) which will automatically run it whenever you get a pppoe
> IP. For example: /usr/local/bin/noip2 -i $4

I updated no-ip at the web site, all servers work but apache times out now if
browsed by using the FQDN, I can access apache by browsing as http://<the
actual inet IP address>

I did change the no-ip.conf to use ppp0 as the device, this should work now.


> Did you update your firewall for the change from eth0 to ppp0? Also you
> should update it from /etc/ppp/ip-up (or ip-up.local) so your firewall
> also updates if your IP changes. Works for me with no-ip.com names for
> sshd, smtp and www (vhosts), but I am on SBC Yahoo which does not block
> any ports (except blaster port 135).

When I installed roaring penguin adsl, I choose NONE for a firewall and am
using firestarter. Firstarter bitched about starting so I changed the
outgoing device to ppp0, seems to work now. Also, adsl was starting after
firestarter during boot so I changed the S number of the adsl script in
/etc/rc.d/rc3.d to make adsl come up first, then firestarter. All of this is
very good but I still cannot access my web server now by using the domain
name. Everything else does work with domain name such as ssh, ftp, and mail.
I put domain, www.domain, and ftp.domain in a group at no-ip so that they can
be updated together.

Since web server can be accessed by IP but not by domain name, perhaps there
is something wrong with the setup now at no-ip? I have the www part at no-ip
set as DNS Host (A), there are other options such as round robin, cname, also
port 80 redirect and web redirect. Could something be wrong here?

> One other note if an smtp server is port forwarded behind a router
> (instead of on the router) is to change its LAN nic to match mtu of your
> pppoe connection (typically mtu 1492 max due to 8 byte pppoe header).
> But do NOT change the mtu of eth to bridge/modem.
>

Huh? Not using a router, set ADSL modem as bridged and run roaring pengiun to
connect. smtp server seems to be working fine.

Thanks for your help.

--
~Ohmster

On Wed, 25 Feb 2004 13:51:13 +0000, Ohmster wrote:

> (E-Mail Removed) (David Efflandt) wrote in
> news:(E-Mail Removed):
>
>> You can run the no-ip.com update client once from /etc/ppp/ip-up (or
>> ip-up.local) which will automatically run it whenever you get a pppoe
>> IP. For example: /usr/local/bin/noip2 -i $4
>
> I updated no-ip at the web site, all servers work but apache times out now if
> browsed by using the FQDN, I can access apache by browsing as http://<the
> actual inet IP address>
[...]

If your domain is actually ohmster.com I just loaded the page here
using Mozilla and your domain name. FYI, do you realize that running
a ftp, e-mail and web server on non-business ADSL is against
BellSouth.net's AUP? See: <http://makeashorterlink.com/?D21C23D04>.
See also: <http://www.dslreports.com/faq/8681>. BellSouth.net DOES
enforce this policy. To verify that see this ex-BS.n users post on
DSLR: <http://www.dslreports.com/comment/554/34900>.

Personally I chose to get a domain with an inexpensive separate
hosting service for my SOHO business instead of risking losing my
ADSL access to my home. I don't intend to report you, but were I in
your position I would NOT advertise on USENET that I was actively
breaking my ISP's AUP. All you have to do to get caught is piss-off
one of these fragile USENET freaks that engage in the interminable
flame-wars. Your posts along with domain name are archived on Google
<http://makeashorterlink.com/?I2E126687> and can easily be referred
to BS.n's abuse department. :-)

Gene (e-mail: gene \a\t eracc \d\o\t com)
--
Linux era4.eracc.UUCP 2.4.22-26mdkenterprise i686
09:25:30 up 25 days, 11:21, 11 users, load average: 0.01, 0.03, 0.00
ERA Computer Consulting - http://www.eracc.com/
eCS, OS/2, Mandrake GNU/Linux, OpenServer & UnixWare resellers

ERACC <(E-Mail Removed)> wrote in
news(E-Mail Removed) P:

> If your domain is actually ohmster.com I just loaded the page here
> using Mozilla and your domain name.

Ya know, this is one exception where a reply by email might really have not
been such a bad thing. <g>

Anyway, thanks for the heads up.

I don't do anything commercial with my machine, it is my "linux 101" class, I
cannot afford the money or the time to study linux in school so I do it at
home on my old PIII 800. I really have learned a lot about networking and
linux in general and I am very pleased with the OS. The web server is really
just a small server for my family with .htaccess protection for family
messages and photos. None of this is high volume, I already leaned that an
ADSL connection is not suitable for a real, public website.

I was the very first person in my area to subscribe to the ADSL, they charged
me three hundred freaking dollars for the install and the modem. Gave me a
bridged ethernet connection and all was well. Now that they pulled the plug
on the briged ethernet and stuck me with PPPoE, I am very much less than
satisfied. Losing Bellsouth would not really be such a big loss now.

Anyway, on to the fun linux stuff. Apparently, you are right and the web
server is operational. Checking the access_log shows this to be so. What is
puzzling me is that I cannot access this site with either of the two XP
machines on the LAN, unless I browse to the IP address. Browsing by domain
gives me a "page not found" message but it is not a 404 apache message. Going
to the root of the domain give me "This site under construction and does not
have a default page". This is also not an apache message, but rather an MS
server message. Where in the hell is this message comming from? I am not
running an MS web server on either machine, ping and traceroute both go right
to the actual IP and return pretty quickly.

Neither XP machines have changed configs at all, both have static NAT IPs and
use my ISP's two nameservers for DNS lookups. The actual linux machine can
display the web site by domain name. The XP machines can only display the
site via inet IP address (Or local NAT IP).

What the heck is going on here? The only thing that I can think of is that
roariing penguin changed some kind of file somewhere and now my LAN machines
cannot find the correct IP for my http server, OR that it is being
intercepted somehow by an MS machine and hence I am getting the "under
construction" page.

This is really freaking me out because I cannot understand this, hope that
someone can shed a little light.

Thanks again for the heads up, next time please use direct reply to author
for this kind of reply. ;>)

--
~Ohmster