Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: treyh on August 12, 2005, 08:24:12 PM

Title: **URGENT** accidental loopback
Post by: treyh on August 12, 2005, 08:24:12 PM

Hey Everyone,

I'm having a bad problem. I am a patient person but I am running out of time.

I accidentally set the public ip set
69.8.x.x
as a local network.

After doing so the internet went down. When I try to ping to the outside world I get a reponse that 172.16.1.1 is not responding (which is the local ip)

I think it's causing it to do a loopback to the local int when trying to get to the outside world. Any help will be greatly appreciated.

Title: Re: **URGENT** accidental loopback
Post by: CharlieBrady on August 12, 2005, 09:09:47 PM

Quote from: "treyh"

I accidentally set the public ip set
69.8.x.x
as a local network.

Login at the console, and access the manager and delete that network.

If the manager isn't accessable, then do:

/sbin/e-smith/db networks delete 69.8.x.x
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot

Title: thank you
Post by: treyh on August 12, 2005, 10:32:38 PM

Hello,

Thank you very much for your help and response charliebrady but I am still having problems.

Let me explain.

when I issue "route"

everything is fine except the default gateway. This is how it appears
default mail.mail.*.org 0.0.0.0 eth0

Now if i remove that route with this command
route del default gw mail.mail.*.org netmask 255.255.255.0 eth0

and add this route
route add default gw 69.8.3x.x netmask 255.255.255.240 eth1

then everything is fine and works great. before I did your previous suggestion the 69.8.30.x was showing up under route and I also had to remove it before things would start working. I eagerly await your reply.

Title: different
Post by: treyh on August 12, 2005, 11:36:46 PM

when I add this route
route add default gw 69.8.3x.x netmask 255.255.255.240 eth1

everything begins working. is there a way I can write a script to do this for me at the beginning of every startup?

Title: final solution
Post by: treyh on August 13, 2005, 03:31:09 AM

Well,

I do not have an "actual fix" for this problem but, I did find a work around.

I wrote a script (route.script):
route add default gw 69.8.3x.x netmask 255.255.255.240 eth1

This script runs from /etc/rc.d/init.d/route

The "route" file was setup like this:
. /installs/scripts/route.script

This worked well for me.