I cannot vouch for the UK... but there are quite a few ISPs in the US, specifically the Midwest that do the same thing. In nearly every case, I've found it is a policy of the company, not a limitation of technical nature. Many of the smaller CLECs in our area will not allow the customer CPE to be placed into RFC1483 bridge mode on their ADSL circuits for some reason. When we run into this problem, and the customer is unwilling to change ISPs for whatever reason, we put the IP of the pfSense/monowall WAN in the DMZ of the ISP provided unit. It sounds like the device you are using now has 1:1 NAT available on it? I guess if you are forced to keep your equipment on a private subnet, this is the best setup as you can have multiple servers. We are limited to only one device through the DMZ function.

Tim Nelson
Technical Consultant
Rockbochs Inc.



Siju George wrote:
Dear People in U.K,

I had a little taste of the British Telecom ( BT ) ISP a while back.

It seems that they have a device ( modem ) that has to be used to give
IP address by "dhcp" to all systems.

And even if you want to give Static IPs ( routable on the Internet )
assigned to you by BT on any of your servers you should first assign
the server an IP in the local range through dhcp and then get into the
BT device's web interface and assign the Static IP through that
interface to the appropriate server.

How do the British people use pfSense as the firewall while using BT
as their ISP?
I asked the sysadmin there and he said they just use the firewall on
the BT device (modem) and that the device cannot be done away with or
configured to allow us to define static IPs on the interface of our
Servers using the config files on the servers Operating System.

Is this true?
And what are the other ISPs other than BT in U.K especially in the Bolton Area?

Thankyou so much

Kind Regards
Siju

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to