Hello List; My SuSE 9.1 thinks it is on a 56K dial up modem. It is really hooked up to Warner Cable's Road Runner service. Any suggestion on the best way to get the correct setup? The current modem is a Toshiba PCX 1000 and there is a Linksys cable DSL router between the box and the modem. Not married to either piece of equipment and could change if necessary. Thanks in advance. -- "God bless us everyone."
On Tuesday 24 May 2005 9:10 pm, James F. Pirtle wrote:
Hello List;
My SuSE 9.1 thinks it is on a 56K dial up modem. It is really hooked up to Warner Cable's Road Runner service.
Any suggestion on the best way to get the correct setup? The current modem is a Toshiba PCX 1000 and there is a Linksys cable DSL router between the box and the modem. Not married to either piece of equipment and could change if necessary.
Since your box is connected to the Linksys, all you should need to do is configure via Yast -> Network Devices -> Network Card. The box doesn't care about the DSL modem on the other side of the Linksys. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Wed, 2005-05-25 at 00:10, James F. Pirtle wrote:
Hello List;
My SuSE 9.1 thinks it is on a 56K dial up modem. It is really hooked up to Warner Cable's Road Runner service.
Any suggestion on the best way to get the correct setup? The current modem is a Toshiba PCX 1000 and there is a Linksys cable DSL router between the box and the modem. Not married to either piece of equipment and could change if necessary.
Have the router handle the connection and DHCP. Go into yast and locate the section for network card "Choose the setup method" I'm using "Automatic address setup (via DHCP). Click the next button Host name is set to the name of your computer. As you can see mine is P-733. Select a suitable Domain Name, don't use a real domain name unless you have it registered, even then I'm not sure if it won't cause problems, perhaps someone will know. Click the update name servers and search list via DHCP, for the Name Server your's will most likely be 192.168.0.1, it's the same intranet address that you use to configure the router with. Click OK, and follow through to the end. That ought to do it. Mike
On Wed, 2005-05-25 at 00:42 -0400, Mike McMullin wrote:
On Wed, 2005-05-25 at 00:10, James F. Pirtle wrote:
Hello List;
My SuSE 9.1 thinks it is on a 56K dial up modem. It is really hooked up to Warner Cable's Road Runner service.
Any suggestion on the best way to get the correct setup? The current modem is a Toshiba PCX 1000 and there is a Linksys cable DSL router between the box and the modem. Not married to either piece of equipment and could change if necessary.
Have the router handle the connection and DHCP. Go into yast and locate the section for network card "Choose the setup method" I'm using "Automatic address setup (via DHCP). Click the next button Host name is set to the name of your computer. As you can see mine is P-733. Select a suitable Domain Name, don't use a real domain name unless you have it registered, even then I'm not sure if it won't cause problems, perhaps someone will know. Click the update name servers and search list via DHCP, for the Name Server your's will most likely be 192.168.0.1, it's the same intranet address that you use to configure the router with.
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP. The default address for linksys routers is 192.168.1.1 or at least it is for the two I have owned.
Click OK, and follow through to the end. That ought to do it.
Mike
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem, but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Wed, 2005-05-25 at 08:51 -0500, Joe Morris (NTM) wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem, but maybe not. I was just wondering if this is a common router problem. -- Joe Morris
If you have a local linux box running a caching dns server just point the windows box to it but also include your ISP name servers as well. The linksys I have (wrt54g) can supply a list of name servers but cannot act as a name server except for local dhcp addresses it has issued. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Wed, 2005-05-25 at 10:21, Ken Schneider wrote:
On Wed, 2005-05-25 at 08:51 -0500, Joe Morris (NTM) wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem, but maybe not. I was just wondering if this is a common router problem. -- Joe Morris
If you have a local linux box running a caching dns server just point the windows box to it but also include your ISP name servers as well. The linksys I have (wrt54g) can supply a list of name servers but cannot act as a name server except for local dhcp addresses it has issued.
Do you offhand recall (I don't) where in the configuration of the network card the nameserver info is entered? I opened up YAST2 a few times to check out what's there and I don't see anything mentioned other than the network address of my SMC @ 192.168.2.1 in the section for nameserver lookup, which is greyed out by default.
Do you offhand recall (I don't) where in the configuration of the network card the nameserver info is entered? I opened up YAST2 a few times to check out what's there and I don't see anything mentioned other than the network address of my SMC @ 192.168.2.1 in the section for nameserver lookup, which is greyed out by default. it is under "Host name and Name Server Configuration". if you have "Update name servers and search list via DHCP checked, then the
On Wednesday 25 May 2005 12:42 pm, Mike McMullin wrote: list will be grayed out. But, /etc/resolv.conf should be updated by DHCP to contain the name servers. Since I use a router, I normally update this manually with 2 Comcast and 2 non-comcast sites. (I should be running a name server locally, but am too lazy to spend the 3 minutes it takes to set it up). -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
On Wed, 2005-05-25 at 09:51, Joe Morris (NTM) wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem, but maybe not. I was just wondering if this is a common router problem.
My main router is an SMC Barricade SMC7008ABR (192.168.2.1), I have a secondary router (DI-604, 192.168.0.1) linked to this in another room, as far as nameserver configs go I opened up YAST2 and checked out the config on the network card I get thiis screen warning The resolver configuration file (/etc/resolv.conf) has been temporarily modified by dhcpcd. You have two options: Modify the current (changed!) version of the file Press 'Accept' now and continue editing other (non-resolver) data. You could return to this dialog later when the above service has terminated. The nameserver and domain search list section is greyed out, Change hostname via DHCP is checked. I can't off hand recall putting the name server addresses that I got from my ISP into this system, of the one I just upgraded to 9.3. Of course I could be missing something. Mike
On Wednesday, May 25, 2005 @8:38 AM, Mike McMullin wrote:
On Wed, 2005-05-25 at 09:51, Joe Morris (NTM) wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem, but maybe not. I was just wondering if this is a common router problem.
My main router is an SMC Barricade SMC7008ABR (192.168.2.1), I have a secondary router (DI-604, 192.168.0.1) linked to this in another room, as far as nameserver configs go I opened up YAST2 and checked out the config on the network card I get thiis screen warning
The resolver configuration file (/etc/resolv.conf) has been temporarily modified by dhcpcd. You have two options: Modify the current (changed!) version of the file Press 'Accept' now and continue editing other (non-resolver) data. You could return to this dialog later when the above service has terminated. The nameserver and domain search list section is greyed out, Change hostname via DHCP is checked. I can't off hand recall putting the name server addresses that I got from my ISP into this system, of the one I just upgraded to 9.3. Of course I could be missing something.
Mike
On my machine, I set the default gateway under routing to "192.168.1.1". I then went to Host Name and DNS, unchecked Update via DHCP, and entered "192.168.1.1" for "Name Server 1" and "local" for "Domain Search 1". That works great for me.
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem, but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server. Greg Wallace
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem, but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server.
Greg Wallace
What version of bind is running on your linksys router? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem,
but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server.
Greg Wallace
What version of bind is running on your linksys router?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That I don't know. I logged into it but couldn't find any reference to a bind version. Greg
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your
nameserver.
Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem,
but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server.
Greg Wallace
What version of bind is running on your linksys router?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind. On mine, a BEFSR41, I can configure the dns server entries to hand out to DHCP clients on the Linksys DHCP page, but that's not the same as running a DNS server. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server.
Greg Wallace
What version of bind is running on your linksys router?
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to DHCP clients on the Linksys DHCP page, but that's not the same as running a DNS server.
Scott Which is the point I was trying to send to Greg, Linksys routers do not run bind and therefore cannot be pointed to as a DNS server. If his entire network becomes unavailable when the nameserver was unavailable
On Fri, 2005-05-27 at 18:16 -0700, Scott Leighton wrote: then he does not have his local hosts files setup correctly (my best guess). On the wrt54g wireless router with third party firmware you can set it up to act as a local dns cache but it will not perform any internet address translations. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Friday, May 27, 2005 @ 6:24 PM, Ken Schneider wrote:
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
The setup you say you have now is what I had at one point and
changed
because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server.
Greg Wallace
What version of bind is running on your linksys router?
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to DHCP clients on the Linksys DHCP page, but that's not the same as running a DNS server.
Scott Which is the point I was trying to send to Greg, Linksys routers do not run bind and therefore cannot be pointed to as a DNS server. If his entire network becomes unavailable when the nameserver was unavailable
On Fri, 2005-05-27 at 18:16 -0700, Scott Leighton wrote: then he does not have his local hosts files setup correctly (my best guess). On the wrt54g wireless router with third party firmware you can set it up to act as a local dns cache but it will not perform any internet address translations.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
When I first installed SuSE, it defaulted to going out to my ISP, grabbing the name server addresses, and storing those as its name servers (you could see them from the YAST screen we were discussing earlier in this thread). Then, if I lost my connection to my ISP, my network would not start. I'd get a message saying it could not access my name server. Setting Linux to look to my router for names solved that problem. It checked the router for the name server and the router basically said it was ready to supply the names as needed. At least that's the behavior it exhibited at startup. Greg W.
On Sat, 2005-05-28 at 02:06 -0800, Greg Wallace wrote:
On Friday, May 27, 2005 @ 6:24 PM, Ken Schneider wrote:
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to DHCP clients on the Linksys DHCP page, but that's not the same as running a DNS server.
Scott Which is the point I was trying to send to Greg, Linksys routers do not run bind and therefore cannot be pointed to as a DNS server. If his entire network becomes unavailable when the nameserver was unavailable then he does not have his local hosts files setup correctly (my best guess). On the wrt54g wireless router with third party firmware you can set it up to act as a local dns cache but it will not perform any internet address translations.
When I first installed SuSE, it defaulted to going out to my ISP, grabbing the name server addresses, and storing those as its name servers (you could see them from the YAST screen we were discussing earlier in this thread). Then, if I lost my connection to my ISP, my network would not start. I'd get a message saying it could not access my name server. Setting Linux to look to my router for names solved that problem. It checked the router for the name server and the router basically said it was ready to supply the names as needed. At least that's the behavior it exhibited at startup.
Greg W. What do you mean by "my network would not start"? Do you mean that the ethernet interface would not come up? Do you have multiple PC's connected to the Linksys router? Also what model Linksys do you have as different models have different capabilities? Without going through the archives can you post you /etc/resolv.conf file?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Friday, May 27, 2005 5:17 PM, Scott Leighton wrote:
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
Ken Schneider wrote:
The Linksys router will be your default route but -not- your
nameserver.
Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem,
but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server.
Greg Wallace
What version of bind is running on your linksys router?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to
DHCP clients on the Linksys DHCP page, but that's not the same as running a
DNS server.
Scott
But it's just grabbing the ip address from the name server it sees at the ISP and handing it off to Linux, right? So as far as Linux is concerned, it is the name server (it doesn't know the difference). Greg W.
On Saturday 28 May 2005 2:56 am, Greg Wallace wrote:
On Friday, May 27, 2005 5:17 PM, Scott Leighton wrote:
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
Ken Schneider wrote: >The Linksys router will be your default route but -not- your
nameserver.
>Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the
same
name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP,
it
makes it a pain for a laptop. I thought it was maybe a Netgear problem,
but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1
IS
the name server.
Greg Wallace
What version of bind is running on your linksys router?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to
DHCP clients on the Linksys DHCP page, but that's not the same as running a
DNS server.
Scott
But it's just grabbing the ip address from the name server it sees at the ISP and handing it off to Linux, right? So as far as Linux is concerned, it is the name server (it doesn't know the difference).
No, that's not the way I understand it. It's passing the address of the nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Sat, 2005-05-28 at 11:22, Scott Leighton wrote:
On Saturday 28 May 2005 2:56 am, Greg Wallace wrote:
On Friday, May 27, 2005 5:17 PM, Scott Leighton wrote:
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote: >Ken Schneider wrote: >>The Linksys router will be your default route but -not- your
nameserver.
>>Use the name servers provided by your ISP. > >Is this a common problem with routers? I have a Netgear with the
same
>name server problems. For my linux machines I usually set up a > local caching DNS using the ISPs DNS as forwarders, which works > great for Linux but no such luck for Windows. Since they configure > via DHCP,
it
>makes it a pain for a laptop. I thought it was maybe a Netgear > problem, > >but maybe not. I was just wondering if this is a common router > problem. -- >Joe Morris >New Tribes Mission >Email Address: Joe_Morris@ntm.org >Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1
IS
the name server.
Greg Wallace
What version of bind is running on your linksys router?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to
DHCP clients on the Linksys DHCP page, but that's not the same as running a
DNS server.
Scott
But it's just grabbing the ip address from the name server it sees at the ISP and handing it off to Linux, right? So as far as Linux is concerned, it is the name server (it doesn't know the difference).
No, that's not the way I understand it. It's passing the address of the nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers.
Seems to make sense. So the OP seems to need the DNS server info for the Linksys configuration, and point his boxes to the router\switch.
On Saturday, May 28, 2005 @ 7:23 AM, Scott Leighton wrote:
On Saturday 28 May 2005 2:56 am, Greg Wallace wrote:
On Friday, May 27, 2005 5:17 PM, Scott Leighton wrote:
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote: >Ken Schneider wrote: >>The Linksys router will be your default route but -not- your
nameserver.
>>Use the name servers provided by your ISP. > >Is this a common problem with routers? I have a Netgear with the
same
>name server problems. For my linux machines I usually set up a > local caching DNS using the ISPs DNS as forwarders, which works > great for Linux but no such luck for Windows. Since they configure > via DHCP,
it
>makes it a pain for a laptop. I thought it was maybe a Netgear > problem, > >but maybe not. I was just wondering if this is a common router > problem. -- >Joe Morris >New Tribes Mission >Email Address: Joe_Morris@ntm.org >Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1
IS
the name server.
Greg Wallace
What version of bind is running on your linksys router?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to
DHCP clients on the Linksys DHCP page, but that's not the same as running a
DNS server.
Scott
But it's just grabbing the ip address from the name server it sees at the ISP and handing it off to Linux, right? So as far as Linux is concerned, it is the name server (it doesn't know the difference).
No, that's not the way I understand it. It's passing the address of the nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers.
Scott
That's the way it used to work (I'd see those ISP name server addresses in my Linux box). Once I overrode that to my Router IP address, that's the only address that showed up in Linux. Greg W
On Sunday 29 May 2005 5:14 am, Greg Wallace wrote:
On Saturday, May 28, 2005 @ 7:23 AM, Scott Leighton wrote:
No, that's not the way I understand it. It's passing the address of the nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers.
Scott
That's the way it used to work (I'd see those ISP name server addresses in my Linux box). Once I overrode that to my Router IP address, that's the only address that showed up in Linux.
Well, I'd love to know what model Linksys router you are using. I was unaware that any of them run a DNS server, but if you can simply point /etc/resolv.conf to your router and get DNS services, then the router must be running one. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Sunday 29 May 2005 11:27 am, Scott Leighton wrote:
On Sunday 29 May 2005 5:14 am, Greg Wallace wrote:
On Saturday, May 28, 2005 @ 7:23 AM, Scott Leighton wrote:
No, that's not the way I understand it. It's passing the address of the nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers.
Scott
That's the way it used to work (I'd see those ISP name server addresses in my Linux box). Once I overrode that to my Router IP address, that's the only address that showed up in Linux.
Well, I'd love to know what model Linksys router you are using. I was unaware that any of them run a DNS server, but if you can simply point /etc/resolv.conf to your router and get DNS services, then the router must be running one.
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT. Most Linksys routers have a firmware firewall, which isn't a bad idea when 'Bloze might be on the inside of it. Fred -- "BIG BROTHER IS WATCHING YOU!" Brought to you by the US Department of Homeland Security and the Patriot Act(s) numerous Presidential Directives, etc.
On Sunday 29 May 2005 8:58 am, Fred A. Miller wrote:
On Sunday 29 May 2005 11:27 am, Scott Leighton wrote:
On Sunday 29 May 2005 5:14 am, Greg Wallace wrote:
On Saturday, May 28, 2005 @ 7:23 AM, Scott Leighton wrote:
No, that's not the way I understand it. It's passing the address of the nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers.
Scott
That's the way it used to work (I'd see those ISP name server addresses in my Linux box). Once I overrode that to my Router IP address, that's the only address that showed up in Linux.
Well, I'd love to know what model Linksys router you are using. I was unaware that any of them run a DNS server, but if you can simply point /etc/resolv.conf to your router and get DNS services, then the router must be running one.
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT. Most Linksys routers have a firmware firewall, which isn't a bad idea when 'Bloze might be on the inside of it.
I stand corrected. I guess I have no clue what is going on, if I change the nameserver in /etc/resolv.conf to point to the Linksys at 192.168.1.1 it _does_ resolve. helphand@helphand:~> dig suse.com ;; Query time: 386 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun May 29 09:07:19 2005 ;; MSG SIZE rcvd: 117 So apparently there is some magic going on that I don't grok. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Sunday 29 May 2005 9:09 am, Scott Leighton wrote:
On Sunday 29 May 2005 8:58 am, Fred A. Miller wrote:
On Sunday 29 May 2005 11:27 am, Scott Leighton wrote:
On Sunday 29 May 2005 5:14 am, Greg Wallace wrote:
On Saturday, May 28, 2005 @ 7:23 AM, Scott Leighton wrote:
No, that's not the way I understand it. It's passing the address of the nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers.
Scott
That's the way it used to work (I'd see those ISP name server addresses in my Linux box). Once I overrode that to my Router IP address, that's the only address that showed up in Linux.
Well, I'd love to know what model Linksys router you are using. I was unaware that any of them run a DNS server, but if you can simply point /etc/resolv.conf to your router and get DNS services, then the router must be running one.
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT. Most Linksys routers have a firmware firewall, which isn't a bad idea when 'Bloze might be on the inside of it.
I stand corrected. I guess I have no clue what is going on, if I change the nameserver in /etc/resolv.conf to point to the Linksys at 192.168.1.1 it _does_ resolve.
helphand@helphand:~> dig suse.com ;; Query time: 386 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun May 29 09:07:19 2005 ;; MSG SIZE rcvd: 117
So apparently there is some magic going on that I don't grok.
Some googling reveals that many, but not all, of the Linksys boxes can operate as a DNS proxy. Apparently my BEFSR41 has that capability, which explains why it magically seems to work when putting the router address in /etc/resolv.conf Note that some of those same google sources recommended not doing so though. There were reports that the proxy feature was buggy and could cause long delays in DNS lookups. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Sun, 2005-05-29 at 10:55 -0700, Scott Leighton wrote:
On Sunday 29 May 2005 9:09 am, Scott Leighton wrote:
Some googling reveals that many, but not all, of the Linksys boxes can operate as a DNS proxy. Apparently my BEFSR41 has that capability, which explains why it magically seems to work when putting the router address in /etc/resolv.conf
Note that some of those same google sources recommended not doing so though. There were reports that the proxy feature was buggy and could cause long delays in DNS lookups.
Scott Which is why you would be better off setting up your own DNS server even if it is only used as a forwarder.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sunday 29 May 2005 11:38 am, Ken Schneider wrote:
On Sun, 2005-05-29 at 10:55 -0700, Scott Leighton wrote:
On Sunday 29 May 2005 9:09 am, Scott Leighton wrote:
Some googling reveals that many, but not all, of the Linksys boxes can operate as a DNS proxy. Apparently my BEFSR41 has that capability, which explains why it magically seems to work when putting the router address in /etc/resolv.conf
Note that some of those same google sources recommended not doing so though. There were reports that the proxy feature was buggy and could cause long delays in DNS lookups.
Scott
Which is why you would be better off setting up your own DNS server even if it is only used as a forwarder.
Agreed. I'm running a local caching only server myself. I only played around with this due to the OP's questions, and in the process learned quite a bit too <g>! I had no idea that the Linksys did DNS proxy, so his posted results were a curiosity to me. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Sunday 29 May 2005 17:58, Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.
What are you talking about, Fred? That's simply not true
....so will most HUBS. MANY HUBS will even do NAT.
huh?? A hub is a very simple device that connects a number of ethernet cables together. It has little or no intelligence. Certainly not to the point where it can do routing or network address translation
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
??? Lessee know, according to my calendar, April 1 was a few weeks back. Perhaps you're wrong? I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
On Sun, 2005-05-29 at 12:32 -0400, James Knott wrote:
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
I have owned two different Linksys routers, the most resent being a WRT54G. Neither, out of the box supports any DNS. I installed a third party firmware in the 54g which will only support supplying DNS for any DHCP addresses it hands out. Other than that it supplies no other DNS info. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
Not a chance. ;)
I've never heard of a hub that's capable of anything more that
Check out BestBuy and other stores sometime.
regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
You don't know much about hardware, I suspect. Fred -- "BIG BROTHER IS WATCHING YOU!" Brought to you by the US Department of Homeland Security and the Patriot Act(s) numerous Presidential Directives, etc.
Fred A. Miller wrote:
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT. ???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
Not a chance. ;)
I've never heard of a hub that's capable of anything more that
Check out BestBuy and other stores sometime.
regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
You don't know much about hardware, I suspect.
Since that I don't rely on Best Buy for info, probably not. However, given that I've got my Novell CNA, completed CNE course, TCP/IP and other networking courses at IBM, provided 3rd level support at IBM, installed a few networks along the way and much, much more, I may know a thing or two. You might want to have a chat with Rich Seifert (one of the creators of ethernet) in the comp.dcom.lans.ethernet newsgroup, about hubs and stuff.
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
'Just realized we're both maybe confused on this........I'm talking about handing out addresses, and maybe you are talking about real addresses from the Net. The original post on this had something to do with a cable modem, which gives out an address to a 'Puter, router, etc. In this case, a router question, MOST Linksys and other routers do provide addresses under Nat. as part of firewall. Maybe in my sleep deprived induced stupor I didn't understand what you said.....probably my fault. Fred -- "BIG BROTHER IS WATCHING YOU!" Brought to you by the US Department of Homeland Security and the Patriot Act(s) numerous Presidential Directives, etc.
On Sunday 29 May 2005 20:11, Fred A. Miller wrote:
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
'Just realized we're both maybe confused on this........I'm talking about handing out addresses, and maybe you are talking about real addresses from the Net.
That's DHCP, not DNS. And even then, not all boxes that do routing do DHCP
On Sunday 29 May 2005 2:11 pm, Anders Johansson wrote:
On Sunday 29 May 2005 20:11, Fred A. Miller wrote:
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
'Just realized we're both maybe confused on this........I'm talking about handing out addresses, and maybe you are talking about real addresses from the Net.
That's DHCP, not DNS. And even then, not all boxes that do routing do DHCP
True......not all do - just most. DNS IS passed on via most routers that I know of, including mine....a Linksys. Some routers and switches have a LOT more capability than they used to, as some others here have pointed out. Fred -- "BIG BROTHER IS WATCHING YOU!" Brought to you by the US Department of Homeland Security and the Patriot Act(s) numerous Presidential Directives, etc.
Fred A. Miller wrote:
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Fred A. Miller wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT. ???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
'Just realized we're both maybe confused on this........I'm talking about handing out addresses, and maybe you are talking about real addresses from the Net. The original post on this had something to do with a cable modem, which gives out an address to a 'Puter, router, etc. In this case, a router question, MOST Linksys and other routers do provide addresses under Nat. as part of firewall. Maybe in my sleep deprived induced stupor I didn't understand what you said.....probably my fault.
Well, I'm not the one confused about what those "firewall/router" boxes do.
On Sunday 29 May 2005 2:55 pm, James Knott wrote:
'Just realized we're both maybe confused on this........I'm talking about handing out addresses, and maybe you are talking about real addresses from the Net. The original post on this had something to do with a cable modem, which gives out an address to a 'Puter, router, etc. In this case, a router question, MOST Linksys and other routers do provide addresses under Nat. as part of firewall. Maybe in my sleep deprived induced stupor I didn't understand what you said.....probably my fault.
Well, I'm not the one confused about what those "firewall/router" boxes do.
No, but I knew that a lot routers can furnish DNS. ;) There's always all of us can learn, James. Fred -- "BIG BROTHER IS WATCHING YOU!" Brought to you by the US Department of Homeland Security and the Patriot Act(s) numerous Presidential Directives, etc.
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
Any router that is responsible for making the connection to an ADSL or cable (or wireless) ISP would have to take on the function of a DNS forwarder. Who else is going to get the DNS IP addresses? And who would the router hand them off to?
On Sunday 29 May 2005 20:21, Bruce Marshall wrote:
Any router that is responsible for making the connection to an ADSL or cable (or wireless) ISP would have to take on the function of a DNS forwarder.
I've seen enough connections that required you to enter the DNS servers by hand from a sheet of paper the ISP sent. You haven't? Also, if there is a DHCP server in that box, it could ship out the DNS IP addresses to the clients through that There is no "have to" here
On Sunday 29 May 2005 11:21 am, Bruce Marshall wrote:
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT.
???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
Any router that is responsible for making the connection to an ADSL or cable (or wireless) ISP would have to take on the function of a DNS forwarder. Who else is going to get the DNS IP addresses? And who would the router hand them off to?
I don't think that's true. Perhaps many consumer-level boxes on the market do have the DNS proxy feature, but I don't think they all do and it certainly isn't mandatory. If the box supports DHCP, it can just as easily hand out the DNS Server addresses and leave the proxying out of the picture. For that matter, a plain no-frills router could require the user to manually configure the PC side with the DNS server addresses. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
Bruce Marshall wrote:
On Sunday 29 May 2005 12:32 pm, James Knott wrote:
Really? 'Didn't know? ALL routers, no matter what make will hand out DNS addresses.....so will most HUBS. MANY HUBS will even do NAT. ???
Lessee know, according to my calendar, April 1 was a few weeks back.
Perhaps you're wrong?
I've never heard of a hub that's capable of anything more that regenerating and distributing packets. Also, a router does nothing more than forward layer 3 packets. Those Linksys and other boxes, include several functions, which *MIGHT* include DNS.
Any router that is responsible for making the connection to an ADSL or cable (or wireless) ISP would have to take on the function of a DNS forwarder. Who else is going to get the DNS IP addresses? And who would the router hand them off to?
Once it's obtained the info from the ISP, it can provide it to the computers, when they get their dhcp data.
On Sunday 29 May 2005 11:27 am, Scott Leighton wrote:
Well, I'd love to know what model Linksys router you are using. I was unaware that any of them run a DNS server, but if you can simply point /etc/resolv.conf to your router and get DNS services, then the router must be running one.
It was my impression that most routers that deal with the ADSL/wireless/cable connection will act as a DNS server or at least a forwarder. For example, the Dlink router I have here (DI624) does a pppoe connection to my broadband wireless rcvr and picks up the dns server addresses from the ISP. It then will pass on any dns requests to the ISP DNS servers.
On Sunday 29 May 2005 11:16 am, Bruce Marshall wrote:
On Sunday 29 May 2005 11:27 am, Scott Leighton wrote:
Well, I'd love to know what model Linksys router you are using. I was unaware that any of them run a DNS server, but if you can simply point /etc/resolv.conf to your router and get DNS services, then the router must be running one.
It was my impression that most routers that deal with the ADSL/wireless/cable connection will act as a DNS server or at least a forwarder.
For example, the Dlink router I have here (DI624) does a pppoe connection to my broadband wireless rcvr and picks up the dns server addresses from the ISP. It then will pass on any dns requests to the ISP DNS servers.
Yes, I subsequently discovered that the Linksys I have does DNS proxy. Probably the OP's box does the same, explaining his similar results. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
Recap: Laptop running 9.1Pro with a Cisco Aironet 350 card. Worked fine for home WLAN, but would not work with public hotspots (particularly, tmobile). Well, this has been quite a learning experience. Unfortunately, I don't think I'm quite done climbing the learning curve. But this is what I've found so far: 1: YAST network setup for wireless seems to have a bug, or perhaps a feature I don't quite grasp properly. I had the WEP key for my home WLAN set as one of the four available keys under YAST, and had no trouble at home. But when I tried to associate with the TMobile hotspot, I had to use 'iwconfig eth1 enc off' from the shell to associate to the unencrypted hotspot. This worked, but only for a little while -- after maybe 5min or so, if I used iwconfig to check on eth1's status, it would be back to using my home WLAN encryption key again. I had to keep fighting YAST from the command line. (Note: ESSID set under YAST was 'any') 2: 'iwconfig eth1 ap xxxx' was the command I wanted, for use in situations where multiple APs were in range. But for some reason the 'ap' option doesn't show up when I do an 'iwconfig --help'. All the other options do show up. 'essid' doesn't seem to work as a replacement. In fact, 'essid' can be downright counterproductive -- I tried using that first, and it made my 'iwconfig eth1' output *look* as if I was associated, when in fact I was not (But I was still learning iwconfig at that point -- it looks like the key is to double-check the AP MAC ID shown by iwconfig. If it's all FF:FF..., you're not associated). 3: working from the command line, once I realized what had been going wrong encryption-wise, I could dependably get my Aironet card to associate and draw an IP address from the hotspot AP/router. I could even, sometimes, get nameserver data to show up in /etc/resolv.conf, though this wasn't entirely consistent for reasons I haven't puzzled out. But-- 4: I still can't get any traffic to pass through. Ping and traceroute attempts against the DNS IPs shown in /etc/resolv.conf work sometimes, but other times give "destination unreachable" errors. Pinging or traceing anything by name rather than IP causes the command to hang for some time (~2-3min) before returning a "temporary failure of name resolution" or "unkown host" response. At this point, I believe I've got the purely wireless side of the problem licked, albeit in an inelegant fashion. So I suspect that I've moved into more mainstream network troubleshooting areas. Problem is, my grasp of the nuts&bolts of network operations, beyond using ping to check connections, is pretty weak (I can use route -n, for example, but I don't really understand what it's telling me). So if anybody knows a decent 'network primers for n00bs,' let me know, please? :) Something that really explains routing, DNS clients, and the other stuff I'm having trouble with would be nice. I *am* curious, though, as to why the YAST setup would keep overriding the iwconfig commands, even when I wasn't issuing any commands like 'rcnetwork restart,' 'ifup/down,' etc -- just trying 'ping' and 'traceroute.' Is there a background process that keeps resetting the interface to the YAST settings? And with only one key set up out of four, why would the system keep defaulting to that key, even when the YAST ESSID was set to 'any' and the only AP within range was unencrypted? As soon as I forced encryption off using iwconfig, the card associated instantly, without needing any more help (assuming I was in a one-AP environment), so I can't see it being an ESSID problem. Also, the KDE Control Center's Wireless Networks setup doesn't seem to work for me. I tried blanking out the YAST settings and using the KDE setup on my home WLAN, but no dice. I recall seeing some complaints here not too long ago that this program was problematical, so maybe it's not just me.
David McMillan wrote:
Recap: Laptop running 9.1Pro with a Cisco Aironet 350 card. Worked fine for home WLAN, but would not work with public hotspots (particularly, tmobile).
What I have done, is create different wifi config files and then just copy the appropriate one, to the wlan file. Then simply restart the interface. One of these years, I'm going to write a script, using Kdialog, to make the selection.
James Knott wrote:
David McMillan wrote:
Recap: Laptop running 9.1Pro with a Cisco Aironet 350 card. Worked fine for home WLAN, but would not work with public hotspots (particularly, tmobile).
What I have done, is create different wifi config files and then just copy the appropriate one, to the wlan file. Then simply restart the interface.
One of these years, I'm going to write a script, using Kdialog, to make the selection.
Forgot to mention. It would be nice if Kwifimanager actually worked, as it's supposed to take care of different configurations. However, in the four versions of SuSE (9.0 - 9.3) that I've had on my notebook, it's never worked properly.
James Knott wrote:
David McMillan wrote:
Recap: Laptop running 9.1Pro with a Cisco Aironet 350 card. Worked fine for home WLAN, but would not work with public hotspots (particularly, tmobile).
What I have done, is create different wifi config files and then just copy the appropriate one, to the wlan file. Then simply restart the interface.
Which files would those be, exactly? (Man, I wish I knew this stuff...) I went poking around, and found /etc/wlan/wlan.conf, which looked promising, but its contents don't resemble my settings. The script idea certainly sounds cool. In the meantime, I have found that changing my settings in YAST and rebooting allows me to connect problem-free to the hotspots I was having trouble with before, but now I can't connect to my home WLAN without changing YAST back, even using iwconfig from the command line to fix my settings. It really seems as if YAST is conflicting with iwconfig, somehow. And going into YAST every time I want to connect to a different wireless net seems like a really poor way of doing business.
David McMillan wrote:
James Knott wrote:
David McMillan wrote:
Recap: Laptop running 9.1Pro with a Cisco Aironet 350 card. Worked fine for home WLAN, but would not work with public hotspots (particularly, tmobile).
What I have done, is create different wifi config files and then just copy the appropriate one, to the wlan file. Then simply restart the interface.
Which files would those be, exactly? (Man, I wish I knew this stuff...) I went poking around, and found /etc/wlan/wlan.conf, which looked promising, but its contents don't resemble my settings. The script idea certainly sounds cool.
There's a config file /etc/sysconfig/network/ifcfg-wlan-id-<mac address>, which contains the info. Configure the card and copy the file to another directory. You can create multiple versions, for different networks.
James Knott wrote:
David McMillan wrote:
James Knott wrote:
David McMillan wrote:
Recap: Laptop running 9.1Pro with a Cisco Aironet 350 card. Worked fine for home WLAN, but would not work with public hotspots (particularly, tmobile).
What I have done, is create different wifi config files and then just copy the appropriate one, to the wlan file. Then simply restart the interface.
Which files would those be, exactly? (Man, I wish I knew this stuff...) I went poking around, and found /etc/wlan/wlan.conf, which looked promising, but its contents don't resemble my settings. The script idea certainly sounds cool.
There's a config file /etc/sysconfig/network/ifcfg-wlan-id-<mac address>, which contains the info. Configure the card and copy the file to another directory. You can create multiple versions, for different networks.
Huh! I don't have one. I *do* have one with the MAC-ID for my ethernet port (eth0), but nothing else with a MAC-ID in the filename. I *do,* however, have a file called ifcfg-wlan-bus-pcmcia that, when opened in an editor, that has settings that match my YAST setup. Hm... okay, making changes to my wifi card setup in YAST causes immediate changes to this file, but the changes don't seem to 'take' until I reboot. So if I use multiple versions of this file, and a script to swap them around, I need another command to force the card to re-apply the file. 'rcnetwork restart,' perhaps? Going back to the earlier problem for a moment, I've been playing around with the system, trying to learn by experimentation. So far, I've found that fixing the encryption from iwconfig causes immediate association to the Access Point, but dhcp doesn't seem to follow through. What I see from ifconfig is that eth1 will show an IP address, but /etc/resolv.conf remains blank. Activating the dhcpcd command manually doesn't do anything -- in fact, I tried it with Ethereal running, and running the dhcpcd command generated *no* packet traffic at all(!). And trying to ping my router at 192.168.0.1 from my laptop, which ifconfig is showing at 192.168.0.10, results in "destination network unreachable." Now, all my previous network experience is with Windows, but I'd been under the impression that with these IPs, that error was impossible. Could ifconfig possibly be showing me an IP that wasn't really assigned by DHCP? Does Linux have anything like that "automatic private IP" that WXP defaults to when it fails to get anything from a DHCP server?
David McMillan wrote:
James Knott wrote:
David McMillan wrote:
James Knott wrote:
David McMillan wrote:
Recap: Laptop running 9.1Pro with a Cisco Aironet 350 card. Worked fine for home WLAN, but would not work with public hotspots (particularly, tmobile).
What I have done, is create different wifi config files and then just copy the appropriate one, to the wlan file. Then simply restart the interface.
Which files would those be, exactly? (Man, I wish I knew this stuff...) I went poking around, and found /etc/wlan/wlan.conf, which looked promising, but its contents don't resemble my settings. The script idea certainly sounds cool.
There's a config file /etc/sysconfig/network/ifcfg-wlan-id-<mac address>, which contains the info. Configure the card and copy the file to another directory. You can create multiple versions, for different networks.
Huh! I don't have one. I *do* have one with the MAC-ID for my ethernet port (eth0), but nothing else with a MAC-ID in the filename. I *do,* however, have a file called ifcfg-wlan-bus-pcmcia that, when opened in an editor, that has settings that match my YAST setup. Hm... okay, making changes to my wifi card setup in YAST causes immediate changes to this file, but the changes don't seem to 'take' until I reboot. So if I use multiple versions of this file, and a script to swap them around, I need another command to force the card to re-apply the file. 'rcnetwork restart,' perhaps?
You could use the ifdown and ifup commands.
Going back to the earlier problem for a moment, I've been playing around with the system, trying to learn by experimentation. So far, I've found that fixing the encryption from iwconfig causes immediate association to the Access Point, but dhcp doesn't seem to follow through. What I see from ifconfig is that eth1 will show an IP address, but /etc/resolv.conf remains blank. Activating the dhcpcd command manually doesn't do anything -- in fact, I tried it with Ethereal running, and running the dhcpcd command generated *no* packet traffic at all(!). And trying to ping my router at 192.168.0.1 from my laptop, which ifconfig is showing at 192.168.0.10, results in "destination network unreachable." Now, all my previous network experience is with Windows, but I'd been under the impression that with these IPs, that error was impossible. Could ifconfig possibly be showing me an IP that wasn't really assigned by DHCP? Does Linux have anything like that "automatic private IP" that WXP defaults to when it fails to get anything from a DHCP server?
I haven't seen that for IPv4, though it's part of IPv6. I don't imagine it would be too hard to impliment. You essentially have to pick a "random" address and ping to see if anyone's using it. Failing that, just pick one and a Windows or Mac system should be able to find another address. Incidentally, in another message, I posted a link to the wificonfig rpm. Have you tried it? If not, could you please give it a try and let me know how it works for you. tnx jk
On Sunday 29 May 2005 5:14 am, Greg Wallace wrote:
On Saturday, May 28, 2005 @ 7:23 AM, Scott Leighton wrote:
No, that's not the way I understand it. It's passing the address of
On Sunday 29 May 2005 @ 5:14 AM, Scott Leighton wrote: the
nameservers to your Linux box via DHCP, your Linux box then uses those addresses for /etc/resolv.conf, so the end result is that your Linux box gets its list of DNS servers from the Linksys, but after that, it is simply resolving addresses using the servers that were on the list, the Linksys isn't directly involved. The Linksys isn't running a nameserver, it is only passing out the addresses of nameservers.
Scott
That's the way it used to work (I'd see those ISP name server addresses in my Linux box). Once I overrode that to my Router IP address, that's the only address that showed up in Linux.
Well, I'd love to know what model Linksys router you are using. I was unaware that any of them run a DNS server, but if you can simply point /etc/resolv.conf to your router and get DNS services, then the router must be running one.
Scott
My resolv.conf file contains --> nameserver 192.168.1.1 search local I'm using an RV042 Dual WAN router, but I had the same capability on my previous single WAN Router, which I fried. I don't remember what the model number on it was, but looking at the Linksys Web Site, it looks like it was a BEFSR41. Greg Wallace
On Sat, 2005-05-28 at 05:56, Greg Wallace wrote:
On Friday, May 27, 2005 5:17 PM, Scott Leighton wrote:
On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
Ken Schneider wrote: >The Linksys router will be your default route but -not- your
nameserver.
>Use the name servers provided by your ISP.
Is this a common problem with routers? I have a Netgear with the same name server problems. For my linux machines I usually set up a local caching DNS using the ISPs DNS as forwarders, which works great for Linux but no such luck for Windows. Since they configure via DHCP, it makes it a pain for a laptop. I thought it was maybe a Netgear problem,
but maybe not. I was just wondering if this is a common router problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The setup you say you have now is what I had at one point and changed because my entire network would be unavailable if that name server was unavailable (say the ISP was unreachable). You then have no name server. You should be able to just tell your machine that 192.168.1.1 IS the name server.
Greg Wallace
What version of bind is running on your linksys router?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
That I don't know. I logged into it but couldn't find any reference to a bind version.
Probably because the Linksys router does not run bind.
On mine, a BEFSR41, I can configure the dns server entries to hand out to
DHCP clients on the Linksys DHCP page, but that's not the same as running a
DNS server.
Scott
But it's just grabbing the ip address from the name server it sees at the ISP and handing it off to Linux, right? So as far as Linux is concerned, it is the name server (it doesn't know the difference).
I looked at my /etc/resolv.conf and it contains: nameserver 192.168.2.1 search mwmcmlln.ca the 192.168.2.1 is my SMC-Barricade broadband handler connected to an ADSL modem. the mwmcmlln.ca is now a valid and registered domain, but not when I set up this machine. the backup file /etc/resolv.conf.saved.by.dhcp contains the same entries.
On Wed, 2005-05-25 at 3:40 AM, Ken Schneider wrote:
On Wed, 2005-05-25 at 00:42 -0400, Mike McMullin wrote:
On Wed, 2005-05-25 at 00:10, James F. Pirtle wrote:
Hello List;
My SuSE 9.1 thinks it is on a 56K dial up modem. It is really hooked up to Warner Cable's Road Runner service.
Any suggestion on the best way to get the correct setup? The current modem is a Toshiba PCX 1000 and there is a Linksys cable DSL router between the box and the modem. Not married to either piece of equipment and could change if necessary.
Have the router handle the connection and DHCP. Go into yast and locate the section for network card "Choose the setup method" I'm using "Automatic address setup (via DHCP). Click the next button Host name is set to the name of your computer. As you can see mine is P-733. Select a suitable Domain Name, don't use a real domain name unless you have it registered, even then I'm not sure if it won't cause problems, perhaps someone will know. Click the update name servers and search list via DHCP, for the Name Server your's will most likely be 192.168.0.1, it's the same intranet address that you use to configure the router with.
The Linksys router will be your default route but -not- your nameserver. Use the name servers provided by your ISP. The default address for linksys routers is 192.168.1.1 or at least it is for the two I have owned.
Click OK, and follow through to the end. That ought to do it.
Mike
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On my network, my Linksys router is the name server as far as my Linux machine is concerned (I have 192.168.1.1 specified as the name server in Linux). I assume it just goes to the router and asks it for the ip address and the router then gets it from one of my ISP name servers and hands it back. At one point, ages ago, I had the ISP name server address in Linux (I suppose by default), which caused no end of problems if my ISP provider was unavailable (I couldn't access my network at all in that case, not even local addresses!). So, if you just specify 192.168.1.1 as the name server in Linux that should be all you need to do. Greg Wallace
On Tuesday 24 May 2005 23:10, James F. Pirtle wrote:
Hello List;
My SuSE 9.1 thinks it is on a 56K dial up modem. It is really hooked up to Warner Cable's Road Runner service.
Any suggestion on the best way to get the correct setup? The current modem is a Toshiba PCX 1000 and there is a Linksys cable DSL router between the box and the modem. Not married to either piece of equipment and could change if necessary.
Thanks in advance. -- "God bless us everyone." Thanks for all the help and suggestions. My problem got solved this evening when I did the YOU and got all the KDE updates. Now I'm crusing along at cable modem speeds.
But I seemed to have opened a whole new thread. I'll keep it open and listening. I'm learning something. Thanks again. -- "God bless us everyone."
participants (12)
-
Anders Johansson -
Bruce Marshall -
David McMillan -
Fred A. Miller -
Greg Wallace -
James F. Pirtle -
James Knott -
Jerry Feldman -
Joe Morris (NTM) -
Ken Schneider -
Mike McMullin -
Scott Leighton