Quote:
Originally Posted by phoenix  by any chance is yours an Intel NIC? |
I had too much problems with Intel NICs so this time I decided to go back to very cheap ones (Realtec onboard and D-Link with a Realtec chip). lspci shows
Code:
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:03.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)
I didn't have the problems You had with your xen box. Would drive me crazy. So I already thought about reinstalling the whole machine with vmware. But I don't known, wether this would be a simpler solution. with less problems. Finally problems are gone know and I don't like to invest so much time.
Quote:
Originally Posted by phoenix I still think you could achieve the same set-up via the firewall in in your DomU without the need for the Linksys, it would also mean your firewall would handle all the port forwarding (if needed) and not be limited by that feature on the Linksys which only has a limited number of ports you can forward (plus I don't like two firewalls, but that's just me). |
I want the WLAN NIC beeing treated as traffic coming from the web. So it seems easier to me having the WLAN NIC connected to the NIC on the xen which is directly connected to the firewall. Next step will be eliminating the DSL modem and using the LinkSys like in former times. Because I do need a DSL modem I also have two firewalls - the LinkSys (also being the DSL modem in future) and the DomU firewall. Till some weeks I needed the additional DSL modem because I simply hadn't my provider account information - it was only set up in that box - shame on me. The simple solution for that was using this box and cascading the LinkSys. Shame on me, yes
