SOLVED: outbound issue

[kcgr]

I read this thread: viewtopic.php?f=16&t=2343 and I seem to have the same issues.

I think an ubuntu update messed things up. It started with not being able to connect to the Amahi server. I pulled the HDD and booted on a machine with a monitor and changed the /etc/network/interfaces file to use a static IP.

/interface contents:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
# iface eth0 inet dhcp
iface eth0 inet static
address 192.168.1.132
netmask 255.255.255.0
gateway 192.168.1.1


if I # out the last 4 lines and unhash the line with dhcp, I cannot SSH to the unit at all.

Now I can access everything, BUT I cannot ping my router or anything outside the network. I can only ping machines on the home network. The amahi.org site thinks the server is down (of course since I cannot ping outside), and the apps section in the dashboard is unavailable. Typing "hda" in the address bar takes awhile for the dashboard to come up.

I've run # route add default gw 192.168.1.1 eth0 .. and that didn't help. I stall cannot ping the outer or connect outside.

here's the routing table:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun0
10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0



some more details

headless HP mediasmart server (using dns server but not using dhcp server)

I pass steps 1-4 on the troubleshooter and fail when I ping the router in step 5.
I didn't do the traceroute, because I cannot access the net to get the package.

any help would be appreciated.

[bigfoot65]

Have you modified anything else on your network? I am running Ubuntu with latest updates and have had no issues.

Seems like an update would not cause this problem.

[kcgr]

I updated the router firmware, but I have the exact same settings as before (static IP's etc). The first time this happened, it was a loose wire. The second time (this time) they were all snug. Then I started doing troubleshooting leading me to where I'm at now. I don't have any other network issues for any other device.

What I find odd, is if I make the /interfaces file back to the default values of: iface eth0 inet dhcp, I cannot ssh in. I'm also trying to ping the internal router address of 192.168.1.1, not an external address.

I'll remove the amahi from my router static IP assignment list and will reboot both units to at least check that variable.

Any other config file contents I can provide? config files?

[bigfoot65]

Did you shut down your network after the upgrade? Sometimes it's best to do a fresh start.

I presume you are not using the HDA as your DHCP server. If that is the case, what about DNS? Is that the HDA or your router?

[kcgr]

thanks for the tip. I checked the log of the router and found it was blocking the server. I think my wife blocked the wrong MAC-ID when she was trying to limit internet access for one of the kids.

This was driving me nuts, but now all appears to be OK.

This was a bit embarrassing.

Thanks again for your time and the hint.

[bigfoot65]

No problem. Glad it's resolved.