Results 131 to 137 of 137
Originally Posted by elija
Is your ethernet card plugged into your router?
Who is your ISP?
When I run
Code:
whois 128.129.175.117
it shows LogicaCMG Inc. All of which suggests ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 06-01-2012 #131Just Joined!
- Join Date
- May 2012
- Posts
- 96
I am plugged right into the wall as my ethernet cable is not long enough to hit the router we have. Do you suggest i try to find a way to plug it into the router (The router istelf is also plugged into the wall but into a different wall port than the one the Cent box is plugged into)
EDIT: I'm sorry! i mistyped my IP. its supposed to be 128.120.175.117. Can you whois that to see what comes up? all of the above info about me being plugged into the wall still might be a problem.
I am plugged right into the wall, do you suggest i instead find a way to get to the router instead? (as i said above the router is still plugged into the wall where internet from the college is provided).
Yes that is a decent summary. Don't forget the blacklisting. I will update the OP later (i'm typing this kind of in a hurry) with a full summary! (promise
)
Haha, thanks for sticking with me this long, as i have said before all of your guys' tremendous support has made this very annoying problem somewhat easy to deal with. You guys really know a lot (and are good at researching solutions)! I am glad to be apart of this forum and i feel like i will be here for a long time.
- 06-01-2012 #132Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,746
- 06-01-2012 #133Just Joined!
- Join Date
- May 2012
- Posts
- 96
replying from my phone so please excuse bad spelling.
Why exactly is it important to be plugged into the router? what will being plugged into the route provide me that straight into the wall doesnt?
- 06-02-2012 #134Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,746
the router provides you the security of being obscured behind NAT, as well as hopefully a built-in firewall on the router.
as to why it does not work when you go static, a DHCP server can be configured to require clients to use DHCP in order to get out. i don't know if that is it, though. are you sure all your static IP settings are right?
- 06-02-2012 #135
128.120.175.117 = ucdavis.edu which makes a bit more sense

Using your own router will give you control over your own network, which is then linked in to the larger network via the router being plugged in to the wall; it will let you use static IP addresses and as has been said, it provides additional security.If we hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate! (Zapp Brannigan)
Snakey Wakey!
The Fifth Continent reborn
- 06-03-2012 #136Just Joined!
- Join Date
- May 2012
- Posts
- 96
the forum wont let me edit my first post so im gonna post the summary here:
__________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ ______
Realtek RTL8111/8168B Ethernet Malfunction solved!
Summary: (The below summary is an edited version of ktech11's post on page 8 of this thread.)
The following commands should be done as root user to avoid conflicts.
Download the latest driver from realtek's site Realtek scroll to where it says Unix(Linux) and choose your mirror (US1 is the west coast mirror so that maybe the fastest.) I couldn't get an exact link so you will need to download it in the GUI.
In the terminal move to where you downloaded it (normally the user logged in to the gui's home directory e.g. /home/ktech11/Downloads)
Remove the r8169 (must be done as root)
verify it is uninstalledCode:rmod 8169
if it returns a result you you need to remove the driversCode:running lsmod | grep r8169
Extract the filesCode:rmod 8169
Move in to the newly created directoryHTML Code:tar -xjv f name-of-downloaded-file (you can use tab complete to do this)
(or whatever the name of the newly created directory is)Code:cd r8168
Run the autorun.sh script that is in that directory (to make sure it is in there, ls -l)
as root
(you may need to doCode:autorun.sh
but the first should work).Code:bash autorun.sh
Now blacklist the r8169 driver
Credit for this detailed walkthrough goes to realtek-dropping-packets-on-linux-ubuntu-and-fedora - foxhop.netCode:echo "blacklist r8169" >> /etc/modprobe.d/blacklist.conf
__________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ ______
The above should work and get the correct drivers installed for the Realtek 8111/8168B Ethernet Adapter.
If it does not work you may also need to disable SELinux.
To disable SELinux do the following:
Change the file from what it is now which should look like this:Code:vi /etc/selinux/config
to this (i have bolded the line that has changed):Code:# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=enforcing # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted
Note: I have a dinner to attend right now but i will add more relavant information to this summary when i get back and will try to make sure i get everything that was helpful. Please excuse my absence.Code:# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
Last edited by Silman; 06-03-2012 at 12:47 AM.
- 06-26-2012 #137Just Joined!
- Join Date
- May 2012
- Posts
- 96
Its been a while...i completely forgot about this thread and i wanted to finish the summary (i remembered not finishing last night when i was going to sleep and though "OH ****!").
The last thing i wanted to do was make sure that if someone has the same problem as me is that they PM me, i would be more than glad to help anyone who is having a similar issue! Don't hesitate at all because after all the help i got here as my first time posting in Linuxforums i am so grateful to the people who helped me and i want to share the experience!


3Likes
Reply With Quote
