Date: Tue, 26 Jun 2001 20:49:09 -0400 (EDT) From: "Ian P. Thomas" <ipthomas_77@yahoo.com> To: crist.clark@globalstar.com (Crist Clark) Cc: freebsd-questions@freebsd.org Subject: Re: cable connection problems Message-ID: <200106270049.UAA00734@scraemondaemon.my.domain> In-Reply-To: <no.id> from "Crist Clark" at Jun 26, 2001 02:44:08 PM
next in thread | previous in thread | raw e-mail | index | archive | help
You're a genius. After unplugging the modem and plugging it back in after disconnecting it from the Windows box, I rebooted and got my IP. Everything just works now. It seems that the cable modem was keeping the MAC in memory when I put the modem into standby. There is no power off button so the plug had to be yanked. A quick question about firewalls. I had a firewall setup for my dial up connection, but I knew the DNS IP's and used the following two lines to let name lookups and responses go through $fwcmd add allow udp from any to 207.217.77.82 53 out xmit tun0 $fwcmd add allow udp from 207.217.77.82 53 to any in recv tun0 How can I allow name lookups if I don't know the DNS IP's? Ian In the last episode, Crist Clark stated... > > "Ian P. Thomas" wrote: > > > > After installing winpcap and ethereal on Windows here is the output > > from when I did a release to when I did a renew. I had trouble viewing it > > with tcpdump -r, it seemed to take awhile and I gave up after a few > > seconds. > > Turn off name resolution. Use the '-n' option (I wish that was the default). > Also, you can clear out the ARP noise by putting a '! arp' filter on > the tcpdump(8) command line. > > > It looks like the problem is with me not specifying myself as > > hes1_buf_adelphia_net. Is this the hostname option in DHCP options? > > hes1.buf.adelphia.net (208.246.218.2) is the name of the DHCP server > that responded too your DHCPDISCOVER broadcast. No one ever responded > in the other dump. > > > The > > use of more info on winipcfg gave me this for the hostname of the Win95 > > laptop. > > > > MBA-07100.buf.adelphia.net > > Is MBA-07100 a name you, the manufacturer, or some one else gave to your > computer? Your machine requested this name and the name is not in DNS. > > Anyway, it all looks like a very typical DHCP negotiation. dhclient(8) > on your FreeBSD system should work just fine. I still think it is a problem > with your MAC address. Have you tried to, > > (1) Remove the Win machine from the network. > (2) Power off the modem. > (3) Wait... > (4) Connect FreeBSD machine. > (5) Power on modem > (6) Boot FreeBSD machine. > > Yet? If this does not work either, call your ISP. Ask them why you are > having trouble moving the connection between machines. This has nothing > to do with OS compatibility. DHCP is an Internet protocol and therefore > is OS independent. > -- > Crist J. Clark Network Security Engineer > crist.clark@globalstar.com Globalstar, L.P. > (408) 933-4387 FAX: (408) 933-4926 > > The information contained in this e-mail message is confidential, > intended only for the use of the individual or entity named above. If > the reader of this e-mail is not the intended recipient, or the employee > or agent responsible to deliver it to the intended recipient, you are > hereby notified that any review, dissemination, distribution or copying > of this communication is strictly prohibited. If you have received this > e-mail in error, please contact postmaster@globalstar.com > 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?200106270049.UAA00734>