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 am going to physically connect the second LAN card now on the machine. What are the issues I have to take care? I want both of the LAN cards work in tandem and the second one should be our Internet Gateway. Please throw some light.
I have the same problem me too, except it's only for one of two nic's. I have currently flushed and rebuilt my routing tables, and iptables is empty with default INPUT, OUTPUT, FORWARD set to ACCEPT.
I can ping with my first nic, and get reasonable responses, but with my second nic i get
ping: sendmsg: Operation not permitted.
and that goes not only for ping, it seems to be something blocking the damn thing, and i can't figure out what
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
The title of the thread is such and the content good so it comes on google easy.
I just thought it was worth adding to all this that quite often on a LAN the ping error
is due to the firewall not letting anything out, and as shorewall is used by many,
worth saying "have a look in /etc/shorewall/policy or rules and be sure to have"
ACCEPT fw net all
(that is accept all outgoing traffic from the fw to the net.
It is better than stopping shorewall all together. To restart, as root
service shorewall restart (once rules or policy are edited)
But you might want to be more granulous than that...