Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So when i do the command iptables -L -n -v | grep eth0 , i get one ipaddress , but the bad part is i can't find where it is described (the eth0) and what ip address it has , i can't seem to find it anywhere in my server. Tried it to look up in /etc/network/interfaces but its not there even though there is wifi , wlan , wan ect. Any ideas how to find it where it is?
Distribution: Redhat, Fedora, Open BSD, FreeBSD, SlackWare
Posts: 115
Rep:
what I understand you try to find your eth0 interface IP? if correct then use ifconfig command.
if not then kindly share your distro name and version, and try to specific your question.
waiting.
what I understand you try to find your eth0 interface IP? if correct then use ifconfig command.
if not then kindly share your distro name and version, and try to specific your question.
waiting.
Ifconfig command still dosen't show the eth0 , yes i want to find where the eth0 is hidden and what the ip address it has. if i type ifconfig i only see bond0 , bond0:0 , int0 , int1 ,lo , wan , wifi. Theres no eth0 :/
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.10 (squeeze)
Release: 6.0.10
Codename: squeeze
Actually ifconfig shows only the interfaces that are set as up.
Try to run ifconfig -a to display all the interfaces available (even if down). If eth0 shows up in this case it means that eth0 is not configured properly and you need to do it (giving it an IP address, netmask, gateway...). Only after that (hopefully!) it will shows up with a corresponding IP address...
Moreover I see you have bond0 interface which may contain eth0 as slave interface. In that case bond0 is the interface you should consider not eth0. To see which interface are bounded under bond0 just type something like:
If you are seeing interfaces with names like en0, follow that link.
iptables is the firewall capability built into the Linux kernel. Linux "firewall" programs are normally frontends for iptables. The one I would recommend for a GUI frontend is gufw.
Actually ifconfig shows only the interfaces that are set as up.
Try to run ifconfig -a to display all the interfaces available (even if down). If eth0 shows up in this case it means that eth0 is not configured properly and you need to do it (giving it an IP address, netmask, gateway...). Only after that (hopefully!) it will shows up with a corresponding IP address...
Moreover I see you have bond0 interface which may contain eth0 as slave interface. In that case bond0 is the interface you should consider not eth0. To see which interface are bounded under bond0 just type something like:
Code:
cat /proc/net/bonding/bond0
ifconfig -a if i do this it dosen't show the eth0 and if i go cat /proc/net/bonding/bond0 the slave interfaces are int0 and int1 , still no eth0.
if i do:
the first line is in INPUT section of iptables and the second line is in the FORWARD section of the iptables. I need to find where the eth0 is to know where the firewall sends the user who logins from that port.
I suppose this probably means that as mentioned by frankbell in your case the interfaces are called int0, int1,.. instead of eth0, eth1,...
Anyway how many physical interfaces are connected to your machine?
Moreover if bond0 has been set up using as slave int0 and int1 usually the iptable rules should be done on the interface bond0 and not on the separately on each slave interface...
It could be simply that the iptable rules involving eth0 have been set up wrongly...
Finally is the bond0 interface configured and working properly? Why exactly you are trying to find an interface called eth0 on your system?
I suppose this probably means that as mentioned by frankbell in your case the interfaces are called int0, int1,.. instead of eth0, eth1,...
Anyway how many physical interfaces are connected to your machine?
Moreover if bond0 has been set up using as slave int0 and int1 usually the iptable rules should be done on the interface bond0 and not on the separately on each slave interface...
It could be simply that the iptable rules involving eth0 have been set up wrongly...
Finally is the bond0 interface configured and working properly? Why exactly you are trying to find an interface called eth0 on your system?
There are alot like really alot it's a schools serve. I need it for my work i need to learn which port leads where so i can then tell other administrator so he can set up a mikrotik . Like in iptabbles i know every each where it leads etc. but his specific one i can't find what the ip address eth0 has , and the bad part is it's not me who setted up the firewall it's few other administrators and we took the job from them.
I'm not sure I understood clearly your set-up and what you would like to achieve.
Could you please post the output of the command ifconfig -a?
Moreover could you also describe which firewall rules you would like to have implemented in iptables (for example which ports need to be open on which interface)?
In doing that be sure to not show information you don't want to show like IPs...
I'm not sure I understood clearly your set-up and what you would like to achieve.
Could you please post the output of the command ifconfig -a?
Moreover could you also describe which firewall rules you would like to have implemented in iptables (for example which ports need to be open on which interface)?
In doing that be sure to not show information you don't want to show like IPs...
i don't really want to change anything in firewall i just want to understand why there is an eth0 even though it's nowhere to be seen to be described, i just want to understand where the eth0 sends the user who logs in through the port 3389 to what ip address he is sent.
OK. It seems you have two (one real + one virtual) non-wireless interfaces active: bond0, bond0:0 (at least both of them show an IP). The interface named "eth0" does not appear there so it means that actually you don't have any nic with that name on your system. As already mentioned the fact that iptable has defined some rules involving the interface "eth0" does NOT assure an interface named "eth0" is actually installed on your system. I guess in your case all the iptable rules involving "eth0" are wrong (or maybe they refer to a previous configuration of the same server when "eth0" was present) and should be removed.
The relevant non-wireless firewall rules should be listed by the command:
Code:
iptables -L -v -n | grep bond0
Last edited by gda; 07-27-2016 at 08:10 AM.
Reason: typo
OK. It seems you have two (one real + one virtual) non-wireless interfaces active: bond0, bond0:0 (at least both of them show an IP). The interface named "eth0" does not appear there so it means that actually you don't have any nic with that name on your system. As already mentioned the fact that iptable has defined some rules involving the interface "eth0" does NOT assure an interface named "eth0" is actually installed on your system. I guess in your case all the iptable rules involving "eth0" are wrong (or maybe they refer to a previous configuration of the same server when "eth0" was present) and should be removed.
The relevant non-wireless firewall rules should be listed by the command:
Code:
iptables -L -v -n | grep bond0
Wow mate , thanks i seem to understand a bit what are you saying ant it makes sense because there were like few system administrators before me and it's make senses that can be the situation here with eth0 . Thanks alot!!
Knowing the distro and version would help but I think that frankbell is correct that the naming scheme is the newer BSD style made to be more verbose in the identification of devices.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I'm lost , eth0 , iptables.
