Fwd: Re: [Wylug-help] Networking Trouble
Roger Greenwood
rg at nthong.freeserve.co.uk
Sat Jun 5 17:50:28 BST 2004
Update :-
Fixed it (eventually)
The online update, as well as causing general chaos, had set the firewall on,
which was blocking all access from the network card.
Changed firewall rules, voila!
Kids amazed they can surf from their own machine.
---------- Forwarded Message ----------
Subject: Re: [Wylug-help] Networking Trouble
Date: Wednesday 02 Jun 2004 18:28
From: Roger Greenwood <rg at nthong.freeserve.co.uk>
To: wylug-help at wylug.org.uk
On Wednesday 02 Jun 2004 17:11, Jim Jackson wrote:
> Roger,
>
> On Tue, 1 Jun 2004, Roger Greenwood wrote:
> > am having trouble setting up my local network - any pointers appreciated
> >
> > :-
> >
> > machine 1 - server - 192.168.0.1
> >
> > machine 2 - slave - 192.168.0.2
> >
> > std. ethernet through hub (10Meg). Both machines running SuSE 9.1
> >
> > WAS working at first - set up using yast, broke due to online download
> > (should have left it alone). WAS able to transfer between machines, now
> > can't even ping each other. Slave settings untouched, server settings
> > well screwed. Have now abandoned yast and tried some simple stuff. At one
> > point the server had both eth0 and eth1 set up but only one (eth1) made
> > the lights flash on the hub, so that is the one that I left on.
>
> Are you sure the slave hasn't altered.
> Output from both machines from "/sbin/route -n" would be useful as well.
> I'm assuming 192.168.0.3 doesn't exist on the network, and so the last
> ping output is fine.
Hi Jim,
Don't think slave altered - lost the connection after the online update of
server.
Whilst connected via modem :-
server:/usr2 # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
195.92.66.29 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 195.92.66.29 0.0.0.0 UG 0 0 0 ppp0
SLAVE :-
# /sbin/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
169.254.0.0 0.0.0.0 255.255.0.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 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
> jim
>
> > SuSE 9.1 seems to be very different from previous and lots of online help
> > is not very useful/superceded.
> >
> > Thanks,
> >
> > Roger Greenwood.
> >
> > These are some stuff from the server - any comments appreciated :-
> >
> > rogerg at server:~> /sbin/ifconfig
> > eth1 Link encap:Ethernet HWaddr 00:C0:DF:0A:14:E3
> > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> > inet6 addr: fe80::2c0:dfff:fe0a:14e3/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:489 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:364 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:1 txqueuelen:1000
> > RX bytes:37180 (36.3 Kb) TX bytes:26086 (25.4 Kb)
> > Interrupt:5 Base address:0x1000
> >
> > 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:2936 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:2936 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:489089 (477.6 Kb) TX bytes:489089 (477.6 Kb)
> >
> >
> > server:/usr2 # netstat -r
> > Kernel IP routing table
> > Destination Gateway Genmask Flags MSS Window irtt
> > Iface 192.168.0.0 * 255.255.255.0 U 0 0
> > 0 eth1 loopback * 255.0.0.0 U 0 0
> > 0 lo default server.local 0.0.0.0 UG 0 0
> > 0 eth1
> >
> >
> > rogerg at server:~> ping 192.168.0.2
> > PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
> >
> > --- 192.168.0.2 ping statistics ---
> > 10 packets transmitted, 0 received, 100% packet loss, time 8997ms
> >
> > rogerg at server:~> ping 192.168.0.1
> > PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
> > 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.224 ms
> > 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.186 ms
> > 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.183 ms
> > 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.184 ms
> >
> > --- 192.168.0.1 ping statistics ---
> > 4 packets transmitted, 4 received, 0% packet loss, time 2999ms
> > rtt min/avg/max/mdev = 0.183/0.194/0.224/0.019 ms
> >
> > rogerg at server:~> ping 192.168.0.3
> > PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
> >
> > >From 192.168.0.1: icmp_seq=2 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=2 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=3 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=4 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=6 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=7 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=8 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=10 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=11 Destination Host Unreachable
> > >From 192.168.0.1 icmp_seq=12 Destination Host Unreachable
> >
> > --
> > The trouble with doing something right the first time is that no one
> > appreciates how difficult it was.
> >
> >
> >
> > _______________________________________________
> > Wylug-help mailing list
> > Wylug-help at wylug.org.uk
> > http://list.wylug.org.uk/mailman/listinfo/wylug-help
>
> _______________________________________________
> Wylug-help mailing list
> Wylug-help at wylug.org.uk
> http://list.wylug.org.uk/mailman/listinfo/wylug-help
--
The trouble with doing something right the first time is that no one
appreciates how difficult it was.
_______________________________________________
Wylug-help mailing list
Wylug-help at wylug.org.uk
http://list.wylug.org.uk/mailman/listinfo/wylug-help
-------------------------------------------------------
--
The trouble with doing something right the first time is that no one
appreciates how difficult it was.
More information about the Wylug-help
mailing list