[SLE] Going from analog to dsl modem... now what?
Greetings! Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network? Thanks! Christopher Reimer -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 03 May 2000, you wrote:
Greetings!
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
What software is running in windows? More to the point is it a pppoe client or just DHCP ? -- Bob F EMail BobFi@SWBell.net A Truly Wise Man Never Plays Leapfrog With A Unicorn... -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 03 May 2000, you wrote:
Greetings!
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
What software is running in windows? More to the point is it a pppoe client or just DHCP ?
The technician installed "NTS Ethernet 300" client that behaves quite similiar to the Windows Dial Up Network client. The DSL modem is using DHCP to get a dynamic IP and it is currently plug into the hub. (I plan on building a two NIC firewall box to take care of security.) I'm not sure if I need the pppoe or DHCP client. Christopher Reimer -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
...(I plan on building a two NIC firewall box to take care of security.) I'm not sure if I need the pppoe or DHCP client.
Most likely it'll be DHCP. I helped Jon Pennington set up the SuSEfirewall package on a machine to do just what you're going to do, and we used DHCLIENT on eth0 which hooked to the DSL modem via a cat-5 crossover cable, and DHCPD on eth1 which then hooked to a hub via a straight cat-5 cable. Worked like a champ. :-) If in doubt, configure what will be your firewall first to be a command line workstation with DHCLIENT linked to eth0, and that hooked to the DSL modem via a cat-5 crossover cable. If you can connect up to the outside world, the rest is just configuration. Good luck! I hope it pans out the way you want. Argentium -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 3 May 2000, Argentium G. Tiger wrote:
...(I plan on building a two NIC firewall box to take care of security.) I'm not sure if I need the pppoe or DHCP client.
Most likely it'll be DHCP. I helped Jon Pennington set up the SuSEfirewall package on a machine to do just what you're going to do, and we used DHCLIENT on eth0 which hooked to the DSL modem via a cat-5 crossover cable, and DHCPD on eth1 which then hooked to a hub via a straight cat-5 cable. Worked like a champ. :-)
If in doubt, configure what will be your firewall first to be a command line workstation with DHCLIENT linked to eth0, and that hooked to the DSL modem via a cat-5 crossover cable. If you can connect up to the outside world, the rest is just configuration.
From the description of his Windows client, Enternet, and the fact that he is with PacBell, it's most likely PPPoE. Also, the Westell DSL modem uses a standard cable, not crossover, from the modem to the network card, but it sounds like he already has that up and running with Windows.
Greg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 3 May 2000, Christopher D. Reimer wrote:
On Wed, 03 May 2000, you wrote:
Greetings!
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
What software is running in windows? More to the point is it a pppoe client or just DHCP ?
The technician installed "NTS Ethernet 300" client that behaves quite similiar to the Windows Dial Up Network client. The DSL modem is using DHCP to get a dynamic IP and it is currently plug into the hub. (I plan on building a two NIC firewall box to take care of security.) I'm not sure if I need the pppoe or DHCP client.
It's PPPoE. The dynamic IP is supplied by PPP, not DHCP. The Linux client actually works better than the Windows one. You may want to look into pacificnet.net as you can get a static IP for $10 per month. That's $39 to PacBell, and $10 to Pacificnet (first three months are free). PacBell is currently oversubscribed in SoCal and their PPPoE server was a little unreliable before I made the switch. Greg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 03 May 2000, you wrote:
On Wed, 3 May 2000, Christopher D. Reimer wrote:
On Wed, 03 May 2000, you wrote:
Greetings!
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
What software is running in windows? More to the point is it a pppoe client or just DHCP ?
The technician installed "NTS Ethernet 300" client that behaves quite similiar to the Windows Dial Up Network client. The DSL modem is using DHCP to get a dynamic IP and it is currently plug into the hub. (I plan on building a two NIC firewall box to take care of security.) I'm not sure if I need the pppoe or DHCP client.
It's PPPoE. The dynamic IP is supplied by PPP, not DHCP. The Linux client actually works better than the Windows one.
Think it's DHCP here guys. Notice he said the modem is plugged into a hub. My pppoe won't work with a hub. -- Bob F EMail BobFi@SWBell.net A Truly Wise Man Never Plays Leapfrog With A Unicorn... -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
----- Original Message ------
It's PPPoE. The dynamic IP is supplied by PPP, not DHCP. The Linux client actually works better than the Windows one.
Think it's DHCP here guys. Notice he said the modem is plugged into a hub. My pppoe won't work with a hub.
I been watching this thread a bit and I'm still confused. The Westel modem is connected to the hub in the port that has the switch enabled to crossover. (Don't need a crossover cable if you can switch it at the hub. ;) The windows software has no problem going over the NIC (192.168.1.4), through the hub, to reach the modem. PPPOE looks like it needs an interface (i.e., eth1) before it will do anything. I got the MAC address for the modem, but I don't see how I can use that. I'm sure about DHCP since I don't think it applies to this situation. Anyway, unless someone comes up with a better idea, I'm going to break out an old NIC and crossover cable to do this thing right. Christopher Reimer -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I been watching this thread a bit and I'm still confused. The Westel modem is connected to the hub in the port that has the switch enabled to crossover. (Don't need a crossover cable if you can switch it at the hub. ;) The windows software has no problem going over the NIC (192.168.1.4), through the hub, to reach the modem. PPPOE looks like it needs an interface (i.e., eth1) before it will do anything. I got the MAC address for the modem, but I don't see how I can use that. I'm sure about DHCP since I don't think it applies to this situation. Anyway, unless someone comes up with a better idea, I'm going to break out an old NIC and crossover cable to do this thing right.
That was an interesting side trip. Didn't get anywhere because the old NIC that I had required more work than I was willing to put in for a night. I decided to wait until I got my firewall box put together. In the meantime, I put the wvdial.dod back into service for the rest of the network and told my roommates to suck some eggs while I have the fastest Internet connection in the house. It's kinda ironic that the Windows client can work across the hub but the Linux client doesn't. <sigh> Christopher Reimer -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
BobF
Think it's DHCP here guys. Notice he said the modem is plugged into a hub. My pppoe won't work with a hub.
-- Bob F
EMail BobFi@SWBell.net
I have a CDSL (Nortel 1Meg Modem) and roaring penguin works great with this deal. rp-pppoe-1.8.tar.gz See http://www.roaringpenguin.com/pppoe.html Best Regards -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 3 May 2000, BobF wrote:
On Wed, 03 May 2000, you wrote:
On Wed, 3 May 2000, Christopher D. Reimer wrote:
On Wed, 03 May 2000, you wrote:
Greetings!
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
What software is running in windows? More to the point is it a pppoe client or just DHCP ?
The technician installed "NTS Ethernet 300" client that behaves quite similiar to the Windows Dial Up Network client. The DSL modem is using DHCP to get a dynamic IP and it is currently plug into the hub. (I plan on building a two NIC firewall box to take care of security.) I'm not sure if I need the pppoe or DHCP client.
It's PPPoE. The dynamic IP is supplied by PPP, not DHCP. The Linux client actually works better than the Windows one.
Think it's DHCP here guys. Notice he said the modem is plugged into a hub. My pppoe won't work with a hub.
Mine did. Plus the PacBell EnterNet 300 client is a PPPoE client. Greg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 3 May 2000, BobF wrote:
On Wed, 03 May 2000, you wrote:
Greetings!
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
What software is running in windows? More to the point is it a pppoe client or just DHCP ?
Most likely PPPoE since I had the same setup with PacBell. Got tired of it, changed ISPs to pacificnet.net (with PacBell still providing the line), got static IPs, and am living happily ever after. Anyways, PacBell supplies a PPPoE client for Linux that works well. Or if he's using a recent SuSE, then the other clients work well, too. Greg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, May 03, 2000 at 07:32:05PM -0700, Christopher D. Reimer wrote:
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
Firstly, congradulations. The world is your oyster now that you have a fat pipe like some of us have enjoyed for so long. Secondly, from experience (last night, actually), I'd *highly* recommend starting out with Coyote Linux, at http://www.coyotelinux.com/. It has basic firewalling (but not much to speak of), runs no unnecessary services, and allows (almost) full IP forwarding capabilities. The *best* part about Coyote is the fact that it has an incredibly easy setup process. Get the tarball and an msdos or vfat HD floppy disk, and you'll be up in no time at all. I'd recommend that you not use the pre3 release that was announced on freshmeat this week, though. Get one of the stable ones from the FTP site. -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | http://www.atipa.com /\\ Kansas City, MO, USA | 816-241-2641 x121 _\_V 6D04 39E0 CAE9 9ADA 2CA3 2EBE 898A 6C37 CA1E A29C -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, 4 May 2000, Jon Pennington wrote:
On Wed, May 03, 2000 at 07:32:05PM -0700, Christopher D. Reimer wrote:
Previously, I was using wvdial.dod and ip masquerading with an analog modem to get my network connected to the internet. Now I get Pac Bell DSL (dynamic IP) and a Westel DSL modem, I'm totally clueless on how to get my linux box to work with this new device. My windows system is running flawlessly with the provided software with a 911kps downward rate. Any ideas for the rest of my network?
Firstly, congradulations. The world is your oyster now that you have a fat pipe like some of us have enjoyed for so long.
Thank you.
Secondly, from experience (last night, actually), I'd *highly* recommend starting out with Coyote Linux, at http://www.coyotelinux.com/. It has basic firewalling (but not much to speak of), runs no unnecessary services, and allows (almost) full IP forwarding capabilities. The *best* part about Coyote is the fact that it has an incredibly easy setup process. Get the tarball and an msdos or vfat HD floppy disk, and you'll be up in no time at all.
I'm checking it out. It's a much updated Internet Router Project distribution that can run off a floppy. Cool... I just need to grab a couple of NICs and I can be in business. Thanks! Christopher Reimer -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (6)
-
agtiger＠coolnet.net -
BobFi＠swbell.net -
creimer＠rahul.net -
deem＠wdm.com -
ethant＠pacificnet.net -
jpennington＠atipa.com