hugosantos Posted June 12, 2004 Report Share Posted June 12, 2004 I've some problems setting up the network card running under Mandrake 10. With Suse 9.0 it went fine but with mandrake no. No pings allowed to other netwoking machines (Windows). I've exactly the same problem that nawialkair memeber but I'm trying to connect to a proxy under a windows machine but I cannot even get the network card starting to ping. Any Ideas? Good software is proportional function to stability, fast results on settings and production. Linux must work harder to get there. Thanks. Link to comment Share on other sites More sharing options...
streeter Posted June 12, 2004 Report Share Posted June 12, 2004 If you still have MDK installed :) , post same info as requested from nawialkair... Chris Link to comment Share on other sites More sharing options...
hugosantos Posted June 12, 2004 Author Report Share Posted June 12, 2004 Well your're correct! (and I still have MDK...I'm a patience guy) Some things are getting stronger and better: KDE and OpenOffice! hurray for them. Amazing how can they be so much better than commercial packages. About the problem... I suppose it won't help much but nevertheless here it is: Ifconfig: eth0 Link encap:Ethernet HWaddr 00:30:1B:26:A0:3D inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::230:1bff:fe26:a03d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:16 overruns:0 frame:0 TX packets:0 errors:7 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Base address:0xe400 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:16436 Metric:1 RX packets:148 errors:0 dropped:0 overruns:0 frame:0 TX packets:148 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11162 (10.9 Kb) TX bytes:11162 (10.9 Kb) iptables -nvL command not found (so no firewalls) route -n [root@localhost root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo resolv.conf search 168.0.1 nameserver 192.168.0.1 # nameserver 127.0.0.1 # ppp temp entry -------------------------------------------- 192.168.0.1 (it's the windows machine with proxy) 192.168.0.5 (it's the MDK 10 machine) Thanks for the support! Link to comment Share on other sites More sharing options...
hugosantos Posted June 12, 2004 Author Report Share Posted June 12, 2004 by the way... pings...go this way: from the LINUX machine: ping 192.168.0.5 OK good response ping 192.168.0.1 bla bla...destination host unreachable Link to comment Share on other sites More sharing options...
streeter Posted June 13, 2004 Report Share Posted June 13, 2004 Couple of things here - set the nameserver to the same nameserver that windows uses- I don't suppose you have a nameserver running on windows. You can find it in network properties. You don't have a default route - set to the IP address of the windows machine - 192.168.0.1. Neither of these will stop you pinging windows though... So: Unless I am missing something obvious... The only similar factor I can see in these two threads, is that neither of you have iptables running. Now, I have never installed Linux without some sort of firewall, so don't know if this makes a difference. Try installing iptables (urpmi iptables), don't set anything up yet, reboot and see if it all starts working... In the mean time, I will install mdk on a spare partition with this config, and see if it makes any difference - never stop learning, do we? :) Chris Link to comment Share on other sites More sharing options...
hugosantos Posted June 14, 2004 Author Report Share Posted June 14, 2004 Many Thanks! I've installed iptables as your suggestion. Nothing happened after rebooting. Everything stands still. :-( Problem...the network configuration tools from Mandrake should be working and they don't!!!! I suppose you have some experience with this OS but I shoudn't be an expert to make an OS work. This is why I'm saying Mandrake is not a good tool. I'm a user not an expert. Why should I buy an OS that I cannot handle??? Let us ask this question to the Mandrake guys... Thanks for your amazing interest! I suppose you have your place in heaven now ... but still I'm disappointed (again) with MDK. Link to comment Share on other sites More sharing options...
streeter Posted June 14, 2004 Report Share Posted June 14, 2004 Sort of agree with you - for instance the internet connection sharing wizard sets up a nameserver, proxy server and a dhcp server - on a simple home network, these are not really needed - too much complication. But having said that, I installed a fresh copy of mdk 10 yesterday with no firewall or servers and it all worked perfectly, first time. Even with the wizards. Didn't have to enter any more networking information or do anything more than you do when installing windows. If you are still with us, post the output of "iptables -nvL" and "iptables -nvL -t nat" , "route -n" and "ifconfig eth0" and we will see what we can do. Or if you haven't set up too many other things yet, reinstall, but don't set up networking yet - then we know it is clean. Chris Link to comment Share on other sites More sharing options...
Gowator Posted June 14, 2004 Report Share Posted June 14, 2004 hmm Shouldnt need the firewall.. non of my Mandrake boxes have one becuase they are all behind my dedicated firewall. The Wizards tend to screw-up when its a non standard situation (like having 2 NIC's) but in the old days you could just install then the standard way with linux conf or webmin! Now Mandrake is trying to be like Suse and Yast and you cant use linux conf AND the wizards! Anyway the problem is the routing, its set for class B (somehow) but the card is broadcasting to C there uis no default gw set either so either the route for the 192.168.0.1 should be set... I know its perfectly valid to use that IP but I have it becuase it makes the netmasks look weird! you can set a static route to 192.168.0.1 though and add a default anyway... then you need to set up the proxy in the browser and set the nameserver ... Link to comment Share on other sites More sharing options...
streeter Posted June 14, 2004 Report Share Posted June 14, 2004 You are right - you don't NEED the firewall - Like I said, I just tried it on a fresh install. The wizards are indeed hopeless... The routing is OK, apart from the default route - network 192.168.0.0 and netmask 255.255.255.0 is class C. it's OK to use the zero in the third octet. If you mean the odd entry in resolv.conf (search 168.0.1), I am assuming hugosantos has that as the domain name?? eg linux.168.0.1 ?? otherwise just comment out/delete this line. This wouldn't stop a ping by Ip address anyway. Chris Link to comment Share on other sites More sharing options...
Gowator Posted June 14, 2004 Report Share Posted June 14, 2004 The routing is OK, apart from the default route - network 192.168.0.0 and netmask 255.255.255.0 is class C. it's OK to use the zero in the third octet. I know its valid but it always looks weird to me.... (usng a 0 in the 3rd octet) it makes it hard to explain to someone (netgear routers use this too) If people understand already then this makes some sense (although I find it ugly) but its hard to explain about broadcasts and masks if one of the octets is zero... The wizards are indeed hopeless... Yep unless you happen to want to do what the wizard wants ... not the other way round! I dont even like them when they work becuase they tend to do things in a strange way! It might work but if you dont understand it you cant alter it! sounds like winBlows to me! the resolv.conf entry looks lik an error (a missing 192. in front seems likely) but it wont work unless his Windows machine has its own nameserver .... if not it should be set to the same nameserver the windows machine is using then the windows proxy server should pass this on. Link to comment Share on other sites More sharing options...
hugosantos Posted June 14, 2004 Author Report Share Posted June 14, 2004 Thanks! New fresh MDK10 install (no server options). There's always an orange icon informing that the newtwork is down. So here it is the data: root@localhost root]# iptables -nvL bash: iptables: command not found [root@localhost root]# iptables -nvL -t nat bash: iptables: command not found [root@localhost root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo [root@localhost root]# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:30:1B:26:A0:3D inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:2 overruns:0 frame:0 TX packets:0 errors:1 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Base address:0xe400 [root@localhost root]# resolv.conf: empty ping 192.168.0.5 OK ping 192.168.0.1 (win machine, Machine name: VHN-1, workgroup: VHN) [root@localhost root]# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. From 192.168.0.5 icmp_seq=1 Destination Host Unreachable From 192.168.0.5 icmp_seq=2 Destination Host Unreachable From 192.168.0.5 icmp_seq=3 Destination Host Unreachable --- 192.168.0.1 ping statistics --- 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4998ms , pipe 3 [root@localhost root]# Thanks! Link to comment Share on other sites More sharing options...
streeter Posted June 15, 2004 Report Share Posted June 15, 2004 (copied and edited from another of my posts) I think perhaps the easiest thing to do though would be start from scratch manually (what have you to lose?): Type drakxservices in a console as root. Click Stop and uncheck "On boot" dhcpd, squid, netplugd and named if they are there and running. This will turn off some unnecessary and possibly broken servers. Then edit /etc/sysconfig/network-scripts/ifcfg-eth0 - the entries should read : DEVICE=eth0 BOOTPROTO=static IPADDR=192.168.0.5 NETMASK=255.255.255.0 NETWORK=192.168.0.0 BROADCAST=192.168.0.255 ONBOOT=yes MII_NOT_SUPPORTED=yes /etc/resolv.conf should have valid nameserver addresses - put the address of your ISPs nameserver (get it from windows?) at the top. eg nameserver 195.20.224.165 (this is a valid nameserver you can use for testing - it belongs to onetel in the UK, so you should use your own ISPs nameserver - check their website) The default gateway goes in /etc/sysconfig/network: HOSTNAME=yourhostname_goes_here #eg linux.mylan.home NETWORKING=yes GATEWAY=192.168.0.1 Then type "ifup eth0" . Then try pinging windows from linux. If it doesn't work, you need to check the cables (how are the machines connected? Through a hub/switch, or directly with a single cable?) and Windows firewalling. Check to make sure it all works across a reboot. Think that coves it all - apologies if I left something out... Let us know how you get on, including the output of "route -n" Chris Link to comment Share on other sites More sharing options...
hugosantos Posted June 16, 2004 Author Report Share Posted June 16, 2004 Hi Thank you for your tips. a) I have a connection through proxy server on a windows pc. Hub connection between pc's. B) new tested cable connected to linux. c) did all things as your suggestion. d) havn't changed resolv.config (empty) because I want to connect using the proxy. e) route -n exactly as the last time. f) ping's...again not working. thank you. Link to comment Share on other sites More sharing options...
streeter Posted June 16, 2004 Report Share Posted June 16, 2004 Could we have some output from the following, so we can check what is working, and what isn't... 1) Output from "ifconfig eth0" 2) Can you ping Linux from the windows machine? Also windows from the windows machine? 3) You should still have a resolv.conf for good measure - you may want to do something that doesn't use the proxy. It will only be used when necessary. 4) route -n exactly as the last time. You still don't have a default route? Put the following line at the end of /etc/rc.d/rc.local: route add default gw 192.168.0.1 eth0 Then reboot and send output of "route -n" 5) Are the hub link lights on, and do they flash when you try to ping? That'll do for now.. :) Chris Link to comment Share on other sites More sharing options...
hugosantos Posted June 17, 2004 Author Report Share Posted June 17, 2004 did all your suggestions: [root@localhost root]# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:30:1B:26:A0:3D inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Base address:0xe400 [root@localhost root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0192.168.0.1 0.0.0.0 UG 0 0 0 eth0 [root@localhost root]# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. From 192.168.0.5 icmp_seq=1 Destination Host Unreachable From 192.168.0.5 icmp_seq=2 Destination Host Unreachable From 192.168.0.5 icmp_seq=3 Destination Host Unreachable ping: lights flash on ping thanks, hugo Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now