Topic: No Connection to Internet - LAN Works OK

[DungaBee]

I've submitted a bug report for this, although I am not sure it's a bug so much as something borked on my end.  I hope it is OK to reach out for help here too.

The link to the bug report is:  http://bugs.contribs.org/show_bug.cgi?id=4825

I'll paste the same info here.  I've looked at similar threads here and tried the same things to no avail.  Hopefully someone my have some wisdom to pass my way.

Thanks again.

---------------------
I recently ran the command to correct the UTF-8 issue (yum update --enablerepo=smecontribs).
After running that command and the server rebooting, the server can no longer access the internet or anything on our WAN.

WAN and internet connectivity is done via a Snapgear FW and not SME.  SME is on server only mode but was acting as a primary DNS server so I could take advantage of the corporate DNS functions.

Pinging by IP also fails.  NSLOOKUP does not work.

In reading the forums, I tried to clear the squid cache and even rebuild the squid database to no avail.  Squid does seem to start and run normally and a telnet to port 3128 of the server from my PC results in a connection.

I CAN ping my laptop from SME which is on the same subnet.

Output from ifconfig is:

eth0      Link encap:Ethernet  HWaddr 00:A0:CC:27:03:9F
          inet addr:172.26.10.10  Bcast:172.26.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2821 errors:1 dropped:0 overruns:0 frame:0
          TX packets:94772 errors:2 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000
          RX bytes:286022 (279.3 KiB)  TX bytes:8277809 (7.8 MiB)
          Interrupt:10 Base address:0x4000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4536 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4536 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:361550 (353.0 KiB)  TX bytes:361550 (353.0 KiB)

Also:
lspci | grep -i ethernet
00:0a.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)

Thank you for your work on SME and for any assistance you can provide!
---------------------

[idp_qbn]

Hi, some questions to consider. Their answer may help you solve the problem, or help others to help you.

1) Can your laptop access the Internet?
2) Can your laptop "see" the FW?
3) Can you connect to the FW?
4) If none of the above, do you know the IP of the firewall.
5) Does Is your FW handle DHCP for your network? If so, does the IP address 172.16.10.10 match?
6) Do you have 2 DHCP servers? - this should not happen.
7) Can you reboot the FW (desperation measure only if all else fails) in case it has frozen.

Cheers
Ian

[DungaBee]

Hi, some questions to consider. Their answer may help you solve the problem, or help others to help you.

1) Can your laptop access the Internet?
2) Can your laptop "see" the FW?
3) Can you connect to the FW?
4) If none of the above, do you know the IP of the firewall.
5) Does Is your FW handle DHCP for your network? If so, does the IP address 172.16.10.10 match?
6) Do you have 2 DHCP servers? - this should not happen.
7) Can you reboot the FW (desperation measure only if all else fails) in case it has frozen.

Cheers
Ian

#7 was the winner!

You can check out the dialog in the Bugzilla report for all the details.

What was so strange is that ONLY SME was blocked from talking to the FW.  My laptop, my VOIP phone could both talk out of the FW to the internet and over our WAN.

No idea what the issue was within the FW, but a reboot solved it..go figure!  When in doubt, reboot!

Thanks for your reply and thanks to the SME team!