Strange IP address

[FredTheDog]

Hi,

Before Xmas my AC66U router threw a fit, don't know why just tried to access the internet one morning and nothing worked. Eventually managed to get access to the router and it couldn't access my ISP. What I did notice though was when I connected to it over wireless my machine had an IP addr of 192.168.1.216 with subnet 255.255.255.0 and I could connect to the router pages and other machines on the network. However when I connected over wire my IP address gets set to 169.254.162.75 with subnet 255.255.0.0 and I cannot connect to anything.

I have:
Hard reset the router
Cleared NVRAM
Loaded various firmware versions

All to no avail, I have even borrowed a machine that has never connected to this router and get the same strange IP address range assigned when connecting over wire and the correct range when connecting over wireless Both use DHCP for wired and wireless.

I don't know if this is the cause of my not being able to connect to the ISP with this router but I figured it was my starting point.

Any ideas as to why this is happening and what I can do to fix?

Am now on Merlin build 3.0.0.4.374.38_1

Thanks

FTD

EDIT: I have set the IP address it should assign to the MAC address using the "Manually assign IP around the DHCP" in the DHCP settings.

I then see several lines in the System log:

Jan 1 00:52:37 dnsmasq-dhcp[648]: DHCPDISCOVER(br0) <my MAC Addr>
Jan 1 00:52:29 dnsmasq-dhcp[648]: DHCPOFFER(br0) 192.168.1.222 <my MAC Addr>

But there is no
Jan 1 00:52:47 dnsmasq-dhcp[648]: DHCPACK(br0)
line for the wired connection as there is for the wireless

 

[jack901]

its the goofy windows default ip address. not a router problem.on the computer go in to network settings and change adapter tcp protocol and set a static ip.
again a windows problem not router.

 

[FredTheDog]

Thanks Jack, but I am using a mac but none the less have set a static IP address still no luck connecting to the router when wired, I can only connect to it using wireless.

 

[sinshiva]

are you trying to set the same ip address for the mac addresses of both the computer's wired and wireless interfaces?

 

[FredTheDog]

no, I am trying to set different IP addresses for each to avoid a conflict

On the Mac I can choose to connect wired, wireless or both using separate profiles. At the moment I switch between wired and wireless, so one is always switched off. If both are enabled then I cannot access the router either, only when wireless is selected do I connect

 

[sinshiva]

hm. have you tried doing a ipconfig /release before connecting over wired?

oh wait, mac as in apple lol

[edit/]

Camelot,

I got it to work. Once I found out how to determine what en# my pci card was in, I typed in the following commands in the terminal and it changed the IP address:

sudo ipconfig set en2 BOOTP
sudo ipconfig set en2 DHCP

Thanks for your help.

Mark

try this ?

(probably use sudo ifconfig -a to find the appropriate interface
or sudo ipconfig -a )

[edit/] though, i can't see why another computer would have the same problem over wired, hm.

 

[sinshiva]

what is your entire network layout ? anything else running a dhcp server?

 

[FredTheDog]

nothing else running DHCP.

everything has been working fine for 6+ months

I have my router connected to a home plug, on the other end is a switch that connects to other devices. This is what first caused the problem, tried to connect to the NAS through the switch, which has a static IP address and I couldn't connect.

Then tried the internet to look for advice and couldn't get out to the ISP, got onto the Asus and ISP wasn't connecting, DDNS wasn't working etc. So switched back to my old router and all is good again.

It seems as though the Asus won't talk to anything on the ethernet ports, even though it registers things as connecting to them in the status window and showing 10 Half duplex....which thinking about it is weird because the mac is 1000 Full Duplex???

 

[sinshiva]

alright, disclaimer first; never used ethernet over either coax or powerline;

It seems as though the Asus won't talk to anything on the ethernet ports, even though it registers things as connecting to them in the status window and showing 10 Half duplex....which thinking about it is weird because the mac is 1000 Full Duplex???

this has me suspecting a wiring problem, seen it happen before with a crap cable.

if you leave the asus detached from the network, powered on and connect the computer directly to it with a prefab ethernet cable, does it get an ip?

 

[FredTheDog]

When I ping it wired I get:
Ping: SendTo: Host is down

When I ping it wireless I get success

Just switched to wired and set up the same IP address as gets assigned when wireless. Refreshed the Asus connected web page and got the usual IP Address has changes, reconnect using wireless blah blah message. Then refreshed again and it hangs, Firefox tells me host is not responding. Chage to wireless and viola, connected, refresh the page and the settings widow is displayed just as it was before I switched to wired

 

[sinshiva]

ok, connect back over the wireless and if you go to the webui, LOGOUT. disconnect and use the cable, either let it use dhcp or pick a different IP. preferably, see if dhcp will work

 

[FredTheDog]

alright, disclaimer first; never used ethernet over either coax or powerline;

this has me suspecting a wiring problem, seen it happen before with a crap cable.

if you leave the asus detached from the network, powered on and connect the computer directly to it with a prefab ethernet cable, does it get an ip?

Have connecting directly with several cables, dodgy cable was my first thought

 

[FredTheDog]

ok, connect back over the wireless and if you go to the webui, LOGOUT. disconnect and use the cable, either let it use dhcp or pick a different IP. preferably, see if dhcp will work

Connected via wireless, went to webui and logged out, message in firefox telling me so...all good so far

Switch to wired connection allow DHCP to assign an IP address and it takes so long I think the mac is assigning an address itself.

The only reason I say this is I screwed up the settings on the mac messing about connecting to different routers in different ways to test and then post here and I buggered up the wireless info. The mac waits about 10 seconds then tells me its auto assigned an IP address as it couldn't contact the DHCP server....my fault! So I fix it and all is now well with wireless. However I now see with the wired, it waits the same time to get an IP addr, then one magically appears that is very similar to the one set when wireless wasn't working, but I don't get the auto assigned message. Never would have noticed if I hadn't buggered the wireless!

 

[FredTheDog]

So as you say its a wired connection problem.

But:
- My mac connects over cable to the other router without issue. So its not the mac?
- I have tried several cables, including one I know for sure works having tested it connecting to the working router. And no good.

So it has to be the Asus??

 

[sinshiva]

if i'm reading this correctly, the computer doesn't get an actual network ip over wired such as 192.168.x.x? might want to try completely rebooting the machine

 

[FredTheDog]

if i'm reading this correctly, the computer doesn't get an actual network ip over wired such as 192.168.x.x? might want to try completely rebooting the machine

Correct, IP Address using DHCP over wired is nothing like what it should be. All others get me the correct 192.168.XXX.XXX as I would expect.

What it is similar to is the IP address I got when I screwed up the wireless and was told the mac had auto assigned an IP itself.

Have tried rebooting both mac and Asus.....still not working. I have now connected two other machines to the Asus using wired in different ports on the router and get random IP addresses being assigned.

EDIT: One machine is Windows 7 and the other is another mac

 

[sinshiva]

damn, that's weird. maybe you got a ghost in the machine that's misbehaving lol.

ok, i'm going to be lazy and assume you are running asuswrt-merlin since this thread is in the this forum.

first, try setting a new range at LAN > DHCP Server, such as 192.168.x.100 - x.200

if that doesn't work go to Tools > Run CMD and execute: cat /etc/dnsmasq.conf

and paste that along with the output of ifconfig -a

if we can't figure this out with the above results, i'd try reflashing the firmware and if that still does not yet work, then i'm going to have to say return the router

 

[mtrains]

This is looking more and more like the LAN switch part of your router is fried

 

[sinshiva]

This is looking more and more like the LAN switch part of your router is fried

indeed. :\

[edit/] and possibly caused by his homeplug setup, so purchasing another may get him the same results. it could be the homeplug device is faulty...

 

[FredTheDog]

ok, i'm going to be lazy and assume you are running asuswrt-merlin since this thread is in the this forum.

Yes I am, just flashed to the latest version to try to fix

first, try setting a new range at LAN > DHCP Server, such as 192.168.x.100 - x.200

Still no joy, random IP address assigned wired, correct assigned wireless

if that doesn't work go to Tools > Run CMD and execute: cat /etc/dnsmasq.conf

pid-file=/var/run/dnsmasq.pid
user=nobody
resolv-file=/tmp/resolv.conf
no-poll
min-port=4096
bind-dynamic
interface=br0
no-negcache
cache-size=1500
dhcp-range=lan,192.168.1.200,192.168.1.210,255.255.255.0,86400s
dhcp-lease-max=253
dhcp-authoritative
dhcp-option=lan,3,192.168.1.1
read-ethers
addn-hosts=/etc/hosts.dnsmasq
address=/#/10.0.0.1

the output of ifconfig -a

When connected wireless:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
ether c8:2a:14:14:17:9b
media: autoselect (none)
status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether e0:f8:47:3e:1c:e6
inet6 fe80::e2f8:47ff:fe3e:1ce6%en1 prefixlen 64 scopeid 0x5
inet 192.168.1.205 netmask 0xffffff00 broadcast 192.168.1.255
media: autoselect
status: active
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
ether 02:f8:47:3e:1c:e6
media: autoselect
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 70:cd:60:ff:fe:ec:6a:24
media: autoselect <full-duplex>
status: inactive
vboxnet0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:00


When connected wired:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
ether c8:2a:14:14:17:9b
inet6 fe80::ca2a:14ff:fe14:179b%en0 prefixlen 64 scopeid 0x4
inet 169.254.141.209 netmask 0xffff0000 broadcast 169.254.255.255
media: autoselect (1000baseT <full-duplex,flow-control>)
status: active
en1: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether e0:f8:47:3e:1c:e6
media: autoselect (<unknown type>)
status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
ether 02:f8:47:3e:1c:e6
media: autoselect
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 70:cd:60:ff:fe:ec:6a:24
media: autoselect <full-duplex>
status: inactive
vboxnet0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:00

if we can't figure this out with the above results, i'd try reflashing the firmware

Already tried that with Factory Reset and NVRAM clear

and if that still does not yet work, then i'm going to have to say return the router