Re: dhclient problem
From: Jason Campbell (syskill_at_sysk-net.com)
Date: 09/28/03
- Next message: Moe: "Re: UNIX Book Recommendation"
- Previous message: Barry Skidmore: "Re: UNIX Book Recommendation"
- Next in thread: Per Hedeland: "Re: dhclient problem"
- Reply: Per Hedeland: "Re: dhclient problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 28 Sep 2003 03:22:22 GMT
>
> dhclient really shouldn't be able to do that. I can't see any way it
> could arrange for it. Are you, perhaps, getting many different *copies*
> of dhclient started? The ps(1) output should tell you.
>
Only one dhclient was running. Already checked that when it occured.
>
> Routed? What the heck were you running routed for on a DHCP-managed
> connection?
>
With the FreeBSD 5.1 installation, I had it running as a bridge+firewall
and both my netcards had their own IP address (one LAN IP and one Internet
IP). Yes, I already you're not SUPPOSE to have IPs on a bridge, but
there's nothing that says you can't. I also have a 56k "backup" (great for
when I'm getting DoS'd -- it's happened before. Some people just don't
like ops on IRC). The 56k is used for DoS attack prevention (sorta) and if
someone is using too much of my bandwidth, I can reroute them to 56k (I've
done this a lot too):
route add 4.4.4.4 ppp0
I get my bandwidth back, and they're able to download (just at a MUCH
slower rate). So, that's why I had routed running. But with the FreeBSD
4.8 installation, I just had it configured for a NAT (no bridge). Not sure
if I was running routed, I don't think so. But even with 4.8, the problem
still existed, so I know it wasn't a bridge+IP problem.
>
> Wouldn't it be easier just to tell DHCP not to do that? It won't cause
> this problem, though.
Yes, it probably would. But I've never used *BSD before. I've been using
Linux for a couple years now. I've had problems with telling DHCP not to
overwrite my /etc/resolv.conf file. It would still do it anyways. So after
getting pissed, I set chattr +i. Well, I guess now it's just a habit. So
that's why that was done.
>
> Try doing an absolutely minimal amount of configuration on the system,
> and then add one thing at a time to see where the problem comes in.
> Start with a clean install of FreeBSD, add no packages/ports at all,
> configure dhclient, and I suspect you won't have a problem with
> dhclient. Then add things back in.
>
Both 5.1 and 4.8 installations were minimal amount of packages and
configuration. If I remember correctly, I just picked the base (not
sure if it's called base or bin or what it's called) and system source
(ssys) and a couple ports (like vim-lite). It's hard to get any more
minimal that what I had.
- Next message: Moe: "Re: UNIX Book Recommendation"
- Previous message: Barry Skidmore: "Re: UNIX Book Recommendation"
- Next in thread: Per Hedeland: "Re: dhclient problem"
- Reply: Per Hedeland: "Re: dhclient problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
