2
« on: May 05, 2008, 05:01:28 PM »
Hi Mark,
Once again thank you. On a PC, normally you can setup your server to listen to one or to all IPs on an interface. That way you could have two HTTP server running on the same PC but will respond differently depending on the IP address used.
Normally the IPs are in different subnets but the default gateway of a PC is unique to both. In my case, I want to encapsulate IP traffic. In my setup:
Internet Router: IP = 192.168.1.1/24
52233 Device : IP 1 = 192.168.1.10/24
IP 2 = 10.1.240.1/24
Gateway = 192.168.1.1
VoIP Device: IP = 10.1.240.2
Gateway = 10.1.240.1
On the second IP all I need to support is ARP and raw IP. The device just looks at Ethernet packets to the device MAC and an IP outside the subnet (MAC and IP broadcasts are discarded) encapsulates it in UDP and sends it to another device that does the opposite. The packets it will receive do not even have the 10.1.240.1 IP as the VoIP device thinks it is a gateway that will know how to forward a packet outside its subnet.
The main reason for the device is that my brother´s ISP restricts all kind of VoIP and VPN traffic. This device is a simple way to tunnel part of his traffic trough my ADSL connection though a UDP port. I have a working version with a ATMega128 and a RTL8109 and wrote most of the UDP/IP/ARP code from scratch but throughput is not that good. I though it was a nice project to jump to 32 bits and get to know the Coldfire processor. I also want to do some dynamic DNS update and add some more features so a stable TCP stack will be a great aid.
Thanks for your work and support
Carlos