--On Sunday, November 24, 2002 01:25:38 PM -0800 Ivory Williams <[EMAIL PROTECTED]> wrote:
And what makes you so sure this is a problem? As pressure on the IPV4 address space mounts, ISPs are increasing the use of RFC 1918 addresses for their infrastructure systems including DHCP servers. This is likely what AT&T are doing (even though their service reps are clueless).Iam using Dacstein 1.0.2 with all defaults. Dual floppy's [write protected] (only configured both NIC's) for over a year with no problems on an ATT cable modem network.The system is LRP on 486 using default 192.168.1.254 2 ISA NIC's LRP NIC #1 (eth0) to Motorola Cable Modem LRP NIC #2 (eth1) to Addtron Router Cable Port (crossover cable) Addtron E200P hardware router (192.168.2.1) ATT Motorol Surfboard cable modem Various internal PC's connect to Router at 192.168.2.x (statc ip's) Normally it picks up my ATT DHCP server at 24.126.x.x and returns a DHCP IP of 24.x.x.x. which usually doesn't change for 90 days or more. Problem: What is now happening is the DHCP Offer is from a 10.235.112.1 (a privite IP address) as a DHCP server but returns the same IP address I usually receive from the ATT DHCP server (24.x.x.x).
There's a FAQ (http://shorewall.sf.net/FAQ.htm#faq14a) that deals with this for Bering/Shorewall.
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://shorewall.sf.net
ICQ: #60745924 \ [EMAIL PROTECTED]
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
