I come from DD-WRT, but I'm really liking OpenWRT and will probably make the switch on all my routers. Anyway, I'm actually struggling to get a simple Client WiFi setup going. Here's what I'm going for:
Internet --- Foreign AP ---(wifi)--- My OpenWRT Router ---(ethernet switch)------ My OpenWRT LAN
I am able to connect to the Internet via the Foreign AP with my DD-WRT router (identical model and revision). I guess what's confusing me the most about OpenWRT is the eth0 interface, or perhaps a lack of understanding what DD-WRT does with eth0 in Client WiFi mode. As with a Linux desktop/laptop, I assume eth0 is the WAN port on a router, and in Client WiFi mode, is disabled and the routing table is rewritted so eth0 is replaced with wlan0/ath0. Is this correct?
Anyway, my steps on OpenWRT (with luci) are as follows: connect computer to router via ethernet, go to WiFi page and click Scan on wlan0 interface, choose the foreign AP, assign to default WAN firewall group, verify connection/IP Address with foreign AP. At this point I am able to ping 8.8.8.8, but I cannot reach webpages or connect with, say, Spotify.
I took a look at the answer here: Luci (openwrt) wifi bridge client - how to configure? which isn't exactly what I want (this one is for a bridged repeater/client), but it looks like I am doing everything correctly for just the client functionality. I shouldn't have to bridge any interfaces, right?
So all one should have to do is:
Go to interfaces and click Scan on one of the WiFi radios (2.4 or 5GHz)
Select the host WiFi network
And it just works. Why is that not written down anywhere on the Internet? Now it is, I suppose...
I am not able to get this to work with my 5GHz radio (which works for Client mode on DD-WRT), so it may be a kernel (or some other) issue with this particular build of OpenWRT.
Related
The first router (Telekom something) which is connected to the cable from outside is the one which the smart tv is connected to. The second router (Asus something) is connected through the first one and hosts a separate wifi network from the first. My pc is connected to this router through a LAN cable. I'm trying to use a screen sharing program called Deskreen which hosts a website from the computer and can be reached by typing in the ip address of the computer into a browser. This only works on the same network that the pc connected to.
I tried searching online but I couldn't find anything about a similar situation. My main question would be if I can somehow reach the other router from the smart tv since the two routers are connected.
Yes, use more specific networks that are part of the block on the first router (if you have at least a /29 block), and enable proxy arp (should be on by default).
I have a router (belkin) with many devices connected.
I ran a application on one my devices and the application assigned a port number for remote connection.
Now for me access this device i tried doing something like:
wanipaddress:port
But unable to connect. I am not sure if the router can be used to accomplish the above.
Any suggestions on how to achieve the above?
P.S my router assigned unique LAN IP to all the devices.
I achieved the following using Port Forwarding mechanism. A port forward is a way of making a computer on your home or business network accessible to computers on the internet, even though they are behind a router.
I found the following tutorial to be useful:
I am developing a home automation application using IoT components. Most of these SOC's implement a web page for configuration and control, and I would like to be able to access these pages using the hostname vs. IP address.
Problem is some devices are accessible vis hostname and others are not. A port scan of my LAN shows some devices have host names and some don't. The ones with host names are accessible using the name, the others are not. All are WiFi connected using DHCP. The router is a generic WiFi router, with DHCP.
Since this is working on some devices I'm assuming that the infrastructure that makes this work is Ok, and the failure is on the part of the host when it registers itself on the network. So the question is, how does a host make it's name known to the network? Is it part of the WiFi connection protocol, DHCP, or what?
The objective is to fix the failing devices to properly register themselves on the network. I have source code for everything, so hopefully this is doable.
I'm trying to get Age of Empires II (AoE2) to work on my LAN. AoE2 is notorious for it's connectivity problems on modern systems, probably because it used a now deprecated network framework called DirectPlay (in DX9) and the code probably wasn't robust back in the day either.
When I host a LAN game on a computer (win7) for AoE2, Wireshark shows my computer sending a couple packets via SSDP protocol to the multicast address 239.255.255.250. This actually goes to my router (for forwarding I assume) and my router returns a packet using ICMP protocol that says "Destination unreachable (Port unreachable)". Because nothing is forwarded to the other computers on the network, they can't see the game that the host has created.
I think I need to get the application/windows7 to send the packet as something like a broadcast, or I need to get the router to broadcast packets going to that multicast address. Does anyone have thoughts or suggestions on how to do this?
My router/gateway is running DD-WRT firmware v24-sp2.
My first guess is you're using wifi, by default most systems disable multicast on wifi because it can have a detrimental effect on the time slicing that wifi uses. however for just a couple machines it shouldn't be an issue.
here's how to disable multicasting but it should point you in the right direction for enabling it: ddwrt multicast
Secondly make sure they are all in the same VLAN a VLAN is defined as a "broadcast domain" meaning machines on separate VLANs will NEVER get broadcast or multicast from other VLANs without some trickery.
Lastly make sure you've enabled multicasting between LAN ports I believe the option is "multicast forward"
Edit: Just a few things to add to the list in case others have this issue. Broadcasting doesn't exist in ipv6, also a machine running ipv6 MAY NOT see broadcasts from a machine on ipv4 and a machine on ipv4 WILL NOT see multicasts to an ipv6 multi-cast address.
Have you tried LogMeIn Hamachi?
Is not a LAN client itself but it creates a fake Online-LAN and gives you a working IP that will allow you to play with who have it.
we have little network devices which are shipped with IP address 0.0.0.1 to ensure that they never collide with any other device in their new environment (thus none of the 10.x.x.x, 172.16.x.x or 192.168.x.x ranges) until configuration. DHCP is no solution since there might be no DHCP server in the field.
The devices would listen to UDP broadcasts and answer with broadcasts until they are given their new IP address this way.
This worked fine with Windows XP - but sucks with Windows 7: the config program does not receive the answer packets from the devices which still have 0.0.0.1. Wireshark sees the packets, then they are dumped by the system.
Question: Is there any reason (RFC?) that actually prohibits using this address in a local environment? Or is it just MS that was overcautious? Where can I read why they treat this address "invalid"? Which ranges are really "invalid" now, too?
Any idea of a workaround on the PC side (Win 7)?
I know that it is not recommended to use 0.xxx addresses for work places, but for this very reason - having a not-used address - it works perfectly.
Edit: there is a device out there called "Netburner" which might have faced the similar issue, according to their forum. See: http://forum.embeddedethernet.com/viewtopic.php?f=5&t=612&p=2198 Does - by coincidence - anybody know some background information?
It sounds as if your configuration application is listening for broadcast packets on all network interfaces and expecting to receive packets from foreign subnets.
That should not work - the OS should only pass-on broadcast packets from the subnets each network interface is on, not from all subnets on the same physical (e.g. Ethernet) segment. I am reasonably certain that doing otherwise is broken behaviour WRT the IP protocol.
The are two ways to deal with this:
Make sure that your network interface has an IP address in the target subnet. You can have more than one IP addresses for each network card, so that should not interfere with normal network operations.
Configure or modify you application to use raw sockets, like Wireshark. Keep in mind, however, that this overrides all normal checks and balances and should be avoided, since it can cause behaviour that is almost impossible to diagnose - which is why it is frowned upon by meny network administrators.
Can you you add new routing table entries to Windows machines easily? Windows has to know which interface to use when routing a broadcast packet to the 0.0.0.x network.
The Unix machines I'm familiar with have a routing table that maps network/netmask entries to either gateways or interfaces (if the network is a local network). The local network (192.168.0.0/16 for my home network) gets sent to interface eth0. Everything else 0.0.0.0/0 gets sent to a specific gateway machine 192.168.0.1.
If my machine sent a UDP broadcast message to network 0.0.0.0/24 (in other words, UDP broadcast sent to 0.0.0.255, then my machine would forward the packet to the gateway machine (which it can look up via arp). The switches in the middle wouldn't propagate the packet to other network devices, because the MAC address is set.
If my machine had another routing entry for 0.0.0.0/24 to the local interface, then my machine would send the packet on the wire using an ethernet broadcast group, and the switches would forward the packet to all connections. (Yay! Just like hubs in the 90s! :)
So I figure you need to add a routing entry for 0.0.0.0/24 to your client machines, so that they can properly address the broadcast packet.