Problems ==PLEASE HELP!==

[thzone]

@mdh, sorry for bugging you, but i've got problems-major!
@everyone else, *gulp* please? lol...

Okay, here's the skinny of it... After a couple of (wonderful) weeks of untangle, I noticed that the attack blocker was logging incoming attacks from the DMZ interface... and being the ever-inquisitive guy, I decided to take a look... bad idea!

The interfaces are/were as follows
eth0 (unused - this is an onboard NIC that doesn't link up...)
eth1 (LAN, 10.10.10.0/32)
eth2 (DMZ - 72.240.122.160, SOMEHOW)

Now, little did I know that the DMZ host was (somehow?) being assigned the static IP (72.240.122.160) that I had set up in the config/networking tab... and was handling all of the incoming traffic (which would explain all of the attack blocker attempts being logged on the DMZ interface)

So, being the pokey-nosey-gotta-know type... I asked in the IRC channel what I should do... and here's where it goes downhill...

I edited the /etc/iftab (after making a backup copy!) and deleted the eth2 interface, and copy/pasted its MAC address into eth0, and rebooted the machine... while rebooting, I disabled the onboard NIC, load into Untangle and... no net acccess.

I restored the /etc/iftab backup, rebooted the machine, re-enabled the onboard NIC, and got back into Untangle... and ...

Nope, notta, nothing, zip, zilch...

ahhh! help!

The store opens in 3 hours, and Thursday is one of the busier days!

[gotkimchi]

do you have a backup config file? You can restore to that point.

[thzone]

THANK YOU @ mdh! You've instantly become my HERO!

The problem was 1 part configuration error, and 3 parts general idiocy on my part...

It was a "simple" mixup of the DMZ/WAN interfaces.
eth0 (damaged onboard NIC) was being assigned to WAN
eth1 (Intel PCI NIC) was being assigned (correctly) to INTERNAL
eth2 (Intel PCI NIC) was being assigned (INcorrectly) to DMZ

My mistake was editing the iftab, and REMOVING the "eth2" line, and copy/pasting its MAC address in where the eth0's MAC address was... and rebooting... Apparently Untangle didn't like that.

Under the advice of mdh (over the phone), I restored from backup (Guys, the extra money to have your config files backed up off-site is WELL WORTH the money... it saved me the hassle of MANUALLY reconfiguring the server, which I would have had to do if I didn't have the offsite backup), and then editied the iftab file to swap (not delete) the eth0 and eth2 interfaces MAC address...

That worked (kinda), insomuch that I was able to access the internet, and DNS stuff.

That didn't work (more kinda), insomuch that incoming traffic to my mail/web server wasn't coming in...

I solved this (somehow?) by changing something, then immediately deleting my changes in the router rack, and then clicking save. (No, really... I changed something, and before clicking save, I un-changed it...)

Now I'm back up and running!


Thanks again mdh for the friendly and speedy help, and the Untangle crew as a whole (for such a wonderful product, and for hiring mdh)!


I will be spending time today talking my customer into purchasing the full professional package!

**EDIT**
Had this not worked, I would probably have a couple dozen very pissed-off store customers, as there are two tournaments taking place today, one is a Counter Strike tournament, and the other is a Guitar Hero 3 tournament...
**/EDIT**




~~THZone~~
Donald Mowry

[dmorris]

mdh FTW!