I always configure the GnatBOX GB-1000 with GBadmin. Last time I used the web interface was to install v3.2.0 of the GnatBOX software. So, it can't be the usage of the web interface.
Note, when I noticed it, the GB-1000 I administer just decided to goof up. Prior to goofing up, it was about two days ago before I changed the configuration. What's important here is that it just decides to do it. No user/administrator intervention is required for the fault to "happen". I'm not checking the mail server and Gnatbox about three to four times a day. In reality, this is something I don't need to do. I'm surprised this fault has existed since v3.1.3, and maybe on GbatBOX firmware well before then. Not a good sign. At least the fault is out in the open and I'm so hoping for a maintenance release of the GnatBOX software to be release before December arrives. At 31/08/2001 03:41 pm , "Bryan Kuhn" <[EMAIL PROTECTED]> wrote: >I get this sometimes when changing a few things around through the web admin >(seems to hang after trying to save a section). You can tell if messes up by >looking at the active routes. When it messes up for me its always a random >amount that shows up there, sometimes its almost all the static ips, >sometimes its way less. > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of >Paul Dawson >Sent: Friday, August 31, 2001 12:26 AM >To: Bill Jaeger >Cc: Myron Szymanskyj; [EMAIL PROTECTED] >Subject: Re: Static address mapping can become screwed up. > > >Hello Fellas, > >Yes, I too have had the same problem. >However, you do not have to reboot. >Simply resettng the static mappings by re-entering or re-clicking > them should do the trick. > >You know what i mean? In GB-Admin click down arrow and then select the >same thing. > >Cheers, > >Paul Dawson > > > > >Bill Jaeger wrote: > > >--------------------- Attention ----------------------------- > >A digest version of this list is now available. > >Send email to [EMAIL PROTECTED], with the following message: > >subscribe gb-users-digest your_email_address > >Then unsubscribe from this list. > >------------------------------------------------------------- > >GNAT Box User Forum http://www.gnatbox.com/cgi-bin/Ultimate.cgi > >Send postings to: [EMAIL PROTECTED] > >Access the list archives at: http://www.gnatbox.com/gb-users/ > >------------------------------------------------------------- > > > >Myron, > > > >I had seen this same behavior a few months ago with one of our GB-1000s > >running v3.1.3s, and discovered the same "solution" that you did -- reboot. > > > >I chalked this problem up as being a random event at the time since I had > >not seen this behavior before, nor have I seen it since. Like you, I have > >no idea as to what caused this behavior. > > > >-Bill > > > >>-----Original Message----- > >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > >>Myron Szymanskyj > >>Sent: Thursday, August 30, 2001 8:34 PM > >>To: [EMAIL PROTECTED] > >>Subject: Static address mapping can become screwed up. > >> > >> > >>--------------------- Attention ----------------------------- > >>A digest version of this list is now available. > >>Send email to [EMAIL PROTECTED], with the following message: > >>subscribe gb-users-digest your_email_address > >>Then unsubscribe from this list. > >>------------------------------------------------------------- > >>GNAT Box User Forum http://www.gnatbox.com/cgi-bin/Ultimate.cgi > >>Send postings to: [EMAIL PROTECTED] > >>Access the list archives at: http://www.gnatbox.com/gb-users/ > >>------------------------------------------------------------- > >>Spoke to a very nice person at GTA and have uncovered a rather > >>odd problem. > >> > >>Assume the following: > >> External NIC: 200.1.1.1 > >> Alias addressed: 200.1.1.2 and 200.1.1.3 > >> > >>A mail server sat at 172.16.0.1. It's bound to that IP. > >> > >>NAT: A static IP mapping for IP address 172.16.0.1 (on PSN) to IP address > >>200.1.1.2 for outbound traffic to the external NIC. > >> > >>OBF: Outbound filter accepts connections from PSN on IP > >>172.16.0.1 TCP port > >>25 to any IP. > >> > >>NAT: Inbound tunnel: 200.1.1.2 TCP 25 -> 172.16.0.1 TCP 25 > >> > >>RMF: Remote access filter accepts connections coming to an inbound tunnel > >>200.1.1.2 TCP 25 -> 172.16.0.1 TCP 25. > >> > >>Here is the problem with firmware v3.2.0 and possibly v3.2.1, > >>which can be > >>worked around by simply rebooting the GnatBOX. I'm actually running the > >>GB-1000. > >> > >>Outbound connections from the mail server on 172.16.0.1 start > >>getting sent > >>out of the external NIC with an originating IP of `200.1.1.1`. This is > >>incorrect as the originating IP should be `200.1.1.2`. It's a > >>bug. (Shock > >>horror . . .) > >> > >>Exactly how to recreate I do not know. Enough to say that the IP > >>dropped a > >>number our ISP's mail relay didn't know the new originating IP > >>address (no > >>RDNS) and was rejecting e-mail from our mail server. It just happened. > >> > >>After a decent discussion with a technical person at GTA, the temporary > >>solution was to keep an eye out for it happening again and if it does, > >>reboot the GnatBOX. The problem (I belive) has been passed on to > >>the gurus > >>in the states. > >> > >>That's all folks . . . > >> > >>So, I'm curious. Who else has suffered from this? I only sussed > >>out that > >>was happening as our mail server logged our ISP's mail relay's welcoming > >>reply, which (luckily) also returned the IP address of the mail > >>client/server that the ISP's mail relay thought was talking to it. > >> > >>Hmm.. Stealthy and nasty.
