Thursday, June 14, 2018

WIS-Q5300 subnet problems | subnet not seen

Hi guys,

I'm already pulling my hairs of my head.

Device Name : WIS-Q5300 Software Version : 1.0.0338.20161115_Release BusyBox v1.15.3 

I have 2 same devices witch basically i want to use to make Wifi-bridge between 2 places.

both devices are in bridge mode, but soho router doesn't change a thing.

one is AP mode, the other one station client mode.

One device after configuration can ping subnet 192.168.x.x and 10.2.x.x

the other one in the other hand can ping 192.168 but not the 10.2.

i tried reinstalling firmware, factory reset, adding route, iptables are flushed, importing config from one device to another.

NOTHING helps, what the hell i am missing?

routes on working device

~ # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0* 255.255.255.0 U 0 0 0 vbr1 169.254.0.0* 255.255.0.0U 0 0 0 vbr1 default 192.168.1.10.0.0.0UG 0 0 0 vbr1 

ARPS on working device

~ # arp ? (192.168.1.2) at 0c:68:03:9f:d4:82 [ether] on vbr1 ? (192.168.1.1) at 00:8e:73:be:6d:a8 [ether] on vbr1 ? (192.168.1.210) at ac:22:0b:7e:0a:db [ether] on vbr1 <-me 

iptables on working device

~ # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination 

Non working device routes

~ # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.2.1.0* 255.255.255.0 U 0 0 0 vbr1 <- added / deleting it changes nothing 192.168.0.0* 255.255.252.0 U 0 0 0 vbr1 169.254.0.0* 255.255.0.0U 0 0 0 vbr1 default 192.168.1.10.0.0.0UG 0 0 0 vbr1 

non-working device arps

? (192.168.1.210) at ac:22:0b:7e:0a:db [ether] on vbr1 

^

didin't arped to gateway?!!!

non-working device iptables

~ # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination 


No comments:

Post a Comment