I guess I put in too much confusing (at least to me) detail.
I think my question was how to interpret ip's with numbers like:
63.11.8.26 and mask of 255.255.252.0
This seems to get interpreted by the firewall as something like:
63.11.8.0/22
So, I don't know why they are issuing such numbers, but, there must be a
good reason. I mean, why not just issue 63.11.8.0 with mask of 255.255.252.0 ?
Any how, I have tried to install dhclient, without success on my caldera 2.4
box with an updated kernel. As I recall, it wouldn't compile or somesuch, so
I am using dhcpcd, which seems to be a weak cousin. Its main problem seems to be that
it isn't talking to the comcast dhcpd server and just exits every now and then.
So, I just run dhcpcd from a script every so often, and it downloads my
current settings, or gets new ones, and I run my scripts from there. I
use the information file which dhcpcd creates in /var/run/dhcpc...info,
to provide data for my scripts, which is very handy. But, I am going to make
another attempt to get dhcpcd to work as advertised. The problem is, it
takes a long time to find out if dhcpcd is working well with the server,
since the leases are about one week in length and who knows, they may be
renewed repeatedly.
Joel
n Fri, Nov 29, 2002 at 08:17:45PM -0500, Jerry McBride wrote:
>
> You asked a lot, so I sprinkled my comments inside your quoted message.
>
> On Fri, 29 Nov 2002 19:38:55 -0500 Joel Hammer <[EMAIL PROTECTED]> wrote:
>
> > BACKGROUND:
> > I am on comcast, and get dynamically assigned ip numbers now.
>
> Yup, straight DHCP.
>
> > This is a pain, since, as far as I can tell, comcast is not using a standard
> > dhcpd server, and they don't support "third party" software.
>
> My home network is on comcast.net in New Jersey. Currently my home server runs
> OpenLinux 3.1.1. I use all the Caldera provided utilities with the ONLY
> modification being security upgrades. It works PERFECTLY.
>
> > My dhcpcd client can't tell when the ip number is changed...
>
> That's an inherent part of DHCP.
>
> >so, I run a
> > script whenever my connection gets bad, and so far this has been working.
> >
>
> If dhclient isn't picking up the new address, you've got something set up wrong.
> Review your setup.
>
> > However, I have to fool around with the firewall rules, too.
> >
>
> How about adding this to your firewall script?
>
>
> # your IP address
> IPADDR=`ifconfig | grep -A 4 eth0 | awk '/inet/ { print $2 } ' | sed -e
> s/addr://`
> echo " using this IP address from DHCLIENT -->"$IPADDR"<--"
>
>
>
>
> --
>
> ******************************************************************************
> Registered Linux User Number 185956
> http://groups.google.com/groups?hl=en&safe=off&group=linux
> Join me in chat at #linux-users on irc.freenode.net
> 8:09pm up 6 days, 21:53, 3 users, load average: 0.05, 0.07, 0.08
> _______________________________________________
> Linux-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
