I have had Proscan connected through the Vonet bridge on my internal network. I was working on configuring audio and webserver portion and now,,somehow, I have audio but no display of the scanner through freescan. Whether or not related I will ask,, Do I set the scanner to DHCP and the put the vonet bridge as a static address or the opposite? That seems to be the last settings I touched prior to losing the display. Like I said I had it ALL working earlier. But not to the point of using the web server.
***EDIT***
Seems to be on the computer side. Another computer works fine.
1: Plug the vonet into you laptop/computer to set it up per the instructions (basically you plug it into your ethernet port, then log into it's GUI/web page and look at the list of wi-fi networks, enter your password and it then locks onto an IP, Subnet, Default Gateway and DNS. At that point its acting like a wifi card in your computer.
2: Logged into my cable modem, and went into the wireless client section and looked at the list of IP addresses that had been given an IP from the cable modem's built in DHCP server, it was 192.168.0.28. I then went to the DHCP section where you can also assign a static IP, I did that, based on finding it in the client list, I had the IP address DHCP handed out, but I also put in the Mac address of the Vonet. This locked in that IP address as belonging to Vonet.
3: Keeping in mind I'm still using Vonet on my Macbook Pro as my wifi card, Vonet's DHCP server handed me an IP, I noted the range, subnet ect to be sure it was in line with my other network stuff, wanted to be sure it had not thrown me onto a subnet.
4: Unplugged Vonet's cat 5 connection from my computer, put it in the front of the SDS200, plugged in the USB for power (although I'd probably go a separate source as each time I FTP's up to it or the power cycled, so did the SUB V+ so Vonet rebooted and it's not the fastest coming back online and you risk getting the wrong IP etc...
5: Vonet's lights are flashing, my Macbook Pro is back on its' own wireless connection. I can see on my cable modem (logged into it) that Vonet's woken up and been assigned her IP address of 192.168.0.28, packets are pumping, I look in the SDS200 settings at the LAN settings, "Show IPs", I see that everything looks good, matches what's on the cable modem admin page (I think actually it was one digit higher, I recall my cable modem pushing and my reserving 0.28 but my SDS showing 0.29 as the Vonet acts as a bridge (I've since taken it off). I was then able to connect to it via Proscan both data, FTP Write/Read, as well as Audio with loopback for local audio. I did not open any ports on my firewall as I'm not streaming. Keep in mind, at this point I've told SDS to use "AUTO (DHCP)" in the "Set IP Assignment" section so it's grabbed whatever IP Vonet cares to give. I'll change that shortly. While in the LAN settings, make a note of the
IP address she'd previously been assigned via DHCP, the
Subnet Mask, the
Default Gateway. Like I said, your IP address may be off by one or more but it's important that the items in red are correct.
Note: this is where it's best to power the Vonet from a USB power bank while you're setting this all up, every time you change your IP settings on the SDS, it reboots the scanner, and as a result, the front panel USB port.
6: The DHCP server in Vonet was working great, gave SDS an IP, so once I new everything was working great, I changed the way the SDS gets assigned an IP address from "AUTO (DHCP)" in the "Set IP Assignment" section to 'Manual' in the same section. I then had to enter in the IP address she'd previously been assigned, the Subnet Mask, the Default Gateway etc. Once I set it to 'Manual", it rebooted and came back online.
Note: The 192.168.01. ou see there for Gateway (Default Gateway), is the actual IP address of my cable modem, same IP address I log into when i want to log into make changes to it's setup.
Note: I've taken the Vonet off, only because it introduced ticking sounds on top of the already famous buzzing sound as it was so close to the radio. I could put an extension on the Cat 5 but It was just as easy to run a cable from an Apple Airport Extreme I have close by and connect that to my cable modem like I did the Vonet, just acting as as bridge.
The audio difference is incredible.... LAN is awesome... and I will say, as much as the Vonet method is awesome, if you can run an ethernet cable, you'll be amazed how much quicker it is... the Vonet still took a while to grab and assign IP's etc and seemed finicky a bit, reliable but a bit finicky... Cat 5 blows it out of the water.
I may have missed a couple things but I probably over did this explanation anyways, you sound like you've almost got it working.
Have fun
Jen