[Wylug-help] What am I missing (router question)

[Shaun Laughey]

On Mon, 2007-04-30 at 23:41 +0100, Roger Greenwood wrote:
> On Monday 30 April 2007 22:03, Shaun Laughey wrote:
> > On Mon, 2007-04-30 at 21:28 +0100, Roger Greenwood wrote:
> > > On Monday 30 April 2007 21:18, Lee Evans wrote:
> > > > Hi Roger,
> > > >
> > > > What you want to do is give your hub/wireless access point an IP on the
> > > > same subnet as your local machine [192.168.1.x]
> > >
> > > Thanks Lee,
> > > I was going to try this, tried to change the settings on the hub, but it
> > > all went pear shaped and since then couldn't get access to the netgear
> > > hub!!
> > >
> > > The hub is still on 192.168.0.7 i.e. it didn't change the settings as
> > > requested - this I can see from ethereal.
> >
> > Have you tried adding a temporary ethernet address (an "ip-alias") to your
> > machine so it can use both subnets.
> >
> > e.g. ifconfig eth0:1 192.168.0.250
> >
> > It's not a permanent solution but it will let you access both router and
> > access point and configure them accordingly.
> Thanks Shaun - not heard of that one before. Here is the result :-
> 
> sempron:/home/rogerg # ping -I eth0:1 192.168.0.7
> PING 192.168.0.7 (192.168.0.7) from 192.168.0.10 eth0:1: 56(84) bytes of data.
> From 192.168.0.10: icmp_seq=10 Destination Host Unreachable
> From 192.168.0.10 icmp_seq=10 Destination Host Unreachable
> From 192.168.0.10 icmp_seq=11 Destination Host Unreachable
> From 192.168.0.10 icmp_seq=12 Destination Host Unreachable
> 
> I can still see the router :-
> 
> sempron:/home/rogerg # ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.690 ms
> 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.426 ms
> 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.418 ms
> 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.416 ms
> 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.414 ms
> 
> --- 192.168.1.1 ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 4000ms
> rtt min/avg/max/mdev = 0.414/0.472/0.690/0.112 ms
> sempron:/home/rogerg # ping -I eth0:1 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) from 192.168.1.20 eth0:1: 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.430 ms
> 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.414 ms
> 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.417 ms
> 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.417 ms
> 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.418 ms
> 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.415 ms
> 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.419 ms

Okay Roger you have me there...

( You shouldn't need to add the -I to ping as the routing is added
automatically. at least in my experience )

root at shaunl-desktop:~# ifconfig eth0:1 192.168.1.1
root at shaunl-desktop:~# route -n
Kernel IP routeing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0
eth0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0
eth0
0.0.0.0         192.168.0.254   0.0.0.0         UG    0      0        0
eth0

I am assuming you are doing all this with wires into the router switch
and not trying to get wireless to work and that the access point has a
verifiable IP address on the lan normally.

For example on my network the Accesss Point I use is transparent for
nearly all network traffic except ARP and SNMP. It definitely doesn't
respond to such things as ICMP.

Things to look at are:

1) Cross over cable issues - sometimes ports aren't automatically going
to work between switches/hubs. Rare these days.

2) Connecting to the wrong port on the router - for example on mine the
Access Point connects to any LAN port on the router not the WAN port.

3) Routes in the router - anything that's not the on the local LAN it
will route via the WAN port and it will then let the ISP refuse to
handle it. Some routers let you have more than one network passing
through it - but they aren't the cheaper ones. 

Solution? Connect directly to the Access point from the computer with a
network cable and change the IP address to the same subnet as the router
and your problems will be solved*

--
Shaun Laughey.


* Alternatively of course your problems could be just beginning...