Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I'm running Mandrake 8.1 as a firewall/router for my LAN which has 4 Win98 boxes. I'm connected to the Internet via DSL on the Linux box (as eth1) and get my external IP address via DHCP from my ISP. Twice in the past three weeks I've apparently failed to renew the lease on the address, and lost connectivity. Both times, rebooting the Linux box brought everything back -- but that seems to be a Win9x solution rather than a *nix way to do things. Can someone tell me the sequence of commands needed to force renewal without taking the system down to do so?
I'd also like to know how to make portsentry work; it appears that my firewall (iptables) is preventing any scan attempts from getting to portsentry. My logs show a dozen or more attempts to get into port 111 each day (I maintain an open FTP server, which is a beacon for the script kiddies), but portsentry doesn't have anything in its files to reflect that...
No trace of a "pump" command but I suspect that "service network restart" should do the trick. Will try that next time it happens.
Agreed that rebooting isn't a Good Thing. That's one of the major reasons I switched over for the firewall/router box (which is doubling as a file server but using a different drive). The other was to have better control of my system...
As best I've been able to determine, swbell.net isn't using PPPoE. It acts more like a simple WAN; while I'm paying only for a dynamic IP, for the first 11 months I had the service it never changed. Then the network went down for several days and when it came back up I had a new IP, which has remained constant for almost 5 months now. The "DSL modem" is a SpeedStream 5260 with four LEDs on the front of it. When the service won't let me connect to anything outside, all four of them are still showing green; I would expect the DSL light to be off, if the DSL connection was actually gone.
Last time it happened I checked "route" to make certain I still had the gateway configured; all looked good but I wasn't able to ping the gateway using its IP address until after the reboot -- and then everything worked again.
Next time I'll try "service network restart" and see if that does the trick. I suspect it's something a bit flaky in the way swbell.net handles its DSL circuits in this area, possibly causing the other end to stop listening to me...
I did, however, determine that swbell.net really does use PPPoE; now I'm wondering how I've managed to stay connected as well as I have, and why I wasn't able to configure the internet NIC (eth1, not eth0) for PPPoE using Mandrake Control Center... I did download a generic PPPoE script from the swbell ISP tech support site but am not certain how well it will work with the Mandrake setup, which is similar to Red Hat but not exactly the same in all respects...
I had no luck with their software, it was outdated and I had rp already installed.
I started by running adsl-setup, he gave me a name and password to enter.
By the time he could tell me they did not support Linux and I said thats ok you don't need to support it. I saw the lights flash a few times and I knew It was connected.
Don't let them give you any crap either. If the link light is flashing it's not in your system and it will came up when the light locks in. The only thing, you might have to power cycle the modem.
Ours went out last month and it took them a week to come out and give us a new modem, the other one had bit the dust.
If it goes out tell them you want a phone number for free dialup access until it's fixed. Your login and password will work. They did not hesitate to give me one. It was really something having 25 people on a dialup account.
Last edited by DavidPhillips; 12-19-2001 at 02:23 PM.
I get the same kind of issue when running on a Wireless ISP connection. Doing and ifconfig eth0 down and the a up doesn't renew the address, nor does running the network interface configuration. A reboot is the only thing I have found thus far that does it. The ISP connection is not a PPPoA/E type service. Basically it's a web page log in currently but they are supposed to be working on some other authentication types.
In my Mandrake 10 box I have 2 ethernet cards. Eth0 goes to a Linksys WET 11 bridge that connects to an antenna for my ISP connection. Thus it handles all the wirless configuration portion but is transparent as far as addressing is concerned. I will have to try the network restart command suggested above to see if that works.
One other thing...if that does work how would somone get that to run automatically? Right now I'm away from home and my connection has failed in this way. Is there a good script that you could use to detect if you have an active connection to the ISP gateway and if not to try some kind of reset commands to bring it back up?
You could actually have a script that runs all of the time which will ping an address to see if there is a connection, then restart networking if it's down. You may want to ping by name if it turns out to be a dns problem.
It would seem that if this uses dhcp you should be able to restart it using dhcpcd or dhclient.