Don’t see a problem with your first layout. In fact I would have thought it better to use the radius etc on a public IP to be accessed by multiple sites. I run it that way but i’m running PPPoE accross wireless. Maybe it’s got something to do with MTU over the ATM(ADSL) network. I know ADSL connections have heavy overhead and often cannot support an MTU above 1400?? You could force a lower MTU perhaps on the MT?
when i try to connect with DSL router (PPPoE client), the connection is unstable. when i leave the modem connected (idle). the connection is drop and cannot connect again. need to restart the router to establish the connection again. i set the idle time out = 1 hour. but before 1 hour, the connection is drop.
Ok so i’m not understanding this then. When you have a idle period it wil disconnect no matter how long to set your idle timeout to be. The MT log shows nothing because the session doesn’t logout or timeout?
If i’m getting this, it sounds like you are having issues with the dsl router and/or dslam.
but when i tried a bridge mode (using DHCP) instead a PPPoE…the connection is steady…we have tried it from 2 days a go…and until now…it still connected…
the problem must be not from the DSLAM or the DSL router…
Well i have pretty close to your first setup. The only difference is the backbone to my internet source is directly plugged into the MT and so is the radius server. They both have their own interface. It works PREFECT and i’ve never had any issues.
Your friend does not know what he is talking about.
Don’t do VJ compression as its a red herring with most current implementations. Adjust mtu/mru to a maximum of 1492
Set keepalive timeout to a lower value (otherwise face the implications of higher timeout). Dont do “change-tcp-mss” as this feature has been broken since pre 2.8. It should just adjust the mss when it’s too high but it just overwrites the mss (which is utterly broken behavior). You need to enforce users to use 1492 and only 1492. Add three proper mss adjustment rules. Instead add two tcp mss rules in forward chain, Don’t permit compression or encryption.