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.
Here is something which has been burning me for the past week.
I recenly bought a Netgear Wireless-N router. In the router admin I set up Port forwarding for SSH/FTP/HTTP, which is not working correctly. Upon calling Netgear for support they said it was something on my end, and it would cost me 100 dollars for their Super Support in order to fix the problem on my local machine. HA
So, I plugged my Linksys back in, set up port forwarding, and instantly SSH/FTP/HTTP works again.
What gives? What is the difference between the Netgear Port Forwarding as Compared to the Linksys. Linksys works without any problems and Netgear did not work at all. Is there really something I have to do on my local machine to set up Port Forwarding on a Netgear router?
This is just boggling since the Linksys works so seemlessly. If anyone has ran into this problem feel free to post about it. Also, if you have a fix, I would love to hear it, as my Linksys is old school, WRT54G, and I would like to get some use of out this fancy new N router.
You could disable Netgear's DHCP server (or Linksys', it doesn't matter) and connect one of its LAN ports to one of Linksys'.
You should be able to connect to your network via Netgear's wireless N, though other machines are connected to Linksys.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 184.108.40.206, KDE 3.5.8 and KDE 4.0 beta, Plu
That is odd if you set portforwarding up to the lan ip and port. If the linksys should work then should the netgear my thought. Which netgear model and which firmware. Have you updated to the latest firmware?
well for the linksys router i do not have to do anything, AT ALL. DHCP is enable and port forwarding still works. However, with the netgear, even with DHCP disabled port forwarding does not work. As I stated Netgear's support told me it was somethjing with my local machine's settings, while linksys required no setting changes at all, and worked right out of the box.
Does anyone know how to get the Netgear router to work correctly with port forwarding. Perhaps someone has had success with open firmware? It's very baffling to me how one would work so seemlessly and the other does not at all.