Brian John wrote:
Lowell Gilbert wrote:
"Brian John" <[EMAIL PROTECTED]> writes:
On Apr 3, 2005 9:12 PM, Anthony Atkielski
<[EMAIL PROTECTED]>
wrote:
One you've changed resolv.conf, it should stay that way permanently
across boots, unless you change it again.
dhclient will overw
Lowell Gilbert wrote:
"Brian John" <[EMAIL PROTECTED]> writes:
On Apr 3, 2005 9:12 PM, Anthony Atkielski <[EMAIL PROTECTED]>
wrote:
One you've changed resolv.conf, it should stay that way permanently
across boots, unless you change it again.
dhclient will overwrite /etc/reso
cape canaveral writes:
> dhclient will overwrite /etc/resolv.conf on boot
Then perhaps dhclient.conf is the culprit; an alternative is to stop
running dhclient, but only if the machine's own IP address is static.
--
Anthony
___
freebsd-questions@fre
"Brian John" <[EMAIL PROTECTED]> writes:
> > On Apr 3, 2005 9:12 PM, Anthony Atkielski <[EMAIL PROTECTED]>
> wrote:
> > >
> > > One you've changed resolv.conf, it should stay that way permanently
> > > across boots, unless you change it again.
> > >
> >
> >
> > dhclient will overwrite /etc/resolv.
On Monday 04 April 2005 09:52 am, Brian John wrote:
> > On Monday 04 April 2005 07:40 am, Brian John wrote:
> > > > On Apr 3, 2005 9:12 PM, Anthony Atkielski
> > > > <[EMAIL PROTECTED]>
> > >
> > > wrote:
> > > > > One you've changed resolv.conf, it should stay that way
> > > > > permanently across
> On Monday 04 April 2005 07:40 am, Brian John wrote:
> > > On Apr 3, 2005 9:12 PM, Anthony Atkielski
> > > <[EMAIL PROTECTED]>
> >
> > wrote:
> > > > One you've changed resolv.conf, it should stay that way
> > > > permanently across boots, unless you change it again.
> > >
> > > dhclient will over
On Monday 04 April 2005 07:40 am, Brian John wrote:
> > On Apr 3, 2005 9:12 PM, Anthony Atkielski
> > <[EMAIL PROTECTED]>
>
> wrote:
> > > One you've changed resolv.conf, it should stay that way
> > > permanently across boots, unless you change it again.
> >
> > dhclient will overwrite /etc/resolv.
> On Apr 3, 2005 9:12 PM, Anthony Atkielski <[EMAIL PROTECTED]>
wrote:
> >
> > One you've changed resolv.conf, it should stay that way permanently
> > across boots, unless you change it again.
> >
>
>
> dhclient will overwrite /etc/resolv.conf on boot
How can I keep dhclient from doing this?
/Bri
On Apr 3, 2005 9:12 PM, Anthony Atkielski <[EMAIL PROTECTED]> wrote:
>
> One you've changed resolv.conf, it should stay that way permanently
> across boots, unless you change it again.
>
dhclient will overwrite /etc/resolv.conf on boot
___
freebsd-que
> On Sun, Apr 03, 2005 at 08:06:16PM -0500, Brian John wrote:
>
> [...]
> > Ok, I think you may have pointed me to the source of the problem. Here
> > is what my resolv.conf looks like after every time I reboot my compuer:
> > search domain.actdsltmp
> > nameserver 192.168.0.1
> > nameserver 205.1
On Sun, 03 Apr 2005 20:06:16 -0500
Brian John <[EMAIL PROTECTED]> wrote:
> Ok, I think you may have pointed me to the source of the problem.
> Here is what my resolv.conf looks like after every time I reboot my
> compuer: search domain.actdsltmp
> nameserver 192.168.0.1
> nameserver 205.171.3.65
On Sun, Apr 03, 2005 at 08:06:16PM -0500, Brian John wrote:
[...]
> Ok, I think you may have pointed me to the source of the problem. Here
> is what my resolv.conf looks like after every time I reboot my compuer:
> search domain.actdsltmp
> nameserver 192.168.0.1
> nameserver 205.171.3.65
If /e
Brian John writes:
> I don't think so because it works fine in Windows. Wouldn't it not work
> in windows if that was the case?
I understood that you had changed ISP connections also. If you're using
the same connection that Windows used, then it's not the ISP. Based on
your other posts, it so
Brian John writes:
> Now, if I change it to this (using my secondary DNS server from my DSL
> modem's 'setup' page):
> search domain.actdsltmp
> nameserver 205.171.2.65
>
> ...everything works. Is there a way that I could keep this from
> changing every time that I reboot my computer?
One you'v
[EMAIL PROTECTED] wrote:
On Sun, 3 Apr 2005 15:51:47 -0500 (CDT)
"Brian John" <[EMAIL PROTECTED]> wrote:
Hello, I just got an xDSL system. In Windows I can browse the
internet and do whatever I want just fine. However, in FreeBSD the
only things that work are my p2p programs. Azureus and amul
I didn't use any config files for this. I never had to use any to get my
cable modem to work either. What config files should I be looking at?
/Brian
- Original Message -
> Sounds to me as if you don't have your FreeBSD system configured
> correctly for DSL modem hookup.
>
> Post the
> Brian John writes:
>
> > Hello, I just got an xDSL system. In Windows I can browse the internet
> > and do whatever I want just fine. However, in FreeBSD the only things
> > that work are my p2p programs. Azureus and amule work fine, they both
> > connect and download. However, when I try to
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2005-04-03, Brian John scribbled these
> curious markings:
> > Hello, I just got an xDSL system. In Windows I can browse the internet
> > and do whatever I want just fine. However, in FreeBSD the only things
> > that work are my p2p program
On Sun, 3 Apr 2005 15:51:47 -0500 (CDT)
"Brian John" <[EMAIL PROTECTED]> wrote:
> Hello, I just got an xDSL system. In Windows I can browse the
> internet and do whatever I want just fine. However, in FreeBSD the
> only things that work are my p2p programs. Azureus and amule work
> fine, they b
Brian John writes:
> Hello, I just got an xDSL system. In Windows I can browse the internet
> and do whatever I want just fine. However, in FreeBSD the only things
> that work are my p2p programs. Azureus and amule work fine, they both
> connect and download. However, when I try to use dillo,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2005-04-03, Brian John scribbled these
curious markings:
> Hello, I just got an xDSL system. In Windows I can browse the internet
> and do whatever I want just fine. However, in FreeBSD the only things
> that work are my p2p programs. Azureus and
21 matches
Mail list logo
