Quote:
Originally Posted by lucmove
What's also great, I reconfigured the virtual machine from Bridged to NAT, and now your iptables script works.
|
Excellent!
Quote:
|
That 192.168.1.122 IP number is gone, now the virtual machine is reported as 192.168.1.135 as expected.
|
Right. I prefer it this way, myself. Less details to worry about, for one.
I'm sure there is some way to support VMWare Player in bridged mode too. It's just a bit difficult for me, since I don't use VMware Player myself.
Quote:
|
Now I just need to find myself another machine I can use to test the armor on this one.
|
Nothing beats a real-life hands-on test. Especially since you know your firewall rules are very clean, and have no exceptions (weak spots, I call 'em), a couple of simple tests should really bring you peace of mind. I really like the way they're not dependent on specific interface numbers, but use e.g.
wlan+ as a wildcard for any wlan interface (wlan0, wlan1, wlan2, and so on). Sometimes the order (suffix numbers) change when you switch drivers or upgrade udev or the kernel.
Quote:
Well. Should I mark this thread as SOLVED? 
|
I guess that'd be nice, but I'd personally wait until having tested the set-up first.
I'm glad I could help,
Nominal Animal
