voyager529
Dabbler
- Joined
- Jul 27, 2011
- Messages
- 36
Hello everyone!
I set up an entry level NAS for some friends. They live in an apartment where they share the wireless internet with the landlord. Since they are on a separate floor, running an ethernet cable is somewhat impractical for now.
I purchased a D-Link DAP-1522 for them. The logic was that it would enable their two desktops to access the NAS over gigabit ethernet, while the desktops would be able to use the wired connection between each other and not have to worry about the offboard wireless NICs going slow (and we suspect another is causing a BSoD here and there). With everything going out a consolidated wireless interface, and that interface not having to be responsible for NAS traffic, rainbows and unicorns would be plentiful.
If I was correct in that assumption, I wouldn't be here.
The first issue I dealt with is that the bridge doesn't seem to pass DHCP traffic from the router to the clients. That's simple enough to deal with - just static IP them - they're desktops anyway, so they're not going anywhere. That's what I did. I did a firmware upgrade to see if that would help, no change, so I left it as-is.
Traffic was flowing between desktops and the NAS beautifully. a 1.1GB file went from desktop to NAS in fourteen seconds. It was glorious. Until I started attempting to install plugins from the UI.
The UI became unbearably slow - I'm literally talking minutes between screen refreshes, and the left nav panel frequently failing to load at all. That got me looking for solutions. The first thing said was that sometimes there were issues with jails. Well, I grabbed the handy 'warden' command on the CLI, and nuked every jail I had from orbit. No luck. I tried using the 10/100 onboard NIC - even if it's not the fastest, if it gets a working UI, I'll manage for now. Still no change.
Since I was on the console anyway from reconfiguring the NICs, I decided to ping some stuff in order to see what would happen. The NAS was able to ping both desktops without a problem - I flooded them both with the evil "ping -i 0" command, no problem. I could ping the bridge itself, also without incident. Getting to the router, or the greater internet, was mostly-impossible. I mean that in that I managed to get a standard ping to complete exactly four pings to Google DNS out of 197. Other than that, nothing on the other side of the bridge functioned.
"So then get rid of the bridge, genius!" is the thought that I'm certain everyone is thinking. Here's the problem with that: The two desktops get on the internet FLAWLESSLY. Traffic of every shape and size gets from the wired NICs to the internet and back, with no significant packet loss, no DNS failures, and no other forms of messiness aside from the aforementioned DHCP issue. If the issue is the bridge, then I'd expect something besides flawless performance for the desktops. Moreover, if I remove the router from the 'IPv4 Default Gateway' line, ironically I can ping the router just fine as well. The only configuration changes made to the bridge were connecting it to a wireless network and giving it a static IP address, but is otherwise in bone stock configuration (not that there's much to configure in bridge mode anyway).
I'm open to suggestions with regards to how to rectify the issue. A few thoughts I had were:
1.) known good wireless/wired bridges (preferably units with gigabit ethernet ports).
2.) means by which to connect a FreeNAS to a wireless network directly (e.g. known good wi-fi configs).
3.) reasons why Windows machines on a LAN can get out the door just fine, but a FreeNAS mostly-can't.
I'll check the thread regularly to provide any follow up information requested. Hardware/config specs as follows, to the best I can (some will unfortunately be vague):
CPU: Intel(R) Pentium(R) D CPU 2.80GHz
Mobo: HP OEM of some kind (no descriptive markings; HP splash screen and BIOS)
RAM: 2x1GB DDR2
HDDs: 4x500GB Hitachi Deskstar 7200RPM SATA
NIC: Onboard 10/100, TrendNet TEG-PCITXR GigE (either/or, no ganging)
Network Config: Static IPs, all on 192.168.1.0 network, DHCP on other side of bridge on same network.
Bridge: D-Link DAP-1522, bridge mode.
Router: ISP provided D-Link 802.11ac (does DHCP/DNS).
Thanks so much for your time.
Joey
I set up an entry level NAS for some friends. They live in an apartment where they share the wireless internet with the landlord. Since they are on a separate floor, running an ethernet cable is somewhat impractical for now.
I purchased a D-Link DAP-1522 for them. The logic was that it would enable their two desktops to access the NAS over gigabit ethernet, while the desktops would be able to use the wired connection between each other and not have to worry about the offboard wireless NICs going slow (and we suspect another is causing a BSoD here and there). With everything going out a consolidated wireless interface, and that interface not having to be responsible for NAS traffic, rainbows and unicorns would be plentiful.
If I was correct in that assumption, I wouldn't be here.
The first issue I dealt with is that the bridge doesn't seem to pass DHCP traffic from the router to the clients. That's simple enough to deal with - just static IP them - they're desktops anyway, so they're not going anywhere. That's what I did. I did a firmware upgrade to see if that would help, no change, so I left it as-is.
Traffic was flowing between desktops and the NAS beautifully. a 1.1GB file went from desktop to NAS in fourteen seconds. It was glorious. Until I started attempting to install plugins from the UI.
The UI became unbearably slow - I'm literally talking minutes between screen refreshes, and the left nav panel frequently failing to load at all. That got me looking for solutions. The first thing said was that sometimes there were issues with jails. Well, I grabbed the handy 'warden' command on the CLI, and nuked every jail I had from orbit. No luck. I tried using the 10/100 onboard NIC - even if it's not the fastest, if it gets a working UI, I'll manage for now. Still no change.
Since I was on the console anyway from reconfiguring the NICs, I decided to ping some stuff in order to see what would happen. The NAS was able to ping both desktops without a problem - I flooded them both with the evil "ping -i 0" command, no problem. I could ping the bridge itself, also without incident. Getting to the router, or the greater internet, was mostly-impossible. I mean that in that I managed to get a standard ping to complete exactly four pings to Google DNS out of 197. Other than that, nothing on the other side of the bridge functioned.
"So then get rid of the bridge, genius!" is the thought that I'm certain everyone is thinking. Here's the problem with that: The two desktops get on the internet FLAWLESSLY. Traffic of every shape and size gets from the wired NICs to the internet and back, with no significant packet loss, no DNS failures, and no other forms of messiness aside from the aforementioned DHCP issue. If the issue is the bridge, then I'd expect something besides flawless performance for the desktops. Moreover, if I remove the router from the 'IPv4 Default Gateway' line, ironically I can ping the router just fine as well. The only configuration changes made to the bridge were connecting it to a wireless network and giving it a static IP address, but is otherwise in bone stock configuration (not that there's much to configure in bridge mode anyway).
I'm open to suggestions with regards to how to rectify the issue. A few thoughts I had were:
1.) known good wireless/wired bridges (preferably units with gigabit ethernet ports).
2.) means by which to connect a FreeNAS to a wireless network directly (e.g. known good wi-fi configs).
3.) reasons why Windows machines on a LAN can get out the door just fine, but a FreeNAS mostly-can't.
I'll check the thread regularly to provide any follow up information requested. Hardware/config specs as follows, to the best I can (some will unfortunately be vague):
CPU: Intel(R) Pentium(R) D CPU 2.80GHz
Mobo: HP OEM of some kind (no descriptive markings; HP splash screen and BIOS)
RAM: 2x1GB DDR2
HDDs: 4x500GB Hitachi Deskstar 7200RPM SATA
NIC: Onboard 10/100, TrendNet TEG-PCITXR GigE (either/or, no ganging)
Network Config: Static IPs, all on 192.168.1.0 network, DHCP on other side of bridge on same network.
Bridge: D-Link DAP-1522, bridge mode.
Router: ISP provided D-Link 802.11ac (does DHCP/DNS).
Thanks so much for your time.
Joey