Hi,
Mark Andrews wrote:
This is just the attitude that's going to get people to use other
software. People are going to laugh at you trying to get a network
connection and joke it works fine with Windows. Then you try and
explain that it's not your OS's fault and somebody messed up some
Hi,
Greg Barniskis wrote:
Mark Andrews wrote:
Yes it is reasonable to expect ISP to fix things like this.
You pay the ISP to operate there part of the network within
the operational contraints of the RFCs (Standards track and
BCP).
I totally agree. Make sure when calling
Mark Andrews wrote:
What would be really interesting to know is what they expect
the customers to find using this suffix.
My bet is that this really is just a configuration error on
their part.
As is often said: Never attribute to malice what can adequately be
Mark Andrews wrote:
--61jdw2sOBCFtR2d/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Nov 13, 2005 at 07:14:00PM -0800, Mark Space wrote:
Hi all,
=20
I just set up the latest 6.0 release, and I'm getting errors with
Sorry for the late reply. I just read this thread and this issue affects
me as well. Hopefully I'm not commenting on something that has been
fixed but I can't test STABLE at the moment to verify that...
I understand the idea that bad values should be rejected, but in
reality, I have the
Hi,
I understand the idea that bad values should be rejected, but in
reality, I have the same DSL modem that these others have and there is
no way to change the domain search list that it sends. No way that I
could find at least. This is SBC-Yahoo in California, so there are a lot
of people
Hi,
I understand the idea that bad values should be rejected, but in
reality, I have the same DSL modem that these others have and there is
no way to change the domain search list that it sends. No way that I
could find at least. This is SBC-Yahoo in California, so there are a lot
of
Mark Andrews wrote:
Yes it is reasonable to expect ISP to fix things like this.
You pay the ISP to operate there part of the network within
the operational contraints of the RFCs (Standards track and
BCP).
I totally agree. Make sure when calling tech support on
I had this as well. It means that your DHCP server returns an invalid
search domain.
The easy way to solve it (if you have access) is to set the search
domain to something valid in your DHCP server (Linksys router by any
chance?). I couldn't find a flag on dhclient to tell it to ignore
On Sun, Nov 13, 2005 at 07:14:00PM -0800, Mark Space wrote:
Hi all,
I just set up the latest 6.0 release, and I'm getting errors with the
DHCP client. Trying to pull a network address during start up, I get:
Bogus domain search list 15: domain_not_set.invalid
This repeats several
Thanks to Sebastian and Brooks for their quick replies. I took the easy
way out and installed the ISC client which works just fine.
The problem is my DHCP server is a DSL modem. I don't see any way to
set the domain field. In addition, this interface is really not on a
network but a
--61jdw2sOBCFtR2d/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Nov 13, 2005 at 07:14:00PM -0800, Mark Space wrote:
Hi all,
=20
I just set up the latest 6.0 release, and I'm getting errors with the=20
On Mon, Nov 14, 2005 at 10:48:09AM -0800, Mark Space wrote:
Thanks to Sebastian and Brooks for their quick replies. I took the easy
way out and installed the ISC client which works just fine.
The problem is my DHCP server is a DSL modem. I don't see any way to
set the domain field. In
Hi all,
I just set up the latest 6.0 release, and I'm getting errors with the
DHCP client. Trying to pull a network address during start up, I get:
Bogus domain search list 15: domain_not_set.invalid
This repeats several times before giving up. Google tells me that this
problem was report
14 matches
Mail list logo
