Problem with two lan networks and access to ap
-
Hmm, this is interesting but confusing.
It is possible that it's only possible to add static routes on the WAN interface, there is no option to select the interface. However if that were the case then adding that route should have had no effect at all. I assume by your statement "nothing worked" that you were then unable to connect to the webgui at all? Seems like your router may be misbehaving somehow.
Anyway you have yet more options! Another way to allow the access point to have a route back to LAN is to NAT between them. Now usually you wouldn't want that but it could be done with manual NAT configuation.
The other thing you could do, and this is what I've done, is just not worry about it! ;) I have an access point that (mis)behaves in exactly this way. It has no route back to other interfaces, I cannot add a route to it, I cannot configure a gateway on it's LAN, I can enter a fudged subnet mask but that doesn't work. So I set it up and ignore it. I probably haven't needed to check its webgui for a year or so and when I do I just connect by wifi.
Steve
-
Personally, I think he should have all his connections on the LAN ports on that AP and that he should put tape over his WAN port.
-
Good Morning
I did a Hard Reset to AP
And put everything to the initial state as if he were RouterThen again I followed the guide to make it to AP
And it works as AP
Just the access its management interface is only when connecting Directly to him
wired or wirelessI do not know what to say
I tried everything I know
And all you knowJust does not work
I will stay with it how it is now
There is internet access from wireless devicesBut not sharing files between computers on the wired network
To computers on the wireless network
Or reversedIt would make me crazy in the near future
So many thanks to everyone for the helpIf I find why this happens I promise to update
-
Just because you can't access the AP webgui from the wired network that should not mean you can't access other wireless clients. That is some other issue. As long as you have the correct firewall rules in place in pfSense there should be access between the wired and wireless networks.
Steve
-
Unfortunately it also does not work
We have 5 laptops at home
One currently running and is with me
Has two shared foldersThey are accessible only if the computer is connected to the wired network
Of course the same thing
But the reverseNo wireless devices access to the wired network shared directories
-
Ok, a number of things could be happening here:
pfSense is blocking the traffic. That's easy to check because it will appear in the firewall logs.
There's a routing problem. This doesn't appear anywhere so it's harder to spot but we've just spent a good deal of time checking out the routing on your network and it looks good.
Something is blocking the traffic locally. E.g. Windows firewall is blocking access because the traffic is coming from another subnet.Remind me, you are not able to ping between wired and wireless clients either?
Steve
-
Remind me, you are not able to ping between wired and wireless clients either?
Steve
Yes
Specific computers that I am trying to access shared folders
Are running Linux Ubuntu -
Ah, er, yes you're not able to ping or yes you are able to ping? ;)
If you plug a client into one of the other LAN ports on the wbr-3406 can you ping the wired clients (on 192.168.0.X) from there? That should exclude and wifi weirdness from the problem.
Steve
-
Yes there is ping
from wireless computer 192.168.2.8 to wired computer 192.168.0.2
and
from wired computer 192.168.0.2 to wireless computer 192.168.2.8 -
Ok so you can ping but not do file transfer? And this worked ok before?
This is probably because the machines are not on the same subnet so they are not directly discoverable by Windows (or whatever). Have you tried accessing the shared folder directly by its IP?
Steve
-
If you don't know how to access a share by IP, its easy in windows…
hit start > computer
on left side, click network
select your current computer in the list
now in that bar at top of file browser, put in \192.168.1.30 (or whatever the IP of the computer with the share is)
I'm slipping - I should have suggested this way way back but "shares" was never mentioned early on.
-
Just now I tried to access a network folder
Using ip numberIt work
Why not see all computers when entering the network
-
File sharing uses broadcasts that don't cross subnets to advertise themselves.
So, when you have files and printers shared, the easy way to reach them across subnets is by IP since no broadcast is required that way.
Understand?
If I had known you had shares, I would have suggested it earlier. Good thing stephenw10 did.
-
If you have a domain controller/WINS server that can register connected clients then you can span subnets I believe, not my area.
If you have enabled "Register DHCP leases in DNS forwarder" then you can access remote machines by their host name but they still won't be discoverable.
You may be able to get discovery to work across the subnets using the IGMP proxy, I've never tried that.
Steve
-
Can I assume that the problem
Related to the same reason that you can not access the management interface of the API'm still trying to check why this is happening and fix it
But not urgent
As beforeIf I run into something on the way so I check and try
At least I have access to shared folders
As you have shown me -
It's two distinct problems:
You can't access the wifi router because it's not possible to give it a route back to the LAN side subnet.
You can't see the wifi clients from the wired network because because the protocol Windows uses to discover network shares doesn't span subnets.
I would try adding the route again to the access point. I should do nothing or fix it. The fact that it killed everything last time you tried it implies something wasn't right.
Steve
-
You can't see the wifi clients from the wired network because because the protocol Windows uses to discover network shares doesn't span subnets.
in My work
There were about 2000 computers connected
Over 50 different networksI tap the icon "Network" on the computer
I see all the networks
Then click on the network icon
And see all the computers on the networkI guess strains because they are connected to servers
So I guess the server tells computers where they are at,Is there something similar to pfsense
I would try adding the route again to the access point. I should do nothing or fix it. The fact that it killed everything last time you tried it implies something wasn't right.
I prepare a file with all the screenshots of this router
I will attach it to the next post
See what I did there
What should be doneYou can't see the wifi clients from the wired network because because the protocol Windows uses to discover network shares doesn't span subnets.
I use Linux not Windows
How can you upload here a presentation weighs 2.8 MB
Or upload more images in a single message -
Here is a link to download the pdf file
With a screenshot of the router's management interface -
I guess strains because they are connected to servers
So I guess the server tells computers where they are at.Exactly.
Is there something similar to pfsense?
No. (I assume you mean for pfSense)
You are probably using the Windows SMB protocol for file shares in Linux, though there are others, so the same applies. You need a domain controller to register the available shares across all subnets and distribute that information. This isn't my forte though. ;)
Here is a useful thread: http://forum.pfsense.org/index.php?topic=22064.0
I would try adding the route I described earlier into the AP routing table again. I can't see how it could possibly break anything. It may not work but it should cause any harm.
Steve
-
Is the Avahi package can fit
I read in this thread
About a similar problemhttp://forum.pfsense.org/index.php?topic=60967.5
When I read the thread you gave a link for it
It said it is related to DNS
