| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 67350 | 2006-03-25 03:29:00 | Suse Linux 10.0 networking | AndrewMercer (9663) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 440557 | 2006-03-27 05:09:00 | Linux is good at networking . :cool: It just works . That "route add" command couldn't work . . . as it told you (in its own way) it wanted a device to use . ;) ifconfig is a very useful command for debugging . . . that output shows that your eth0 had not received or sent any packets since it was last started . Try an ifconfig, a few pings and then another ifconfig . I think that "route" output is OK . Apart from the local stuff on lo ("loopback") , it shows that all 10 . 1 . 1 . * goes to eth0; anything else should go to the gateway on 10 . 1 . 1 . 1, also using eth0 . Why use DHCP? It changes things . . . and I hate that . I prefer to tell computers what to do . Use /etc/hosts My network size goes up and down, and the machines I use most haven't even been added to the tables in my DNS server and backup DNS server which I set up when I was more enthusiastic . (The main one runs on my 486DX66 powered server; the backup on a 486DX33 :D ) . It's easy enough to keep an /etc/hosts file on each machine updated . (Even on Windows boxes) . Make sure the router isn't trying to do DHCP . |
Graham L (2) | ||
| 440558 | 2006-03-27 12:21:00 | Does this new firewall have an inbuilt firewall, does it require allowing certain network ranges for them to be able to access the router? The route output looks strange to me, though I have not used OpenSuSe. link-local and loopback are the only things questionable (they don't appear in my route, only the two items I'm suggesting setting up do), to me however the netmask/subnet/genmask used for 10.1.1.0 is strange to me too. How about we start from the beginning drop the eth0 and bring it back up, then configure the default gw and other routes The network card: /sbin/ifconfig eth0 down /sbin/ifconfig eth0 10.1.1.6 up (I would run /sbin/ifconfig eth0 on it now and check what the netmask is set to? if it's 255.0.0.0 then that would be correct in my thinking, test here if it works now, ignore the rest except for maybe the network restart command at the bottom) The gateway and routes: (we'll delete those routes we'll be setting). /sbin/route del -net 10.1.1.0 netmask 255.255.255.0 eth0 /sbin/route del gw 10.1.1.1 netmask 0.0.0.0 eth0 Now to re-add /sbin/route add gw 10.1.1.1 netmask 0.0.0.0 eth0 /sbin/route add -net 10.1.1.0 netmask 255.0.0.0 eth0 (notice the netmask change, must reflect the same as the IP set for the network card). Now to remember to restart the network: /sbin/service network restart That's all I can think of, the best bet is if you could go inside the router and post it's Network settings, as the netmask is something that's vital in this and it could be the only problem. Cheers, KK |
Kame (312) | ||
| 440559 | 2006-03-27 22:04:00 | Maybe I'll have to turn my SuSE box on :waughh: | dolby digital (5073) | ||
| 440560 | 2006-03-28 03:39:00 | That mask is OK: it will select any 10.1.1.x . That allows 254 hosts ... which is enough for most home networks. 255.0.0.0 allows 65000 times that, but it will do no harm to have a more restrictive mask. | Graham L (2) | ||
| 440561 | 2006-03-29 11:01:00 | Thanx all. I've tried everthing suggested to date in terms of configuration. However, searching the various Linux forums the problem I'm having is a common complaint of those using Suse with a CNET PRO200 network card (with Davicom chipset). Oddly enough other distributions work fine though. Will try with an alternative card (with a different chipset) and see how it goes. Odds are that all will be fine. |
AndrewMercer (9663) | ||
| 440562 | 2006-04-02 00:55:00 | Yup - I changed the network card for one with a RealTek chipset (cheapie Gigabit card from Dick Smith). Things seem to be working fine now. Thanks for all the help and advice. Cheers |
AndrewMercer (9663) | ||
| 1 2 | |||||