[SOLVED] Fedora 12 VM on VMWare ESXi, I am able to VNC & SSH in, but eth0 is in active
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Fedora 12 VM on VMWare ESXi, I am able to VNC & SSH in, but eth0 is in active
In network it show eth0 inactive, and the activate buttons are grayed out... How do I activate it? I can VNC and SSH in no prob. but I cannot hit the internet. I turned off iptables as well.
Are you kidding me? that's your help? don't be such a condescending idiot. There is a solution for this issue, which is what I am looking for. not some joker to tell me ehhh not supported reinstall the latest version. Dude a new fedora version comes out every 6 months. I am not upgrading or reinstalling. I am actively using this machine. So if you wanna be helpful, go ask your mommy if you can borrow her laptop and research this issue then get back to me with an answer
actually don't.... don't even reply to any of my threads ever again. jerk
then do not use fedora
Fedora is a very fast passed research and development distro with a VERY short life ( 13 months and a new version EVERY 6 months)
if you are going to use fedora YOU MUST stay current
also i have been using fedora since fedora 4 -- so I DO KNOW a thing or two about fedora .
Blimey, you are both right. On the one hand, you have a distro that is in active use but on the other you will only get very limited support because of the nature of the distro. It may be that a fix requires files from Fedora 13 or 14.
What out put do you get from
Code:
ifconfig etho up
(or whatever the Fedora equivalent is). Have you made any changes prior to the failure?
i tried that, Like I said it shows an IP address on command line, I can VNC & SSH in no problem... and no it doesnt require files from a new distro. I may have made a change to something unknowingly, because it was working at one time. I just dont now where I should be looking.
people (including government agencies) use fedora, and they do not upgrade the distro, because of something like this. They troubleshoot the issue. Upgrading for something like this is for a newbie, its like "oh my xp machine is really slow, I will just re install xp" this is a forum for solutions and help not condescending remarks from some idiot who trolls looking for people he can talk down to. Like I said John if you dont have an answer then dont reply to my threads
What part of don't respond to my post do you not understand? You are a complete idiot, you are a schmuck you have no idea about anything. and you are just plain stupid. you ruined this thread for someone who may also have this issue. you are an idiot and you provide no help. people like you are what make this forum suck! i cant stress how badly i hate you and i hope you get aids.
PS John Dumb A$$ the reason this is a F12 box instead of 13 was because at the time of install 13 was highly unstable, and it still is. No one here ever asked for an update a kernel package anything. Refer back to the question you f-in loser. No one here cares about you, you suck and you are stupid. This not a matter of a package or an update needed you retard. it's about making an adjustment to something some where to get eth0 available again to be activated. AGAIN refer to the question, not what you think should be done bc you are wrong, stupid, and no one in life likes you. I'm not asking for support from Red Hat or the Fedora project, I am on a forum looking for help with eth0 on FC12. Go back to school and get a clue. No wonder why you don't have a girlfriend your 45 bald, fat, smell, and live in your moms basement
To People who are looking to this thread for an answer... I figured out that it was actually a reverse dns issue. I can do a forward lookup but the reverse was not correct or errored out. IT HAD NOTHING TO DO WITH A FEDORA UPDATE OR NEEDING TO UPGRADE THE OS. THERE WAS A SOLUTION TO THE PROBLEM AND IT DID NOT INVOLVE A DRAMATIC AND POSSIBLY DANGEROUS UNDERTAKING OF UPGRADING THE OS. IF THAT HAD HAPPENED THERE IS A POSSIBILITY THAT THE PROGRAMS AND SYSTEMS I HAVE RUNNING SMOOTHLY ON MY BOX MAY NOT HAVE WORKED ANY MORE, DUE TO DEPENDENCY ISSUES, OR CHANGES IN THE NEEDED LIBRARIES.
To John W. Again if you see me post a question on this site again do everyone in the community a favor and keep your thoughts to your self because your are WRONG. You claim your vast experience in Linux OS however your comments reflect the fact that you have no trouble shooting skills, no knowledge of OS, or networking and you rely on others to fix your issues by taking the easy way (to you) out of your issues. AGAIN DO NOT REPLY TO MY THREADS YOUR HELP IS NOT WELCOME! YOU ARE A CONDESCENDING KNOW IT ALL WITH NO HELPFUL ADVICE WHATSOEVER. I AND PROBABLY LOTS OF PEOPLE HERE CAN DO MUCH BETTER WITH OUT YOUR HELP.
I am marking this thread solved, as I have figured out the answer thru troubleshooting.
Clearly, and strangely, this thread needs to be closed. There was a lot of good advice in the thread, even if most of it was not welcomed in the vein it was given. Davide123: never respond like this to one of our members again. Updating an out of date version of an OS is one way to fix or diagnose the problem. All you had to do was to calmly and politely explain why this wasn't an option. Exploding into ALL CAPS is both unnecessary and childish.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.