Currently I set the IP range of 192.168.2.10 to 192.168.2.90
I was able to set lan port 2 to 18.104.22.168 but when I try to set lan port 1 to any address 192.198.2.x where x has been tried as 2, 3, 4, 5, 91 etc I always get the same error : "other Network Interface Device in the same segment"
I can set it to 22.214.171.124 but that does not help me does it.
1. Fixed the problem that [Storage / Disks] shows a blank page in French, Deutsch, and Italian UI. 2. Fixed the security hole on http://n2100/setfan/hwm.html page. 3. Fixed the problem that LAN 1 and LAN 2 could be set in the same IP segment. 4. Fixed the problem that .DS_Store files were inaccessible and caused backup software failed to complete in Mac computers.
I suppose it comes down to personal opinion on how a machine should behave. As this machine is not billed as having a routing capability and how many SOHO users run multi segmented networks.
Before I attempt this, I want to be sure I understand correctly.
N2100:~#N2100:~# sqlite /app/cfg/conf.db "update conf set v='192.168.1.6' where k = 'nic2_ip'" N2100:~# sqlite /app/cfg/conf.db "select v from conf where k = 'nic2_ip'" 192.168.1.6 N2100:~#
doing this is supposed to change the nic setting so that they can be on the same network segment (so lan 1 is .5 , and lan 2 is .6?
In the case that this is done, does the n2100 just function like a switch once it's changed?... allowing traffic to pass through to the rest of the netgwork on the other side?
I ask because I am not having luck with what the IP sharing mode feature. Even after setting all devices as follows, I am still unable to get any connectivity between the segments:
ip: 192.168.2.* Subnet: 255.255.0.0 router: 192.168.2.1 <----- this being the address of the lan 2 nic.
I've also set lan 2 on the n2100 as:
ip: 192.168.2.1 subnet: 255.255.0.0
I've set the subnet mask this way, in hopes that it would enable connectivity to the 192.168.1.* segment ,of the network.
Lan 1 is set: ip: 192.168.1.9 subnet: 255.255.255.0 gateway: 192.168.1.1
This feature (like much about the n2100) is barely documented. Perhaps we could start a stickied thread that specifically addresses the capabilities of the nics and how to set them up for use in either configuration?
Has ANYone been able to use the ip sharing mode succesfully?
I'm not clear on what setup your trying to achieve.
The thecus is like a pc with two network ports. You can configure it to route but dont expect it to work like a switch.
The dual network ports idealy would offer load balancing and failover for a single ip address which is the intended purpose of the ip sharing.
Unfortunately ipsharing has "issues"
I personally run all of my computers on one subnet 192.168.1.xxx I have no valid reason to run multiple subnets. I have a router for routing.
Prior to 2.1.03 you could set both network ports to the same subnet. For name based file shares this worked well as a failover mechanism.
Digging through the html and php code i noticed that Thecus are working on including a PPPOE client and a routing option.
This seems to parallel the n5200 functionality.
As part of this philosophy the've stopped allowing people to set both ports on the one subnet.
Given that the routing functionality isn't yet enabled applying the restriction is pointless.
Here's the bit that makes it really stupid. If you've got a dhcp server set both ports to use dhcp and they'll both end up on the same subnet.
Here's the other thing. The cpu in the n2100 is just powerful enough for it's current tasks. Ask it to perform as a router (with suitable firewall) and you're asking for performance problems.
If you want both ports to be in the same subnet then here's the process... Decide what network structure you want. If you need a switch then use a switch. Most good DSL and cable routers today have built in switches although usually just 10/100.
Gigabit switches do improve performance.
If you need a router then get a router. The thecus just doesn't have the power.
Decide what ip address you want for each port. Set port 2 to something different in a different subnet. Enter the 255.255.255.0 subnet mask.
Set port one to the final ipaddress that you want for it.
Apply and reboot etc.
Log in with ssh and use vi to edit /app/cfg/cfg_nic1 (this is the file for port 2)
You only need to change the ipaddress.
If you reboot now your job is finished because the thecus will now be running with each ports having the correct ip address.
If you look into the web gui you will notice that it's telling you the wrong ip address. That's because the web gui gets the value from the database and not from the config file.
This update statement will update the value in the database to whatever you choose to insert.
sqlite /app/cfg/conf.db "update conf set v='192.168.1.x' where k = 'nic2_ip'"
Theoretically you could put what you want in there or leave it with what it's got indefinately. As far as the OS is concerned it's happily using the values in /app/cfg/cfg_nic0 and /app/cfg/cfg_nic1 It couldn't care less what the gui says...
If you want to play with expanded subnets then there are online subnet mask calculators out there (or there used to be) which you should use.
If you need advice on achieving a specific configuration then you'll need to supply more info on your intended network topology.
I feel that the product planner who included this restriction should be sat in the same corner as the one who put the mac files in the smb veto list and told to be quiet.
Perhaps though when the pppoe is finished it will all make a little more sense.
I had just assumed (not wise) that having two nics and a "routing" / "ip sharing" capability, it would be able to do some sort of pass-through function.... So that I could insert it into a segment of my network, and still have connectivity between both sides. The reason I am messing with this is that I bought a gigabit switch, and need to have it between my main computer and the n2100. However, space constraints force me to locate them on different floors. On one side, I have my dsl modem connected to a router. This is the central point for most of the network. I have attached the gigabit switch to the router, and then the line for the computer and the line going to the second floor. On the second floor, I already have two other computers (servers) and a wireless router/switch. They are all just 100base-t. My plan was to insert the n2100 before the wireless, so that it would be attached straight through to the gigabit switch, and then use the other nic to provide 100base-t connectivity to the equipment already there.
Essentially, I DO want everything on the same network segment, and I want the n2100 to just pass data through to the rest of the network. I started messing with the subnets, etc. when it seemed that it wasn't going to work.