wide dhcp client and @home cable modem service

wide dhcp client and @home cable modem service

Post by Murray Stoke » Wed, 18 Nov 1998 04:00:00




"identifier" that Windows 98 uses to connect just fine (same system,
dual boot).  In FreeBSD I type

/usr/local/sbin/dhcpc -r fxp0
/usr/local/sbin/dhcpm fxp0 ~/logfile

and basically it just keeps sending the DHCPDISCOVER message over and
over again without ever getting a DHCPOFFER message.  This is what the
logfile created by dhcpm looks like.  I notice that nowhere is my
hostname (the secret 'c#######-a' identifier) mentioned.  Am I missing
some configuration step?  

  "Nov 15 16:06:31.593862"    DHCPDISCOVER
        src_haddr: 00a0c957b4a3, dst_haddr: ffffffffffff
        src_IP: 0.0.0.0, dst_IP: 255.255.255.255
        requested_IP: None
        requested/assigned lease: 3600
        dhcp_t1: 0      dhcp_t2: 0
        op: 1, xid: 295d8164, secs: 61, BRDCST flag: 0
        ciaddr: 0.0.0.0, yiaddr: 0.0.0.0, siaddr: 0.0.0.0, giaddr:
0.0.0.0
        broadcast: None subnetmask: None
        server_id: None
        default router: None    

Thanks!

(please email me with responses by removing the NOSPAM)

        Murray Stokely

 
 
 

wide dhcp client and @home cable modem service

Post by Marc Si » Wed, 18 Nov 1998 04:00:00



>        I'm unable to use FreeBSD to connect to the Internet via the

>"identifier" that Windows 98 uses to connect just fine (same system,
>dual boot).  In FreeBSD I type

Your hostname won't be used as a CLID string by the client. I don't think the
current version of the WIDE client can identify itself by anything other than
the standard MAC address, actually. The ISC v2 client may be able to, using
a config option (again, not your hostname). Are you certain it's strictly
necessary, though? The DHCP server will probably give you the same address
that Windoze had anyway, just based on your MAC address. Even if it doesn't

not more than one concurrently.

Quote:>/usr/local/sbin/dhcpc -r fxp0

That ought to do it. Someone posted recently that they were able to fix
a similar problem by switching the cable modem off and on again. Voodoo, but
worth a try. :)

--
Marc Sira                  |


 
 
 

wide dhcp client and @home cable modem service

Post by Paul » Mon, 23 Nov 1998 04:00:00



static address. This would mean to me that DHCP is not being used. I spoke


their internal home based network. I am a newbie to FreeBSD, but this is
exactly why I am learning this system. We currently use FreeBSD as a

have a class C with private IP's inside.

 I am studying the possibility of using FreeBSD throughout to lower the Cost
Of Ownership (microsoft now :(   ). I first want to become familiar with the
firewall ( I inhereted it). Any info you can point me to for packet
filtering and proxying with FreeBSD would be greatly appreciated.

Thank You
Paul Turner
CityTeam Ministries

-----Original Message-----

Newsgroups: comp.unix.bsd.freebsd.misc
Date: Tuesday, November 17, 1998 2:31 PM


>>        I'm unable to use FreeBSD to connect to the Internet via the

>>"identifier" that Windows 98 uses to connect just fine (same system,
>>dual boot).  In FreeBSD I type

>Your hostname won't be used as a CLID string by the client. I don't think
the
>current version of the WIDE client can identify itself by anything other
than
>the standard MAC address, actually. The ISC v2 client may be able to, using
>a config option (again, not your hostname). Are you certain it's strictly
>necessary, though? The DHCP server will probably give you the same address
>that Windoze had anyway, just based on your MAC address. Even if it doesn't

>not more than one concurrently.

>>/usr/local/sbin/dhcpc -r fxp0

>That ought to do it. Someone posted recently that they were able to fix
>a similar problem by switching the cable modem off and on again. Voodoo,
but
>worth a try. :)

>--

 
 
 

wide dhcp client and @home cable modem service

Post by Kenneth Furg » Tue, 24 Nov 1998 04:00:00



>  I am studying the possibility of using FreeBSD throughout to lower the Cost
> Of Ownership (microsoft now :(   ). I first want to become familiar with the
> firewall ( I inhereted it). Any info you can point me to for packet
> filtering and proxying with FreeBSD would be greatly appreciated.

http://www.freebsd.org/handbook

and

man ipfw

and

man natd

are good places to start.

- K.C.

 
 
 

1. DHCP and @Home cable modem service

Has anyone out there succeeded in getting a Linux DHCP client communicating



apparently does something slightly unusual where they use the DHCP
clientIdentification tag (I think) to make sure a customer is given the same
IP each time (if possible). (Or, rather, they use the Windows "machine
name", which is in turn the DNS name of the IP address, and I assume that
information is propagated as the clientID tag.)

FWIW, so far I've played around with dhcpcd, but have had zero useful
results (tcpdump shows the broadcast packet being sent on the appropriate
interface, but no responses ever come.) I'm not sure whether this is because
I'm not using dhcpcd properly (in my dual NIC setup), or because the
clientID tag needs to be set properly before the server will respond.

Thanks for any help,
Ken

--

2. Need a good one liner

3. Solaris 8 DHCP Client Config on @Home Cable Modem

4. network/ppp/firewall problems

5. HOME cable service dhcp

6. help with TIA please

7. DHCP config for @home cable service?

8. ISDN card driver

9. Cable Modem (COX @HOME), I NEED HELP SETTING UP MY CABLE MODEM WITH RH 5.1

10. @Home Cable Modem and RedHat 6.0 -- no packets get past the cable modem at all!

11. COX@HOME Phoenix AZ Cable Modem Service

12. Linux - @home cable modem service wierdness

13. Comcast@Home Cable Modem Service Help