mint 17 stopped connecting to internet (solved)

[PatH57]

that is really strange are you sure the first one is 17 and the second one 13? not the other way around?

169.254.0.0

this is an internal address assigned if the unit cannot get a dhcp address from the dhcp server or router.
In any case let's try this.
on Mint 17 right click on network manager applet, edit connections and select ethx (where x is 0 or 1)
address: 192.168.2.50
netmask: 255.255.255.0
gateway: 192.168.2.1

save and see if the connection works. BTW what's the router/modem you are using?

[dazhann2]

Re checked route -n on 13 and it is as listed . I"ll reboot to 17 now and make the changes your've suggested

[dazhann2]

Made changes still no connection. Checked route -n was as listed, it was. My modem is a belkin

[PatH57]

in 17 post:

Code: Select all

ifconfig

Code: Select all

uname -a

[dazhann2]

eth0 Link encap:Ethernet HWaddr 00:13:72:23:ec:18
inet addr:192.168.2.50 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fe23:ec18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17 errors:0 dropped:1 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3034 (3.0 KB) TX bytes:82 (82.0 B)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:253 errors:0 dropped:0 overruns:0 frame:0
TX packets:253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18867 (18.8 KB) TX bytes:18867 (18.8 KB)

darryl@darryl-OptiPlex-GX520 ~ $ uname -a
Linux darryl-OptiPlex-GX520 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:31:42 UTC 2014 i686 i686 i686 GNU/Linux

[PatH57]

kind of running out of ideas especially if it was working before...
put the ip back to autodetect.
then

Code: Select all

gksu gedit /etc/resolv.conf

and add

nameserver 8.8.8.8
nameserver 8.8.4.4

save the file
don't reboot, just disconnect and reconnect
the check if you got an IP and if you can browse

Code: Select all

ifconfig

[dazhann2]

Once again thanks for your continued help
Did above still no connection. Can I delete and reinstall network manager, just a thought, as I'm seriously considering doing a total os reinstall!
darryl@darryl-OptiPlex-GX520 ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:72:23:ec:18
inet addr:192.168.2.9 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fe23:ec18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99 errors:0 dropped:3 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11957 (11.9 KB) TX bytes:592 (592.0 B)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:3511 errors:0 dropped:0 overruns:0 frame:0
TX packets:3511 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:248535 (248.5 KB) TX bytes:248535 (248.5 KB)

[PatH57]

sure you can, at this point I'm running out of ideas anyway.
But before you do could you post your var/log/apt/history.log? (you probably have to compress it and attach it)

[dazhann2]

I think its attached?

[PatH57]

can't see anything specific about network but it gave me an idea.
remove /etc/udev/rules.d/70-persistent-net.rules. It will be recreated on the next reboot with numbering in the order the kernel sees the devices

[dazhann2]

It will not allow me to delete, that option is not able to be selected

[PatH57]

you need to open the folder rules.d with administrator (right click on it and select open as administrator)

[dazhann2]

ok Ive fixed it. I deleted my firewall and reinstalled internet now working
I installed and set it up when I first installed 17, so i don't know why it started
blocking all traffic.
Thanks for all your time its people like yourself who make this forum work

[PatH57]

firewall

had it in mind yesterday but forgot about it as I use one on my router and centralize all settings from there (so when it goes belly up I notice it on all my machines)
Have to put it back in my troubleshooting steps.
was it UFW?
seems also JeremyB was on it when he asked about iptables...

[dazhann2]

Yes it was/is ufw.

[PatH57]

check in var/log/apt/history.log if there was a recent update of it? as I'm not using it I can't check it.

[dazhann2]

No update there.