Date: Sun, 20 Jun 1999 08:13:30 -0400 (EDT) From: Howard Goldstein <hgoldste@mpcs.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: dhcp client request for a netblk - ideas? Message-ID: <14188.56042.778949.835423@penny.south.mpcs.com> In-Reply-To: <Pine.BSF.4.10.9906181704330.34137-100000@resnet.uoregon.edu> References: <14182.57600.845707.33747@penny.south.mpcs.com> <Pine.BSF.4.10.9906181704330.34137-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White writes:
> On Tue, 15 Jun 1999, Howard Goldstein wrote:
>
> > This is what they tell me. The kind lady at the other end didn't
> > have/wouldn't tell me the IP block.
>
> Defeats the purpose of having a block, in my eye.
It turns out to be much worse than this. With dhclient at least I
should have been able to figure out the netblk. Turns out there is no
"netblk," not if you as I do think of netblks as contiguous, maskable
address ranges. They're apparently random IPs spread amongst gtei's /20
>
> > Would this work? I thought the protocol mapped a host address to a
> > MAC. If I did that and pulled the {blah} box back off the lease
> > (post-suck) would the ethernet link bomb? Sure, could try this too.
>
> Depends on who's providing the address. I don't know of any routers that
> try to mix DHCP and ARP. Sounds like a recipie for disaster
> though.
Alas, the provided Fujitsu replacement, an Orckit DSL device, doesn't
do IP routing. Ethernet bridging seems all it's capable of. This
causes other problems when the provider's DHCP server (an NT
box)(sigh) takes a dump and forgets about my lease even though it's
been only 3600 seconds instead of the granted 432000, or simply
ignores my bootp requests as it has been doing since 11am on Friday.
> > We *are* talking about the phone company. Is not the phone company
> > arrogant simply because they can be? If I tell them it doesn't
> > support DHCP they're going to tell me to buy their cute little $600
> > router that'll do this for me. I wonder how it's doing it
>
> I'd be curious to know. The Fujitsu solution is pretty space-inefficient
> -- two lines per card for what looks like an 8" tall card. The Copper
> Mountain DSLAMs we use fit 24 ports in a 16" card.
I asked, they said they have no capability for static routing or IPs
"at this time." I'm not going to push it right now since they're
obviously swamped in getting someone to reboot their NT box to get the
dhcp server fixed. Seems it takes GTEI from Friday afternoon until
(projected, promised) sometime before 2PM on Tuesday to do this.
I'm guessing the discman-like Fujitsu bridge is targetting the home
market: Not only doesn't it fit in a rack, it's not even rectangular,
therefore it doesn't stack well with all the other garbage in the
equipment closet.
> > Man I wish bpf was compiled in the GENERIC kernel, I really would have
> > liked to have tried dhclient before unplugging the thing to go home.
>
> I tried to convice them, but they wouldn't have any of it. Apparently it
> does have legal consequences (although Windows machines ship with this
> feature built-in ... hm... )
It would be very nice to have but seeing how much I've paid for
FreeBSD I'm going to be hard pressed to criticize volunteers for not
taking legal risks :-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14188.56042.778949.835423>