Problems after upgrade !

Hello guys!
Well after I upgrade my ROS from 2.9.51 to 3.10 i have lot of problems …
My network is have two parts: public and hotspot.
here is some basic sheme for my network:
Basic Scheme.jpg
When I do upgrade I was clean firewall rules (now is all filter clean except hotspot create own rules and dst-nat to server) and also make hotspot setup again , and at the first moment everything looks fine … now is also working normal , but … something strange is hapening.
Ftp server is accesable only via hotspot !
Ftp server have conected with 2 interface because user can use him at full speed with or without login to internet.
So all my users in network … including me are directly connected to ftp server … with or without login via hotspot … and now there is problem ftp host (win 2k wit latest updates) is sometime work ok and almost all time let say “not working”.
So I was try to change ethernet card because Im suspicious … Hm again same problem .
Here is list what i was try to do:
1.Pinging constant from ftp server few linksys AP is OK all day without loosing packets … fine
2.Pinging constant from ftp server to any windows (or linux) host is not work …
3.Pinging constant from linksys AP to ftp server is OK all day without loosing packets … fine
4.Pinging constant from any Ap or Windows host to mikrotik is not working when is not loged to hotspot?
When Im logged ping is OK. I think that this is normal.
5.Pinging constant from Windows (or linux) host to ftp server is not working if not logged:always first ping go then stops.
6.Pinging constant from Windows host to ftp server is working only when Im logged to hotspot.
7.Internet is working all time normal from both segment of my network (public and hotspot) without interupting… all firewall rules is clean (except hotspot create own rules and dst-nat to server).

Because case 5. and 6. (to eliminate windows errors):
I was check pinging from another windows host and got same results … ping to ftp server is not working all time ?
I was check pinging from another operating system (ubuntu 8.04) and got same results … ping to ftp server is not working all time ?
In mikrotik arp is enabled on all interfaces and I was try to change to proxy arp or replay only and no change… so I put back to enable(because hotspot stop to work).
And funny thing is that pinging to ftp server is somethime working if I make command arp -d , on ftp server and windows host, but only for short time …
Before upgrade everything is working normal so I suspect that is something is wrong with arp in mikrotik.
So it looks that mikrotik somehow block traffick betwen 2 windows host if not logged (only traffick betwen ftp and Linksys or other hardware AP is not blocked?) Magic?
But i dont need this “magic” … somethimes users need to download files without logging … there is also idle timeout in hotspot … which I must increase in that case …
Always problems after upgrade. :frowning:
Well now, after few days, mikrotik is “frozen” (like windoze somethimes) every day 2-3 times, and I cant connect in that moment with winbox from any any side network (only hardware reset help me)… only ping is working from both sides , and Internet is stop working for both sides my network, and looks like mikrotik is hold ADSL conection up.
Also I was include firewall filters for viruses from demo.mikrotik …
Oh man maybe is some hardware error in mikrotik or driver related (realtek8139 and TI ThunderLAN )…
Also when Im turn off mikrotik everythings work normal !
So I was losing ideas what is wrong … any ides is welcome (before downgrade) :frowning: .
Thanks for any help !

Hi Everyone, Normis etc

I’ve checked the forums for a response on this issue, but this was the only thread I could find about it.

I have 5 RB532’s in the field, of which I check the license allowances for all of them and they were able to go up to Verson 3.x. After updating 4 of them, 2 of them have … failed .. not completely tho.

The routers have a pppoe-out session, which according to my service provider is being assigned the correct public IP address, but when I check the IP > address table it gets a 10.112.113.x address as the public IP.

Anyone have any idea?

Do you have any other IP’s on that interface, and perhaps in that 10.x.x.x range?

Please give us a bit more info on your setup

Ok more details

I have a network, connected to ether 2 of the Mikrotik, with an ADSL modem attached to ether 3. My Mikrotik has an IP address of 192.168.5.1 on ether2, and the pppoe-client dials out on ether3.

Furthermore I have a pptp-client dialing out to multiple other Mikrotiks, as well as some pptp-servers for where the other routers dial back. This is a multi-site VPN solution with static routes to 192.168.1.x, 192.168.2.x and so forth.

The problem is now that I have upgraded to Version 3.11, the pppoe-client is being assigned a random 10.x.x.x IP address.

Anyone any thoughts?

Ok so I’ve just been working through this with my customers on the telephone. It turns out that the pppoe-clients no longer work… for no apparent reason. I needed to create new pppoe-client interfaces

After the upgrade, didn’t your PPPoE Servers perhaps jump to your ether3, and when you dial your ADSL it actually connect to a PPPoE server running on ether3?

The only way this could happen is if you have a PPPoE secret which is the same as your ADSL account.

What IP’s do you hand out to your clients?

What does the log say when your ADSL PPPoE connects? (Post the last 10 or so lines)

i have same problem after upgrade to v3.11
the pppoe-client is being assigned always to 10.65.65.75/32 IP address.
then after downgrade backto v3.6, the pppoe-client is being normal IP address

why? maybe v3.11 have bugs on pppoe-client?

\

[quote=“Treath”]Ok more details
I have a network, connected to ether 2 of the Mikrotik, with an ADSL modem attached to ether 3. My Mikrotik has an IP address of 192.168.5.1 on ether2, and the pppoe-client dials out on ether3.

Furthermore I have a pptp-client dialing out to multiple other Mikrotiks, as well as some pptp-servers for where the other routers dial back. This is a multi-site VPN solution with static routes to 192.168.1.x, 192.168.2.x and so forth.

The problem is now that I have upgraded to Version 3.11, the pppoe-client is being assigned a random 10.x.x.x IP address.

Anyone any thoughts?

Ok so I’ve just been working through this with my customers on the telephone. It turns out that the pppoe-clients no longer work… for no apparent reason. I needed to create new pppoe-client interfaces[/quote]