Posted: Sun Jun 22, 2014 10:34 Post subject: DUPs with Client Bridge (Routed)
Hi
Just to know this is normal?: when I arp-scan -I wlan0 --localnet (from modem side) I get a (DUP: 2) from the Client Bridge (Routed) NS2 device Wireless MAC.
Code:
192.168.1.9 00:13:d3:66:70:95 MICRO-STAR INTERNATIONAL CO., LTD.
192.168.1.12 00:1d:73:de:8a:7a Buffalo Inc.
192.168.1.50 00:15:6d:f0:9b:bb Ubiquiti Networks Inc.
192.168.1.51 00:15:6d:da:a2:96 Ubiquiti Networks Inc.
192.168.1.51 00:15:6d:da:a2:96 Ubiquiti Networks Inc. (DUP: 2)
192.168.1.101 00:80:77:34:1b:d7 BROTHER INDUSTRIES, LTD.
When I arp-scan -I eth0 --localnet (from Client Bridge (Routed) side) I also get this DUP and all the ip addresses in the network show the same MAC which is the device LAN MAC.
Code:
192.168.1.9 00:15:6d:db:a2:96 Ubiquiti Networks Inc.
192.168.1.12 00:15:6d:db:a2:96 Ubiquiti Networks Inc.
192.168.1.50 00:15:6d:db:a2:96 Ubiquiti Networks Inc.
192.168.1.51 00:15:6d:db:a2:96 Ubiquiti Networks Inc.
192.168.1.51 00:15:6d:db:a2:96 Ubiquiti Networks Inc. (DUP: 2)
192.168.1.101 00:15:6d:db:a2:96 Ubiquiti Networks Inc.
BUMP, i have installed LAMP onto a dedicated machine
everything is as it should be, BUT all of a sudden i can not ssh into my server, i can view web server and everything else, the ports are forwarded correctly, ive gone over everything with a fine tooth comb and this is where i have ended up, my results are exactly the same using arp-scan gives me a DUP for the ip of the client bridge (routed), i have turned off my 5ghz radio but im assuming when it creates the virtual AP a bug arises where the router DUP's itself, any insight would be awesome, i am going to try using just a straight client bridge and wire it and see if i can duplicate ip's that way, BTW i have sshd listening on an extra port as well and it still wont let me ssh, tcpdump port 22 shows that my server is receiving the packets and it is responding but when the ddwrt router gets it the routing gets messed, need to fix this ASAP as having a headless LAMP and not being able to ssh is no good.
I'm afraid you'll get the same. The issue is not with WAP. It is with Client Bridge. dd-wrt atheros won't work in this conf. You'd need to buy another router and forget you spent money for the licence. I ended setting it as a simple Client. For you, simple Client + VAP will work, but you'll have to route (or forward ports). _________________ ): FoReVeR nEwB
