static i.p., no router - how do i feed internet to my NAS

[zdoe]

win7 / 64 laptop. synology 414slim (though i guess it doesn't matter which NAS box).

internet coming in via WiFi. NAS connected to the LAN port with static ip, no router. storage works. yes - i know my setup is not the most common one.

how do i get the internet from the laptop's wifi to the NAS box? i've ran this as storage only for a while, but now i'd like to start getting email notifications and accessing / syncing files on the NAS over the internet from other workstations.

so far i've enabled internet connection sharing in the wifi connection, and tried various gateway settings on the NAS - but don't know where that should be pointing to.

 

[stevech]

win7 / 64 laptop. synology 414slim (though i guess it doesn't matter which NAS box).

internet coming in via WiFi. NAS connected to the LAN port with static ip, no router. storage works. yes - i know my setup is not the most common one.

how do i get the internet from the laptop's wifi to the NAS box? i've ran this as storage only for a while, but now i'd like to start getting email notifications and accessing / syncing files on the NAS over the internet from other workstations.

so far i've enabled internet connection sharing in the wifi connection, and tried various gateway settings on the NAS - but don't know where that should be pointing to.

Huh? Internet coming in via WiFi. Do you have a router that supports WiFi as WAN? Or do you have a WiFi bridge and switch?

Laptop would associate to a WiFi access point (A wifi router has an access point built-in). If you have no router- just a bare AP or bridge, the usual policy is that a client on these devices is not permitted to communicate with any other WiFi device directly.

Do you actually have an internet service provider and I've misunderstood your writing?

 

[zdoe]

Huh? Internet coming in via WiFi. Do you have a router that supports WiFi as WAN? Or do you have a WiFi bridge and switch?

Laptop would associate to a WiFi access point (A wifi router has an access point built-in). If you have no router- just a bare AP or bridge, the usual policy is that a client on these devices is not permitted to communicate with any other WiFi device directly.

Do you actually have an internet service provider and I've misunderstood your writing?

i guess i was a bit cryptic. i do have a router a floor down that has the usual setup. laptop connects to it / the internet via wifi. but there's no router where the laptop/NAS are so the only place i can plug in the NAS is the laptop's ethernet port. which works for storage, but i'd like to pipe the laptop's wifi internet to the NAS as well.

connectify hotspot IS able to feed internet to outside devices from the laptop, i assume there is a way i could feed it to the NAS as well, just don't know how / what would be the right settings.

 

[thiggins]

Easiest thing is to use a wireless bridge to connect the NAS to your router. Example http://www.smallnetbuilder.com/wire...i-entertainment-adapter-with-4-ports-reviewed

 

[zdoe]

Easiest thing is to use a wireless bridge to connect the NAS to your router. Example http://www.smallnetbuilder.com/wire...i-entertainment-adapter-with-4-ports-reviewed

i guess. but i'm a bit loathe to buy new hardware when i have a feeling that if i just knew what to do i could make it happen without any additional gear.

if i am buying gear, i'll get a set of powerline adapters that can take internet to the location of the setup - and then add a router next to the lap/NAS.

or - how about if i get a usb wifi dongle? is it possible to configure the NAS with a static IP / ethernet to the computer, but getting internet via a dongle?

 

[azazel1024]

If the laptop is always on, you can plug the NAS in to the ethernet port of the laptop and then in windows select the wifi adapter and allow bridging of the wifi adapter.

The laptop has to be on for it to work, but that'll do it.

Maybe money is tight, but seriously, just buy a $20-30 router that can do bridging or a similar cost dedicated wireless bridge. No kludging needed, will always be on, etc.

 

[htismaqe]

Maybe money is tight, but seriously, just buy a $20-30 router that can do bridging or a similar cost dedicated wireless bridge. No kludging needed, will always be on, etc.

Totally agree.

Getting a cheap router will be more efficient, more secure, and just all-around better.

 

[zdoe]

If the laptop is always on, you can plug the NAS in to the ethernet port of the laptop and then in windows select the wifi adapter and allow bridging of the wifi adapter.

The laptop has to be on for it to work, but that'll do it.

Maybe money is tight, but seriously, just buy a $20-30 router that can do bridging or a similar cost dedicated wireless bridge. No kludging needed, will always be on, etc.

the laptop IS always on.

ok - i've bridged the wifi adapter and ethernet adapter. still no internet on the NAS. should i let the wifi-router's DHCP assign the IP to the bridge instead of using a manual IP?

what should i set on the gateway field on the NAS' network settings? the bridge's IP. the ethernet connection's IP? the wifi-router's IP? or?

sure money is an issue, but mostly it's about finding an elegant / compact / transportable solution with no redundant gear and extra wall wart.

--------------------------

tried a bridge now - storage over the ethernet works, but NAS is still not getting internet. i'm bridging a VPN connection, not the wifi - as it should be in my setup.

here's IPconfig /all:
Windows IP Configuration

Host Name . . . . . . . . . . . . : oem0
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Network Bridge:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 5E-26-0A-58-44-2E
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.137.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Atheros WiFi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR9280/AR9281/AR9283/AR5009/AR5B91/AR5BH92/AR5B93 Wireless Network Adapter
Physical Address. . . . . . . . . : 00-1F-E1-13-0C-8F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8080:2050:b464:9f54%24(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, November 06, 2014 9:12:16 AM
Lease Expires . . . . . . . . . . : Thursday, November 06, 2014 2:12:17 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 335552481
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-D6-2A-18-F0-4D-A2-A3-5C-F6
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : PdaNet Broadband Adapter
Physical Address. . . . . . . . . : 00-26-37-BD-39-42
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

PPP adapter vpn a p2p shortest ping:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : vpn a p2p shortest ping
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 198.18.128.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Astrill SSL VPN:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Astrill SSL VPN Adapter
Physical Address. . . . . . . . . : 00-FF-F2-AE-31-DC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{DA985BC1-8EDD-4EC2-8918-A439ECC7D531}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:c612:8002::c612:8002(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:34cd:337:a070:3e7b(Preferred)
Link-local IPv6 Address . . . . . : fe80::34cd:337:a070:3e7b%27(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

 

[stevech]

i guess. but i'm a bit loathe to buy new hardware when i have a feeling that if i just knew what to do i could make it happen without any additional gear.

if i am buying gear, i'll get a set of powerline adapters that can take internet to the location of the setup - and then add a router next to the lap/NAS.

or - how about if i get a usb wifi dongle? is it possible to configure the NAS with a static IP / ethernet to the computer, but getting internet via a dongle?

To do it right, and not have future hassles, get a WiFi bridge as recommended. It is a shame though, to put a NAS on a WiFi connection - as it's slow.
Cost $20 and up.
http://www.newegg.com/Product/Produ...MATCH&Description=wifi+bridge&N=-1&isNodeId=1

 

[zdoe]

To do it right, and not have future hassles, get a WiFi bridge as recommended. It is a shame though, to put a NAS on a WiFi connection - as it's slow.
Cost $20 and up.
http://www.newegg.com/Product/Produ...MATCH&Description=wifi+bridge&N=-1&isNodeId=1

well, of course i won't be using the NAS via wifi - i'd rather keep the NAS off the net then. as for future hassles, i assume, if doable at all, what i want to do is a one time only -hassle...

 

[htismaqe]

If you've successfully bridged the wifi and ethernet adapters, the NAS should be able to pickup an IP address and default gateway via DHCP. That's the surest way to know it is working. Check the router logs to see if it is receiving a DHCP request from the NAS MAC address.

 

[azazel1024]

I see different /24 addresses for the ethernet and wifi on the laptop. What address are you using on the NAS? Bridging should allow stuff to talk across the two networks, even using different subnets, HOWEVER if you are attempting to do DHCP on the NAS across different subnets, that is going to likely cause issues.

I'd ensure that everything is on the same 192.168.1.x address range. Ensure that the router is doing DHCP on a range from, say, 192.168.1.2-100. Then either set the NAS to an address of, say, 192.168.1.200 or leave it on dynamic IP and see what happens.

Simplify this thing.

For the gateway IP, try using the router's IP address for the NAS. If that doesn't work, you can try the IP of the ethernet port on the laptop, but you shouldn't need/want to do that (again, if the /24 address ranges are different, it might be that you need to set it as the IP of the ethernet port on the laptop. I haven't played with bridging across subnets very much).

 

[htismaqe]

azazel1024 is 100% correct here.

You're trying to bridge two subnets.

Really, you should ROUTE between subnets. You should bridge between SEGMENTS.

All of your devices need to be on the same Layer 3 network.

 

[zdoe]

If you've successfully bridged the wifi and ethernet adapters, the NAS should be able to pickup an IP address and default gateway via DHCP. That's the surest way to know it is working. Check the router logs to see if it is receiving a DHCP request from the NAS MAC address.

i think the bridge is currently done right. the NAS originally got its (new, static) IP from synology assistant's connection wizard.

now i had the NAS do DHCP, and the IP changed to 192.168.137.129 - still not on 192.168.1.xxx.

however, this produces something promising - synology package center now says "server busy" instead of failed connection.

there might also be an issue with DNS.

as far as i can see, my router's log for DHCP doesn't contain mac-info.

(and i have a feeling that windows moves the IPs of bridged connections away from the 192.168.1.xxx range.)

 

[zdoe]

it's working now, the NAS gets internet - the package center is working. time servers are not.

this may be related to DNS settings. i guess i can use some public ones, but would prefer to use my own running on the laptop (127.0.0.1 i'm in china, standard DNS queries get poisoned replies.)

besides the DNS issue, i'm sure i'll have plenty fun working out port forwarding so that i can actually see the NAS from outside.

for reference, here's the current IPconfig /all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : oem0
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

PPP adapter vpn a p2p shortest ping:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : vpn a p2p shortest ping
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 198.18.128.41(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Network Bridge:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 5E-26-0A-58-44-2E
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.137.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Atheros WiFi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR9280/AR9281/AR9283/AR5009/AR5B91/AR5BH92/AR5B93 Wireless Network Adapter
Physical Address. . . . . . . . . : 00-1F-E1-13-0C-8F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8080:2050:b464:9f54%24(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, November 07, 2014 9:25:04 AM
Lease Expires . . . . . . . . . . : Friday, November 07, 2014 12:25:07 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 335552481
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-D6-2A-18-F0-4D-A2-A3-5C-F6
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : PdaNet Broadband Adapter
Physical Address. . . . . . . . . : 00-26-37-BD-39-42
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:c612:8029::c612:8029(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:3064:1011:fa38:56c3(Preferred)
Link-local IPv6 Address . . . . . : fe80::3064:1011:fa38:56c3%27(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

 

[azazel1024]

You generally still do not want to bridge across different subnets. You CAN do that. You just generally don't want to. You generally want to route between subnets.

I still suggestion you switch the NAS to 192.168.1.x range just like the rest of the network (same with the ethernet port on the laptop).

 

[zdoe]

You generally still do not want to bridge across different subnets. You CAN do that. You just generally don't want to. You generally want to route between subnets.

I still suggest you switch the NAS to 192.168.1.x range just like the rest of the network (same with the ethernet port on the laptop).

i believe you, but when i tried i didn't get the lap to see the NAS, or NAS to see the internet. don't remember which one. only by using whatever DHCP gave me i'm getting it to jive.

also - i'm actually bridging a VPN connection and the ethernet port - which i have to do because the wifi in my case doesn't have internet, just chinanet.

currently the VPN connection is 198.18.128.41 - and it seems to be on that 198.18.128.xxx range between re-connects, with the last xxx changing. i don't know that i could force the VPN connection to be on the wifi router's range. or - could i?

 

[htismaqe]

i believe you, but when i tried i didn't get the lap to see the NAS, or NAS to see the internet. don't remember which one. only by using whatever DHCP gave me i'm getting it to jive.

also - i'm actually bridging a VPN connection and the ethernet port - which i have to do because the wifi in my case doesn't have internet, just chinanet.

currently the VPN connection is 198.18.128.41 - and it seems to be on that 198.18.128.xxx range between re-connects, with the last xxx changing. i don't know that i could force the VPN connection to be on the wifi router's range. or - could i?

Doubtful. I wondered about this yesterday when I saw the VPN tunnel adapter in your ipconfig.

If you're getting internet through the VPN tunnel, the NAS would have to be bridged with the tunnel interface, which is how you have it.

Unfortunately, this is a highly unorthodox setup but it sounds like you've got it working to the extent that it will.

 

[zdoe]

Doubtful. I wondered about this yesterday when I saw the VPN tunnel adapter in your ipconfig.

If you're getting internet through the VPN tunnel, the NAS would have to be bridged with the tunnel interface, which is how you have it.

Unfortunately, this is a highly unorthodox setup but it sounds like you've got it working to the extent that it will.

yups. i don't have it all yet, but to get the incoming stuff working i'll need to first get some more ports open in the VPN's firewall - which might be a bit of a challenge.

it won't ever be very reliable, but i AM already way ahead of where i was 2 days ago.