Yeah you defiantly want to completely remove the default config. If I remember correctly the default is configured as a simple nat router. So the firewall rules are setup as such. That is why input is dropped on the Gateway port.
The FW doesn't have anything to do with the config. Thanks, Chadd -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stuart Pierce Sent: Tuesday, May 08, 2012 5:36 AM To: Mikrotik discussions Subject: Re: [Mikrotik] 750UP Access Problem It's a 750UP and yes it still had the default config of which I just changed the ports to just bridge with port 2 and put the poe switches to always on except for port 1. So I changed the ip and now I can't access it from port 1 side, backhaul side ( I think port 2 ), so I am going to try an ap ( which I think is port 4 ). Otherwise I put an iBoot on it else I'll have to climb up there and replace it and hope they come out with newer firmware that isn't so touchy on the load. ---------- Original Message ---------------------------------- From: "Chadd Thompson" <[email protected]> Reply-To: Mikrotik discussions <[email protected]> Date: Sun, 6 May 2012 19:22:57 -0500 >Stuart, > >Are you seeing "router was rebooted without proper shutdown" in the logs? > >If so there was a bug in the older firmware that would cause 711 based >boards to randomly reboot and in the log it looks like it is due to power >loss. > >It wasn't something that was ever mentioned in the changelog as far as I >know, I was working with Uldis on it and had a beta firmware he sent me and >it took care of the issue. > >The latest firmware release fixes the problem though. If you upgrade to 5.14 >and update the FW it will fix it. > >For me this was only an issue on 711 boards so if you aren't using 711 it >may or may not be your problem. > >Thanks, >Chadd > >-----Original Message----- >From: [email protected] >[mailto:[email protected]] On Behalf Of Stuart Pierce >Sent: Sunday, May 06, 2012 3:36 PM >To: Mikrotik discussions >Subject: Re: [Mikrotik] 750UP Access Problem > >Cheese and crackers, for now I put in an iBoot. Seems I have one of two >devices losing power randomly and it seems to have reared it's ugly head >with v5.5. > >---------- Original Message ---------------------------------- >From: Bill Prince <[email protected]> >Reply-To: Mikrotik discussions <[email protected]> >Date: Sat, 05 May 2012 19:25:41 -0700 > >>+1. >> >>First rule with any of the 750 units is to _not_ use the default >>configuration. >> >>bp >> >> >>On 5/5/2012 9:45 AM, Robert Andrews wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> I hate that default config! >>> >>> On 05/05/2012 09:20 AM, Josh Luthman wrote: >>>> And it turns off the mac-telnet server on ether1, too =( >>>> >>>> Josh Luthman >>>> Office: 937-552-2340 >>>> Direct: 937-552-2343 >>>> 1100 Wayne St >>>> Suite 1337 >>>> Troy, OH 45373 >>>> >>>> >>>> On Sat, May 5, 2012 at 12:18 PM, Chadd Thompson<[email protected]> >wrote: >>>>> I don't remember for sure what the default config is on the UP but some >of >>>>> the MT routers have a firewall rule setup to drop all input traffic on >>>>> port1. That would show the same symptoms as you describe, if you are >trying >>>>> to connect through port1 maybe try to access it from one of the other >>>>> Ethernet ports. >>>>> >>>>> Thanks, >>>>> Chadd >>>>> >>>>> -----Original Message----- >>>>> From: [email protected] >>>>> [mailto:[email protected]] On Behalf Of Stuart >Pierce >>>>> Sent: Saturday, May 05, 2012 6:11 AM >>>>> To: Mikrotik discussions >>>>> Subject: [Mikrotik] 750UP Access Problem >>>>> >>>>> I got a 750UP and put all ports into the same bridge and left it with >the >>>>> 192.168.88.1 ip, turned on all poe ports except for port one, no other >real >>>>> changes I can think of since I didn't really need it for anything else >than >>>>> providing power to two devices. >>>>> >>>>> It's been in place for a month let's say, went in the other day to >change >>>>> it's ip, via ip and addresses, it listed the one ( 192.168.88.1 ) and I >>>>> changed it to 172.20.81.197 and the gateway to 172.20.81.1 and of >course ok. >>>>> >>>>> Lost connectivity obviously and got into winbox and did a rescan ( ... >) and >>>>> it finds it with the new ip address..... >>>>> >>>>> but it won't connect !!! Either by ip or mac, ip method takes longer to >give >>>>> me no love, but what the heck. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ________________________________________________________________ >>>>> Sent via the WebMail system at avolve.net >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Mikrotik mailing list >>>>> [email protected] >>>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>>> >>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >RouterOS >>>>> >>>>> _______________________________________________ >>>>> Mikrotik mailing list >>>>> [email protected] >>>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>>> >>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >RouterOS >>>> _______________________________________________ >>>> Mikrotik mailing list >>>> [email protected] >>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>> >>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >RouterOS >>>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.11 (GNU/Linux) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >>> >>> iQEcBAEBAgAGBQJPpVkQAAoJEC+8HUjSuDOs75wH/1sc/IjbBlWC32mTjEJ69zma >>> e5LW/PRXjDvi2hLvCnxkTslvfY2cviBsmY9lOsdGuEPLU2DFrrJD7Z5l7rKce7KI >>> oHOKTZ29qwBq61u353po04xl/7rQwX0yHIoVS1lbFhxOITbnKi3//bT8xhcV6EnN >>> XQttxpcoUeerW0Kwl9F044n+Gtj3sJZXiVagOoZHiwkRmsune8XizBmAJf0mh0xZ >>> lXOsyKhJMoCxx5tNzqE/ma405khEg6/iIffl90XP9eDkOFB7Tvirekm1Yx8THfSr >>> 9/2WUOWVV9w+LscYPuw9mkwVhMUBKi3vAvgbUA/RsjnGvlgZFPVcGcuAXmDbMlk= >>> =oJ0e >>> -----END PGP SIGNATURE----- >>> _______________________________________________ >>> Mikrotik mailing list >>> [email protected] >>> http://www.butchevans.com/mailman/listinfo/mikrotik >>> >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >RouterOS >>> >>_______________________________________________ >>Mikrotik mailing list >>[email protected] >>http://www.butchevans.com/mailman/listinfo/mikrotik >> >>Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >RouterOS >> > > > > > >________________________________________________________________ >Sent via the WebMail system at avolve.net > > > > >_______________________________________________ >Mikrotik mailing list >[email protected] >http://www.butchevans.com/mailman/listinfo/mikrotik > >Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS > >_______________________________________________ >Mikrotik mailing list >[email protected] >http://www.butchevans.com/mailman/listinfo/mikrotik > >Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS > ________________________________________________________________ Sent via the WebMail system at avolve.net _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
