My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC? Thanks! Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
--- "Fred A. Miller"
My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
These systems usually come with windows software to configure the modem. (I use Comcast cable, and have, ahem!, experience with Qwest DSL, but I expect this one's the same). All that software does is put your username/password and possibly some other configuration options into the modem. You can do this by hand using the micro-webserver on the modem. Depending on whose modem it is, connect your system to it via Ethernet, let it do dhcp, then browse http://192.168.0.1 or 192.168.1.1 or 192.168.2.1 (the 192.168.2.1 addres seems to be favored by Belkin, most others I've come across use 0.1 or less commonly 1.1) You will probalby find a bunch of helpful pages that discuss setup/configuration, and it should be pretty trivial to follow. Check the wireless capability of the device: leave it off if you don't want it, secure it to some extent if you do use it. The device might include a firewall--probably worth using, particularly if you'll have more connected to it than just the Linux system. It'll probably offer itself as DNS server. Hmm, if it's actiontec, you might want to bypass that if you get strange results! Scan through all the setup pages, and ask yourself if the configuration looks sensible (mainly from a security point of view). Have fun! Cheers, Simon __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Wednesday 11 January 2006 10:55 am, Simon Roberts wrote:
--- "Fred A. Miller"
wrote: My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
These systems usually come with windows software to configure the modem. (I use Comcast cable, and have, ahem!, experience with Qwest DSL, but I expect this one's the same). All that software does is put your username/password and possibly some other configuration options into the modem. You can do this by hand using the micro-webserver on the modem.
Depending on whose modem it is, connect your system to it via Ethernet, let it do dhcp, then browse http://192.168.0.1 or 192.168.1.1 or 192.168.2.1 (the 192.168.2.1 addres seems to be favored by Belkin, most others I've come across use 0.1 or less commonly 1.1) You will probalby find a bunch of helpful pages that discuss setup/configuration, and it should be pretty trivial to follow. Have fun!
Motorola SURFboard 5100 with Comcast uses 192.168.100.1.
Cheers, Simon
Stan
On Wednesday 11 January 2006 7:15 pm, Stan Glasoe wrote:
On Wednesday 11 January 2006 10:55 am, Simon Roberts wrote:
--- "Fred A. Miller"
wrote: My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
These systems usually come with windows software to configure the modem. (I use Comcast cable, and have, ahem!, experience with Qwest DSL, but I expect this one's the same). All that software does is put your username/password and possibly some other configuration options into the modem. You can do this by hand using the micro-webserver on the modem.
Ok.......Konq. can handle that. ;)
Depending on whose modem it is, connect your system to it via Ethernet, let it do dhcp, then browse http://192.168.0.1 or 192.168.1.1 or 192.168.2.1 (the 192.168.2.1 addres seems to be favored by Belkin, most others I've come across use 0.1 or less commonly 1.1) You will probalby find a bunch of helpful pages that discuss setup/configuration, and it should be pretty trivial to follow. Have fun!
Thanks!
Motorola SURFboard 5100 with Comcast uses 192.168.100.1.
Yes........common to a lot of routers also. Thanks for all the info. I can see that DSL (just coming to this area) isn't quite as "clean" and easy as setup as cable........RoadRunner anyway. Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On 1/11/06 10:36 PM, "Fred A. Miller"
On Wednesday 11 January 2006 7:15 pm, Stan Glasoe wrote:
On Wednesday 11 January 2006 10:55 am, Simon Roberts wrote:
--- "Fred A. Miller"
wrote: My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
These systems usually come with windows software to configure the modem. (I use Comcast cable, and have, ahem!, experience with Qwest DSL, but I expect this one's the same). All that software does is put your username/password and possibly some other configuration options into the modem. You can do this by hand using the micro-webserver on the modem.
Ok.......Konq. can handle that. ;)
Depending on whose modem it is, connect your system to it via Ethernet, let it do dhcp, then browse http://192.168.0.1 or 192.168.1.1 or 192.168.2.1 (the 192.168.2.1 addres seems to be favored by Belkin, most others I've come across use 0.1 or less commonly 1.1) You will probalby find a bunch of helpful pages that discuss setup/configuration, and it should be pretty trivial to follow. Have fun!
Thanks!
Motorola SURFboard 5100 with Comcast uses 192.168.100.1.
Yes........common to a lot of routers also. Thanks for all the info. I can see that DSL (just coming to this area) isn't quite as "clean" and easy as setup as cable........RoadRunner anyway.
Fred
I've got Verizon DSL, Cavtel DSL, T1, had Comca$t, etc. As others have said, once you configure the router (via any web browser) it handles the PPPoE for the network. You have to enter your login info to the router, then hit save. 9.1, 9.3 and 10 will work using the DHCP server in the router. I also had to use the router as a DNS server on every system I have- OSX and Linux. Don't remember about XP...but then that box doesn't go to the web or do email. Things worked fine and were easy to set up. You can handle it. FYI I use another firewall after the supplied router. On one system I have a D-Link, one a Netgear... All the CD does is install (on windows) a browser with their page as the home page. -- Thanks, George If Olive oil comes from olives, Corn oil comes from corn, Peanut oil comes from peanuts, Fish oil comes from fish, Where does baby oil come from?
On Wednesday 11 January 2006 11:01 pm, suse_gasjr4wd@mac.com wrote: [snip]
I've got Verizon DSL, Cavtel DSL, T1, had Comca$t, etc. As others have said, once you configure the router (via any web browser) it handles the PPPoE for the network. You have to enter your login info to the router, then hit save. 9.1, 9.3 and 10 will work using the DHCP server in the router. I also had to use the router as a DNS server on every system I have- OSX and Linux. Don't remember about XP...but then that box doesn't go to the web or do email.
It would be the same with any OS.
Things worked fine and were easy to set up. You can handle it.
Of course. ;)
FYI I use another firewall after the supplied router. On one system I have a D-Link, one a Netgear.
I prefer to have a firmware firewall "outside" the 'puter, then SUSE's firewall turned on as well. 'Been wondering if Bastille is better than SUSE's firewall, but haven't had time to check it out.
All the CD does is install (on windows) a browser with their page as the home page.
Ok.......I had assumed that's all it did/does. Verizon, of course, says they don't and won't support Linux. I said, "Yeah, yeah, yeah. It'll work." :) Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On Thursday 12 January 2006 04:22, Fred A. Miller wrote:
Ok.......I had assumed that's all it did/does. Verizon, of course, says they don't and won't support Linux. I said, "Yeah, yeah, yeah. It'll work." :)
Fred
Hi Fred, If you are using a router, you are asking them to support your use of a router. Whether you are using Linux or a Micro$oft product on your clients is no longer material. I have used a router for about 7 years now, and on the few occasions I need support, I say I am using a router, when the question of which version of Micro$oft operating system comes up. If they get insistent, I tell them that the client OS is irelevant, and I want service to my router. Of course, I take responsibility for everything from the router to the client PC, and if I can browse to the router, then that's my side clear. Vince
On Thu, 2006-01-12 at 17:15 +0000, Vince Littler wrote:
On Thursday 12 January 2006 04:22, Fred A. Miller wrote:
Ok.......I had assumed that's all it did/does. Verizon, of course, says they don't and won't support Linux. I said, "Yeah, yeah, yeah. It'll work." :)
Fred
<snip> I tell them that the client OS is irelevant, and I want service to my router. Of course, I take responsibility for everything from the router to the client PC, and if I can browse to the router, then that's my side clear.
Vince
Fred, Everything Vince says is correct, but... In the past I've rarely gotten a support person to get past "we don't support linux." Generally there are some fairly simple router configurations to make, and they usually are done through a web interface that works fine in linux, but they won't talk to you unless you're looking at a MIE screen. What I usually do is plug in a M$oft laptop, walk through the config options with the tech, then once the connection is confirmed just plug in the linux box, because like Vince correctly "stated the client OS is irelevant, and I want service to my router." So, it's kind of capitulating to the world of M$ only, but it might be the shortest distance between two points. Good luck, Regis
On Thursday 12 January 2006 18:03, Regis Matejcik wrote:
On Thu, 2006-01-12 at 17:15 +0000, Vince Littler wrote:
<snip> I tell them that the client OS is irelevant, and I want service to my router. Of course, I take responsibility for everything from the router to the client PC, and if I can browse to the router, then that's my side clear.
Vince
Fred,
Everything Vince says is correct, but...
In the past I've rarely gotten a support person to get past "we don't support linux." Generally there are some fairly simple router configurations to make, and they usually are done through a web interface that works fine in linux, but they won't talk to you unless you're looking at a MIE screen.
Possibly helps that at the moment I am with an ISP who supply [and therefore expect to support] routers. I just stone wall on what OS, and say I have my router's config in my browser, and they just get on with support. My first ISP was IBM in the days of OS/2, Ever since then I have never been of a mind to put up with nonsense about the OS, and I left the only ISP who tried it after very few months. My last contact with my ISP, I told the guy that I had a hardware router with a firewall, a SuSE box with a firewall acting as a second router and a linux network, and if I did boot anything to windows it was subnetted so it couldn't see the internet. "So you are unlikely to have virus problems", he said. I think where you have a capable ISP, they tend to look favourably on Linux and probably feel that Linux users cause them less grief per head, partly because the community tends to look after its own and partly because, even if they don't officially support Linux, they do have people around who know Linux and will informally assist. The less capable ISP's use script readers, who are probably already aware of their own technical limitations and therefore tend to try and close the call ASAP to keep their stats up. Vince
On Thursday 12 January 2006 3:30 pm, Vince Littler wrote:
The less capable ISP's use script readers, who are probably already aware of their own technical limitations and therefore tend to try and close the call ASAP to keep their stats up.
You "nailed" that one in the head. ;) Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On Thursday 12 January 2006 1:03 pm, Regis Matejcik wrote:
What I usually do is plug in a M$oft laptop, walk through the config options with the tech, then once the connection is confirmed just plug in the linux box, because like Vince correctly "stated the client OS is irelevant, and I want service to my router."
So, it's kind of capitulating to the world of M$ only, but it might be the shortest distance between two points.
I can do that, IF need be, but I doubt I'll need to. Thanks, Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On Thursday 12 January 2006 12:15 pm, Vince Littler wrote:
Hi Fred,
If you are using a router, you are asking them to support your use of a router. Whether you are using Linux or a Micro$oft product on your clients is no longer material. I have used a router for about 7 years now, and on the few occasions I need support, I say I am using a router, when the question of which version of Micro$oft operating system comes up. If they get insistent, I tell them that the client OS is irelevant, and I want service to my router. Of course, I take responsibility for everything from the router to the client PC, and if I can browse to the router, then that's my side clear.
Good point! Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
I do not have verizon but dslextreme. On thing I found out is that I initially connect to dslextreme using PPoE. After I connect, I then change the connection to DHCP. At the router I either turn it off or do a renew IP. The internet connection then seems to work. It seems that DSLExtreme examines the MAC address and from that point on, it allows me to connect on the internet with no problem. If I change router, I had to do that process again. The DLink g624 sems to do this automatically. suse_gasjr4wd@mac.com wrote:
On 1/11/06 10:36 PM, "Fred A. Miller"
wrote: On Wednesday 11 January 2006 7:15 pm, Stan Glasoe wrote:
On Wednesday 11 January 2006 10:55 am, Simon Roberts wrote:
--- "Fred A. Miller"
wrote: My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
These systems usually come with windows software to configure the modem. (I use Comcast cable, and have, ahem!, experience with Qwest DSL, but I expect this one's the same). All that software does is put your username/password and possibly some other configuration options into the modem. You can do this by hand using the micro-webserver on the modem.
Ok.......Konq. can handle that. ;)
Depending on whose modem it is, connect your system to it via Ethernet, let it do dhcp, then browse http://192.168.0.1 or 192.168.1.1 or 192.168.2.1 (the 192.168.2.1 addres seems to be favored by Belkin, most others I've come across use 0.1 or less commonly 1.1) You will probalby find a bunch of helpful pages that discuss setup/configuration, and it should be pretty trivial to follow. Have fun!
Thanks!
Motorola SURFboard 5100 with Comcast uses 192.168.100.1.
Yes........common to a lot of routers also. Thanks for all the info. I can see that DSL (just coming to this area) isn't quite as "clean" and easy as setup as cable........RoadRunner anyway.
Fred
I've got Verizon DSL, Cavtel DSL, T1, had Comca$t, etc. As others have said, once you configure the router (via any web browser) it handles the PPPoE for the network. You have to enter your login info to the router, then hit save. 9.1, 9.3 and 10 will work using the DHCP server in the router. I also had to use the router as a DNS server on every system I have- OSX and Linux. Don't remember about XP...but then that box doesn't go to the web or do email.
Things worked fine and were easy to set up. You can handle it.
FYI I use another firewall after the supplied router. On one system I have a D-Link, one a Netgear... All the CD does is install (on windows) a browser with their page as the home page.
-- Joseph Loo jloo@acm.org
On Thursday 12 January 2006 7:24 pm, Joseph Loo wrote:
I do not have verizon but dslextreme. On thing I found out is that I initially connect to dslextreme using PPoE. After I connect, I then change the connection to DHCP. At the router I either turn it off or do a renew IP. The internet connection then seems to work. It seems that DSLExtreme examines the MAC address and from that point on, it allows me to connect on the internet with no problem. If I change router, I had to do that process again. The DLink g624 sems to do this automatically.
There's a DSL setup in Yast in SUSE 10.0. Is that where you'd setup PPoE? NO provider around here uses PPoE, thus I haven't had to set it up before. Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On Thu, 2006-01-12 at 21:51 -0500, Fred A. Miller wrote:
On Thursday 12 January 2006 7:24 pm, Joseph Loo wrote:
I do not have verizon but dslextreme. On thing I found out is that I initially connect to dslextreme using PPoE. After I connect, I then change the connection to DHCP.
Doesn't work that way. PPPoE is the underlying connection that allows communication with a DHCP server for getting the rest of your network setup information so you can surf the internet. There is no connection change.
At the router I either turn it off or do
a renew IP. The internet connection then seems to work. It seems that DSLExtreme examines the MAC address and from that point on, it allows me to connect on the internet with no problem. If I change router, I had to do that process again. The DLink g624 sems to do this automatically.
There's a DSL setup in Yast in SUSE 10.0. Is that where you'd setup PPoE? NO provider around here uses PPoE, thus I haven't had to set it up before.
If the OP's PC is connected directly with the ISP's modem then he needs to setup the DSL connection in YaST. And it is PPPoE, PPP over Ethernet. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Thursday 12 January 2006 10:00 pm, Ken Schneider wrote:
There's a DSL setup in Yast in SUSE 10.0. Is that where you'd setup PPoE? NO provider around here uses PPoE, thus I haven't had to set it up before.
If the OP's PC is connected directly with the ISP's modem then he needs to setup the DSL connection in YaST. And it is PPPoE, PPP over Ethernet.
Ok......thanks! Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On Wed, 11 Jan 2006 22:36:41 -0500, you wrote:
On Wednesday 11 January 2006 7:15 pm, Stan Glasoe wrote:
On Wednesday 11 January 2006 10:55 am, Simon Roberts wrote:
--- "Fred A. Miller"
wrote: My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
These systems usually come with windows software to configure the modem. (I use Comcast cable, and have, ahem!, experience with Qwest DSL, but I expect this one's the same). All that software does is put your username/password and possibly some other configuration options into the modem. You can do this by hand using the micro-webserver on the modem.
Ok.......Konq. can handle that. ;)
Depending on whose modem it is, connect your system to it via Ethernet, let it do dhcp, then browse http://192.168.0.1 or 192.168.1.1 or 192.168.2.1 (the 192.168.2.1 addres seems to be favored by Belkin, most others I've come across use 0.1 or less commonly 1.1) You will probalby find a bunch of helpful pages that discuss setup/configuration, and it should be pretty trivial to follow. Have fun!
Thanks!
Motorola SURFboard 5100 with Comcast uses 192.168.100.1.
Yes........common to a lot of routers also. Thanks for all the info. I can see that DSL (just coming to this area) isn't quite as "clean" and easy as setup as cable........RoadRunner anyway.
I have a few clients using roadrunner - clean is a relative term. I'd rather use dialup. At least Verizon doesn't block business email as spam, irrelevant of what the user has to say about it. They've cost my clients hundreds of dollars and won't even return their phone calls. Every time I see one of those cable internet ads on TV I have to laugh. Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
On Wednesday 11 January 2006 11:23, Fred A. Miller wrote:
My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
Don't think it will be quite that easy but I've never had Verizon. Something or someone has to do a login and that could be in the setup of their DSL modem or you might have to run PPPoE and do it on the linux box. Probably someone with Verizon can tell you more.
I would say that's depending on your geometrical location. As you know, VZ consists of multiple networks historically. For example, if you are on east coast, you may get the service via old Bell Atlantic's network. Or may be via old GTE network. I think (I'm not sure though) both require PPPoE config to get authenticated. If you are however on the west coast, you most unlikely need to set up PPPoE for authentication. West coast VZs have changed their network to serve DSLs last a couple of years. In any case, you need to wait what you get installed by VZ It could be a modem. Or could be a router. You might have already chosen one out of some optional selections. It would be very hard to comment without knowing that kind of information. Toshi On Wed, 2006-01-11 at 11:23 -0500, Fred A. Miller wrote:
My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
On Wed, 11 Jan 2006 11:23:43 -0500, you wrote:
My son gets DSL from Verizon in the next couple of days. I have to do the setup........is it just a matter of installing the hardware and then auto-DNS to the NIC?
Thanks!
Fred
-- Paid purchaser of ALL SuSE Linux releases since 6.x
I also have Verizon DSL. It depends partly on if he's getting static or dynamic IP address. If it's static, there's no modem setup - plug it in and configure your firewall. If it's a dynamic IP address, the procedure isn't too different, but you'll need to make a few settings to the modem using a browser - it's all www based. Verizon support is actually pretty good, so you shouldn't have too much trouble with the settings. They do use several different modems though, so you'll pretty much have to go to their support people. One bit of urgent advice I'll give you though - set up a caching DNS as soon as you can - the response times on Verizons are lousy. Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
participants (11)
-
Bruce Marshall
-
Fred A. Miller
-
Joseph Loo
-
Ken Schneider
-
Michael W Cocke
-
Regis Matejcik
-
Simon Roberts
-
Stan Glasoe
-
suse_gasjr4wd@mac.com
-
Toshi Esumi
-
Vince Littler