Hi, I'm sending this again as no-one has responded to me, I hope someone can help. :-( ------- Well, I finally got myself another network card today for the new machine. However, I can't seem to get it to see the rest of the network or the gateway. :( This is how the network is currently set up: [3 machines]--------[SuSE box]---[modem]----**Internet** | (hub) I tried to ping several machines on the network (with their ips') but get 100% packet loss, and no lights flash on the hub. Here is the 'route' output for scratchy (the non-working machine): Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface scratchy.kechara * 255.255.255.255 UH 0 0 0 dummy0 192.168.1.1 * 255.255.255.0 U 0 0 1 eth0 loopback * 255.0.0.0 U 0 0 2 lo default itchy.k 0.0.0.0 UG 0 0 0 eth0 Here is the output of Itchy (the gateway machine with the modem - if this is relevant) Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface itchy.kechara.o * 255.255.255.255 UH 0 0 0 dummy0 demon-du.demon. * 255.255.255.255 UH 0 0 0 ppp0 192.168.1.0 * 255.255.255.0 U 0 0 527 eth0 loopback * 255.0.0.0 U 0 0 388 lo default demon-du.demon. 0.0.0.0 UG 0 0 23 ppp0 All the other machines on the network (which are Windows98) work fine connecting to Itchy. If anyone has any suggestions, please do let me know with some gentle (newbie-certified(tm)) instructions. :-) If you need any more information, please do let me know what you need and I will try to find out for you. Best Wishes, Lee Smallbone
Don't you have to setup your linux host as a firewall? I've not gotten round to trying much of this myself yet, but my understanding was that you needed: 1) squid, to give your WinPC's a www proxy. 2) /etc/mail/relay-domains to allow sendmail to relay mail 3) ipchains in your kernel (?) 3) socks (sp?) for passing other protocols like ftp, telnet, etc. (I've a suspicion you might not need socks if you have ipchains .. not sure on that though. Someone more experienced will be able to tell you). There must be a HOWTO on setting all this up I guess. I've not needed to do it myself yet (though I will in the near future) so I'm just repeating things I've noticed in other posts from time to time. Hope that gives you a nudge in the right direction. John
Lee Smallbone wrote:
Hi,
I'm sending this again as no-one has responded to me, I hope someone can help. :-(
Hi Lee, This looks a bit weird to me, but since you got no answer at all: In the first place, I thought a firewall issue on your gateway, bu then I noticed:
Here is the 'route' output for scratchy (the non-working machine):
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface scratchy.kechara * 255.255.255.255 UH 0 0 0 dummy0 192.168.1.1 * 255.255.255.0 U 0 0 1 eth0 ^^^^^^^^^^^^^^^^^^^ this looks like a host adress, not a network adress... loopback * 255.0.0.0 U 0 0 2 lo default itchy.k 0.0.0.0 UG 0 0 0 eth0
I suspect this to be 192.168.1.0, the network address like itŽs with the other machine. This must be hidden somewhere in yastŽs network setup for the card, presumeably the network address. HIH Juergen -- =========================================== __ _ juergen.braukmann@ruhr-west.de | -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
Hi, this is what i would do: Assuming that kernel 2.2.x is compiled with IP masquerading support: On the suse: # ifconfig eth0 192.168.1.1 up # /sbin/depmod -a # /sbin/modprobe ip_masq_ftp # /sbin/modprobe ip_masq_raudio # /sbin/modprobe ip_masq_irc # /sbin/modprobe ip_masq_quake # echo "1" > /proc/sys/net/ipv4/ip_forward # ipchains -P forward DENY # ipchains -A forward -s 192.168.1.0/24 -j MASQ On the other 3 machines: change the IP addresses to show 192.168.1.2, 192.168.1.3, 192.168.1.4 with the netmask of 255.255.255.0 try pinging www.netscape.com... I did this yesterday -- took less then 15 min. I did not use a modem though: i alaised two ip's on the eth0 and used the same cable for outside and private networks--> amazingly still works an entry in your routing table could be messing everything up: 192.168.1.1 * 255.255.255.0 ... <--- this route is wrong here is my routing table as an example: alexm@hr-60:~ > netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 208.24.140.0 0.0.0.0 255.255.255.128 U 0 0 0 eth0 192.168.1.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.0 208.24.140.1 0.0.0.0 UG 0 0 0 eth0 This is an example of working setup with ethernet. first line -- a route to my ISP's subnet (real IP) second line -- a route to my private network third line -- self explanatory fourth line -- my default gateway. make sure yours looks similar (except the interface names). (Un)fortunately, i have not dealt much with modems for years now... Also, when posting network related questions use "-n" option with your commands that way we can help you better (machine names do not tell much about your network ;-) ) sorry for a long post. good luck, -alexm On Fri, 30 Jul 1999, Lee Smallbone wrote:
Well, I finally got myself another network card today for the new machine. However, I can't seem to get it to see the rest of the network or the gateway. :(
This is how the network is currently set up:
[3 machines]--------[SuSE box]---[modem]----**Internet** | (hub)
I tried to ping several machines on the network (with their ips') but get 100% packet loss, and no lights flash on the hub.
Here is the 'route' output for scratchy (the non-working machine):
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface scratchy.kechara * 255.255.255.255 UH 0 0 0 dummy0 192.168.1.1 * 255.255.255.0 U 0 0 1
eth0
loopback * 255.0.0.0 U 0 0 2 lo default itchy.k 0.0.0.0 UG 0 0 0 eth0
Here is the output of Itchy (the gateway machine with the modem - if this is relevant)
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface itchy.kechara.o * 255.255.255.255 UH 0 0 0 dummy0 demon-du.demon. * 255.255.255.255 UH 0 0 0 ppp0 192.168.1.0 * 255.255.255.0 U 0 0 527 eth0 loopback * 255.0.0.0 U 0 0 388 lo default demon-du.demon. 0.0.0.0 UG 0 0 23 ppp0
All the other machines on the network (which are Windows98) work fine connecting to Itchy. If anyone has any suggestions, please do let me know with some gentle (newbie-certified(tm)) instructions. :-)
If you need any more information, please do let me know what you need and I will try to find out for you.
Best Wishes,
Lee Smallbone
-- To unsubscribe, e-mail: suse-linux-e-unsubscribe@suse.com For additional commands, e-mail: suse-linux-e-help@suse.com
participants (4)
-
alexm@hr-60.aus.tx.i3s.net
-
firewall@ecad.org
-
jm_uk@bigfoot.com
-
juergen.braukmann@ruhr-west.de