Long involved problem that invites a few questions here as I am way over my learning curve.

Having moved back on my boat, had to establish some sort of internet service. After convincing marina owner it was to his advantage to offer wifi we got a wireless dsl connection set up. After purchasing a Netgear usb wireless nic and finding no native linux drivers managed to get it install and connecting via ndiswrapper.

Signal strength is so-so and connecting sometimes a problem (another issue) so decided to attempt to set up my wgn2000v2 router as a repeater (yet another issue).

In order to accomplish the above it is neccessary to connect to the wgn2000v2 (router2) to access its setup. Just plug in a cat5 and connect, right?..... wrong! With router 2 up and running and no connections other than cat5 to this computer (Fedora17 xfce) Network connections manager shows em1 "disconnected" with no option to connect.

Now for the questions.. Assume because router2 is still set up as a dhcp enabled router using 192.168.1.1 as its address, and router1 (wifi) is using same ip address I cannot connect to both at same time. Correct?

Normally this would not be a problem but as I stated above my connection to router1 (wifi) is flakey. Once connected its solid as a rock, but connecting is hit and miss. Haven't really been able to reproduce the situation and am loath to disconnect from my online reference material. Other users have connected to router1 with no problems so assume is config problem on my machine. Any suggestions appreciated.

TIA
David

System Info
Fedora 17
wireless interface-- netgear wnda3100v2 (ndiswrapper)
ethernet card--Intel 82562EZ 10/100 Ethernet Controller

Additional ijnfo below:

*-network
description: Ethernet interface
product: 82562EZ 10/100 Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: em1
version: 02
serial: 00:11:11:46:8a:22
size: 100Mbit/s
capacity: 100Mbit/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.24-k2-NAPI duplex=full latency=64 link=yes maxlatency=56 mingnt=8 multicast=yes port=MII speed=100Mbit/s
resources: irq:20 memory:fcfff000-fcffffff ioport:ddc0(size=64)

*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 9c:d3:6d:02:00:a8
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmn43xx32 driverversion=1.58+,08/26/2009, 5.10.79.30 ip=192.168.1.3 link=yes multicast=yes wireless=IEEE 802.11g

ifconfig output
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::211:11ff:fe46:8a22 prefixlen 64 scopeid 0x20<link>
ether 00:11:11:46:8a:22 txqueuelen 1000 (Ethernet)
RX packets 172 bytes 12612 (12.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 192 bytes 16905 (16.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 87 bytes 6934 (6.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 87 bytes 6934 (6.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::9ed3:6dff:fe02:a8 prefixlen 64 scopeid 0x20<link>
ether 9c:d3:6d:02:00:a8 txqueuelen 1000 (Ethernet)
RX packets 4179015 bytes 1391774355 (1.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2712708 bytes 265884977 (253.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions

iwlist scan

wlan0 Scan completed :
Cell 01 - Address: F8:E4:FB:C2:77:0F
ESSID:"powells2"
Protocol:IEEE 802.11g
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality:34/100 Signal level:-74 dBm Noise level:-96 dBm
Encryption key: off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: Unknown: 0008706F77656C6C7332
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 050400010000
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: 2D1AFC181BFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1601000400000000000000000000000000000000000000
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F0101
IE: Unknown: DD090010180201F0040000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00

Correct - you can't have two (sub)nets the same; if you want to be able to get to both. Worse if they are both DHCP servers.
In F17 try clicking on the network icon, then "Network Settings", then under Wireless you should have the option to "Forget Network". Haven't tried it, but hopefully that should allow you to get a new IP lease next time you try. Disable the wifi and plug the cat5 in - see if it works.

Last time I tried this, the repeated channel (speed) was halved as it was always used for traffic back and forth through the repeater. Was a few years ago, and hopefully the technology has improved.

@syg00

Thanks for the reply mate... Thought that was the problem. Just avoiding taking down the wifi because its such a pita to get reconnected. Have to get to the root of that problem but figure it is probably the symptom of needing to use ndis wrapper. Only need to connect to the second router long enough to change its default ip address and disable dhcp then should be able to connect via cable while I got the wireless connected.

Re: 1/2 speed on repeated channels. No improvments that I know of. Good news is bandwith choke point is the dsl line so half speed on the router connection will still exceed (by a lot) the available bandwidth on the gateway.

Tks again
David

Once you get sorted, talk to the marina owner and get a static IP for your router. Will make life *much* easier into the future.

I haven't used ndis wrapper in forever - I tend to make sure I only use supported wifi cards. Even the embedded ones on laptops I order specifically.

Well, guess that means I gotta talk to myself (I'm not the owner) as its up to me to get this mess working for the rest of the users. Think when I set router2 up as a relay/repeater, it will be talking to router1 using a mac address rather than an ip address. Either way I will beat it into submission eventually. Don't think I can talk him into buying a dedicated repeater though it would be nice.

Re: Ndis ... Didn't want to use it myself, but supplies locally are scarce, I was in a hurry and I didn't do my research. Live and learn, it won't happen again. Guess I will give things another hour or so then go ahead and pull the plug on the wireless. Hey I got it working once,
what could go wrong? (hehehe)