[ubuntu-za] gateway setup problem

Sat Apr 4 12:27:25 BST 2009

Corrie Strydom wrote:
> 
> 
> On Sat, Apr 4, 2009 at 10:39 AM, Corrie Strydom <corrie206 at gmail.com 
> <mailto:corrie206 at gmail.com>> wrote:
> 
>     Morning,
> 
>     $ arp -a
>     ? (192.168.101.103) at 08:00:37:87:88:bb [ether] on eth0
>     ? (192.168.101.99) at 00:00:aa:66:65:e7 [ether] on eth0
>     ? (192.168.101.101) at 08:00:37:25:4d:4f [ether] on eth0
>     ? (192.168.101.3) at 00:10:4b:b7:97:b3 [ether] on eth0
>     ? (192.168.101.208) at 00:1c:c0:af:02:b9 [ether] on eth0
>     test-12472.local (192.168.101.200) at 00:02:6f:36:2d:55 [ether] on eth0
>     test-12423.local (192.168.101.111) at 00:00:aa:ab:cb:27 [ether] on eth0
>     ? (192.168.101.128) at 00:0d:b9:07:20:54 [ether] on eth0
>     ? (192.168.101.188) at 08:00:37:38:84:cd [ether] on eth0
>     ? (192.168.101.30) at 00:15:17:5f:5d:d0 [ether] on eth0
>     NPID07E5E.local (192.168.101.126) at 00:30:6e:d0:7e:5e [ether] on eth0
>     test-12473.local (192.168.101.121) at 00:00:aa:ab:c8:c0 [ether] on eth0
>     ? (192.168.101.188) at 08:00:37:38:84:cd [ether] on eth0
>     ? (192.168.101.30) at 00:15:17:5f:5d:d0 [ether] on eth0
>     ? (192.168.101.130) at 00:07:0e:68:30:1a [ether] on eth0
>     ? (192.168.101.21) at 00:02:6f:36:2d:55 [ether] on eth0
>     NPID07E5E.local (192.168.101.126) at 00:30:6e:d0:7e:5e [ether] on eth0
>     test-12473.local (192.168.101.121) at 00:00:aa:ab:c8:c0 [ether] on eth0
> 
>     and :
>     $ ping 192.168.101.255 -b
>     WARNING: pinging broadcast address
>     PING 192.168.101.255 (192.168.101.255) 56(84) bytes of data.
>     64 bytes from 192.168.101.103 <http://192.168.101.103>: icmp_seq=1
>     ttl=64 time=0.261 ms
>     64 bytes from 192.168.101.121 <http://192.168.101.121>: icmp_seq=1
>     ttl=64 time=0.316 ms (DUP!)
>     64 bytes from 192.168.101.111 <http://192.168.101.111>: icmp_seq=1
>     ttl=64 time=0.331 ms (DUP!)
>     64 bytes from 192.168.101.99 <http://192.168.101.99>: icmp_seq=1
>     ttl=255 time=0.343 ms (DUP!)
>     64 bytes from 192.168.101.188 <http://192.168.101.188>: icmp_seq=1
>     ttl=64 time=0.355 ms (DUP!)
>     64 bytes from 192.168.101.101 <http://192.168.101.101>: icmp_seq=1
>     ttl=64 time=0.366 ms (DUP!)
>     64 bytes from 192.168.101.130 <http://192.168.101.130>: icmp_seq=1
>     ttl=255 time=0.742 ms (DUP!)
>     64 bytes from 192.168.101.136 <http://192.168.101.136>: icmp_seq=1
>     ttl=64 time=1.61 ms (DUP!)
>     64 bytes from 192.168.101.125 <http://192.168.101.125>: icmp_seq=1
>     ttl=255 time=2.56 ms (DUP!)
>     64 bytes from 192.168.101.24 <http://192.168.101.24>: icmp_seq=1
>     ttl=255 time=3.63 ms (DUP!)
>     64 bytes from 192.168.101.135 <http://192.168.101.135>: icmp_seq=1
>     ttl=64 time=5.79 ms (DUP!)
>     64 bytes from 192.168.101.126 <http://192.168.101.126>: icmp_seq=1
>     ttl=64 time=7.00 ms (DUP!)
>     64 bytes from 192.168.101.200 <http://192.168.101.200>: icmp_seq=1
>     ttl=64 time=9.54 ms (DUP!)
>     64 bytes from 192.168.101.103 <http://192.168.101.103>: icmp_seq=2
>     ttl=64 time=0.275 ms
>     64 bytes from 192.168.101.121 <http://192.168.101.121>: icmp_seq=2
>     ttl=64 time=0.294 ms (DUP!)
>     64 bytes from 192.168.101.111 <http://192.168.101.111>: icmp_seq=2
>     ttl=64 time=0.307 ms (DUP!)
>     64 bytes from 192.168.101.99 <http://192.168.101.99>: icmp_seq=2
>     ttl=255 time=0.318 ms (DUP!)
>     64 bytes from 192.168.101.188 <http://192.168.101.188>: icmp_seq=2
>     ttl=64 time=0.381 ms (DUP!)
>     64 bytes from 192.168.101.101 <http://192.168.101.101>: icmp_seq=2
>     ttl=64 time=0.392 ms (DUP!)
>     64 bytes from 192.168.101.130 <http://192.168.101.130>: icmp_seq=2
>     ttl=255 time=0.777 ms (DUP!)
>     64 bytes from 192.168.101.136 <http://192.168.101.136>: icmp_seq=2
>     ttl=64 time=1.32 ms (DUP!)
>     64 bytes from 192.168.101.125 <http://192.168.101.125>: icmp_seq=2
>     ttl=255 time=2.56 ms (DUP!)
>     64 bytes from 192.168.101.24 <http://192.168.101.24>: icmp_seq=2
>     ttl=255 time=3.64 ms (DUP!)
>     64 bytes from 192.168.101.135 <http://192.168.101.135>: icmp_seq=2
>     ttl=64 time=5.51 ms (DUP!)
>     64 bytes from 192.168.101.126 <http://192.168.101.126>: icmp_seq=2
>     ttl=64 time=6.80 ms (DUP!)
>     64 bytes from 192.168.101.200 <http://192.168.101.200>: icmp_seq=2
>     ttl=64 time=9.62 ms (DUP!)
>     ^C
>     --- 192.168.101.255 ping statistics ---
>     2 packets transmitted, 2 received, +24 duplicates, 0% packet loss,
>     time 1007ms
>     rtt min/avg/max/mdev = 0.261/2.503/9.622/2.952 ms
> 
>     (which then carry's on and on, and I dont see 192.168.101.128?)
> 
>     Corrie
> 
> 
> 
>     On 4/3/09, Lee Sharp <leesharp at hal-pc.org
>     <mailto:leesharp at hal-pc.org>> wrote:
>      > Corrie Strydom wrote:
>      >> Hi everyone, what a issue to be stuck with on a Friday afternoon.
>      >> Something changed (and I realy dont know what since last night) and
>      >> now I cant access a gateway/firewall on our work LAN.
>      >>
>      >> I'm trying to access the gateway (192.168.101.128) from my laptop
>      >> (192.168.101.204)
>      >> I cant ping the IP from my laptop, but I can ping and connect from
>      >> another computer on the network, same kind of settings as below.
>      >
>      > Please give the results of "arp -a" and "ping 192.168.101.255 -b"
>      >
>      >                       Lee
>      >
>      > --
>      > ubuntu-za mailing list
>      > ubuntu-za at lists.ubuntu.com <mailto:ubuntu-za at lists.ubuntu.com>
>      > https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>      >
> 
> 
> 
> Hi, ok got it working, sometimes I wonder why I decided to work in IT 
> and not go into hairdressing?
> 
> I unplugged the firewall/gateway for 20sec and plugged it back in again, 
> and viola, works, I quess I'll try and explain that Monday to the ISP 
> support guys, and see if they can give me a answer.
> 
> Thanks alot and enjoy the rest of the weekend.
> 
> Corrie
> 
Maybe it was because u thought of rebooting the router, A hairdresser 
would have tied knots in the cord.

Wayne A