[opensuse] Getting VMware to see thru SuSE Firewall
After the 'High' of getting the Firmware for Speedtouch 536 set-up and connected to ADSL . . . the next 'prob' :- VMware virtual ethernet vmnet was using NAT, but have re-configured vmware to Bridged network, as suggested by vmware config-wizard, BUT, with the switch from Dial-Up, to ADSL thru Ethernet Card, does not allow vmware to see the Internet :( WHAT, please, must I look for to Open in SuSE Firewall ? thanks ___ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Quoting riccardo35@gmail.com <riccardo35@gmail.com>:
After the 'High' of getting the Firmware for Speedtouch 536 set-up and connected to ADSL . . .
the next 'prob' :-
VMware virtual ethernet vmnet was using NAT, but have re-configured vmware to Bridged network, as suggested by vmware config-wizard,
BUT, with the switch from Dial-Up, to ADSL thru Ethernet Card, does not allow vmware to see the Internet :(
WHAT, please, must I look for to Open in SuSE Firewall ?
Change if necessary these settings in /etc/sysconfig/SuSEfirewall2: FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="0/0" Then restart the firewall, "rcSuSEfirewall2 restart". You will probably need to restart the firewall the first time you start up VMware after a boot. If the interface isn't up when the firewall is started it isn't included. Once this works, you can be more restrictive if you wish, read the comment before FW_MASQ_NETS. HTH, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon 29 Jan 2007 21:11, Jeffrey Taylor wrote:
WHAT, please, must I look for to Open in SuSE Firewall ?
Change if necessary these settings in /etc/sysconfig/SuSEfirewall2:
FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="0/0"
Then restart the firewall, "rcSuSEfirewall2 restart". You will probably need to restart the firewall the first time you start up VMware after a boot. If the interface isn't up when the firewall is started it isn't included. Once this works, you can be more restrictive if you wish, read the comment before FW_MASQ_NETS.
thank you . . . have done this Am not quite 'there' yet - have received a warning "No Interface is Active" . . . and Mozilla in VMware cannot get thru to any web-pages, yet What, please, is the next step? Thank you -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 29 January 2007, riccardo35@gmail.com wrote:
After the 'High' of getting the Firmware for Speedtouch 536 set-up and connected to ADSL . . .
the next 'prob' :-
VMware virtual ethernet vmnet was using NAT, but have re-configured vmware to Bridged network, as suggested by vmware config-wizard,
BUT, with the switch from Dial-Up, to ADSL thru Ethernet Card, does not allow vmware to see the Internet :(
WHAT, please, must I look for to Open in SuSE Firewall ?
thanks ___
Which wizard suggested that switch? IMHO: its a BAD IDEA(tm) 1)Bridged requires that your nic be aliased (run in promiscuous mode) and it requires that it obtain an additional IP via dhcp. While this is usually possible on a real nic, its quite likely that dial-up or ADSL will nor support more than one IP per nic. Neither will many (if not most) wireless nics. This is usually a show stopper. 2)Bridged exposes your VM to the net which in turn means you have to start worrying about running a firewall in the VM and all the other issues you encounter when putting a machine on the net. This is the beauty of VmWare nat. First, it just works. Second it provides a layer of protection to the VMs, allowing you to run vulnerable OSs there (read Windows) without the need to run resource hogging virus scanners. So, short answer: Even if point 1 didn't kill you, point 2 makes it a bad idea. This is most likely NOT a firewall issue. Bridged runs beside your firewall, not behind it. -- _____________________________________ John Andersen
On Mon 29 Jan 2007 21:17, John Andersen wrote:
Which wizard suggested that switch?
IMHO: its a BAD IDEA(tm)
1)Bridged requires that your nic be aliased (run in promiscuous mode) and it requires that it obtain an additional IP via dhcp. While this is usually possible on a real nic, its quite likely that dial-up or ADSL will nor support more than one IP per nic. Neither will many (if not most) wireless nics. This is usually a show stopper.
2)Bridged exposes your VM to the net which in turn means you have to start worrying about running a firewall in the VM and all the other issues you encounter when putting a machine on the net.
This is the beauty of VmWare nat. First, it just works. Second it provides a layer of protection to the VMs, allowing you to run vulnerable OSs there (read Windows) without the need to run resource hogging virus scanners.
So, short answer: Even if point 1 didn't kill you, point 2 makes it a bad idea.
This is most likely NOT a firewall issue. Bridged runs beside your firewall, not behind it.
- that was suggested, when running : /usr/bin/vmware-config.pl Thank you . . . have re-done it NAT only. kind regards ______ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 29 January 2007, riccardo35@gmail.com wrote:
- that was suggested, when running :
/usr/bin/vmware-config.pl
Thank you . . . have re-done it NAT only.
It always gives that option, but I've never read it as a recommendation visa vie Nat. -- _____________________________________ John Andersen
participants (3)
-
Jeffrey Taylor -
John Andersen -
riccardo35＠gmail.com