Kernel_Killer
February 8th, 2006, 16:16
Has anyone else dealt with sticky-IPs? I guess SBC is now using them for their static IP service, and does not offer their "legacy" statics anymore. To make a long story short, they aren't real WAN IPs, but IPs in a frame-relay cloud masked to look like real WAN IPs. First hop from the PPPoE connection is an internal connection, but anyways. We have been having issue holding our connection with this "sticky", and they claimed that our box (that has been working for months with this account) could not handle the sticky connection. So I found some resources regarding this type of connection. I'm not sure if its set correctly, but so far so good. If anyone could let me know if they have encountered this, and what they have done, I would galdly appreciate it. These are the rules I changed:


nat on $ext from $int1:network to !$int2:network -> $gw sticky-address
nat on $ext from $int2:network to !$int1:network -> $gw sticky-address
nat on $ext from $int3:network to any -> $tsip sticky-address


gw = the IP router for the block (/29)
tsip = one of the IPs off the block