On Wednesday 21 July 2004 06:06, Lule George William wrote: > > Never been good at drawing so I'll stick to explaining. > The serial cable from the ISP's equipment goes into our router and from > the router we pick a cat5e cable that is connected straight into one of > the NICs of our proxy/firewall. Then another cat5e cable comes out of > the second proxy/firewall NIC into a switch(Cisco 2950) from which the > rest of the machines feed.
Sorry to be coming in late, but I really need to go home (been out, besides Friends is on Tv :)). You say this PC is connected to a Catalyst switch. Have you checked the switch to make sure there are no VLAN's configured? Have you checked the switch port connected to the faulty SuSE Linux interface to see whether it can give you any info? > > > Can the Suse box ping both its own interfaces? > > Beautifully!!! 0% packet loss. Of course, it uses the loopback interface :). > > > Can the Suse box ping the router? vice-versa? > > My friend, this is what I've been screaming about all along. It cannot. > For more details please see my earlier postings. > Just done the ping from the router, no response from the proxy. If you tested that both interfaces are working fine, it's definitely not a driver problem. You also seem to mention the firewall isn't the problem either. Check your switch port configuration again. Make sure you have no VLAN configurations, or that if you do, they are correct as per your topology. VLAN's cause separate switches within a switch, so you need a router to connect one VLAN to another. If the router and the box are in 2 different VLAN's, with no router in between, nothing will work. > > > > In this state, I > > > accidentally left the ping command running and went to check out on > > > someone and the router replied to only two pings out of 1002 ping Hmmh, interesting, then maybe it works after all :). Paste some output of 'sh int fa0/x' from your switch port connected to the box and the router. DO NOT clear the counters just yet! > > (don't > > > > ask me the percentage it calculated. Its embarrasing), but that is > > the > > > > situation right now. > > > > What is the router saying? [the logs] > > Very quiet about any traffic from the proxy!! Try running Netflow switching to capture any traffic hitting the router interface(s), to tell whether it's getting anything at all. Try a tcpdump on the box too. Mark. --------------------------------------------- This service is hosted on the Infocom network http://www.infocom.co.ug
