Re: [PLUG] VMPlayer host network only
On 08/04/2015 03:17 PM, Michael Rasmussen wrote: > I'm trying to run an network isolated VM image for diagnostics. But I > still need to communicate with the host system to scp log files and such. > > Host: Windows 7 > CLient: SuSE Linux. > Just saw this thread and am glad you noodled it out. I've had quite a few of those "D'OH!" moments myself lately. But here's a thought: The guest and Host do not need to transfer files to each other via networking. A better solution is to set up a host to guest drive mapping. That way, you can still transfer files, with as much security as you need, with a simple cp. I'm not a fan of VMware as I use qemu, but the features set is the same. You simply tell VMplayer on the HOST to share a folder. This folder then is a mount point on the Linux GUEST. A script or crontab can then periodically drop files to the host - no network needed. https://pubs.vmware.com/workstation-9/index.jsp#com.vmware.ws.using.doc/GUID-AACE0935-4B43-43BA-A935-FC71ABA17803.html Have fun, -Ed ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] THURSDAY: August PLUG Meeting: A brief history of software documentation
Portland Linux/Unix Group General Meeting Announcement Who: Jennifer Rondeau What: Back to the Future: A brief history of software documentation Where: PSU, 1930 SW 4th Ave. Room FAB 86-01 (Lower Level) When: Thursday, August 6th, 2015 at 7pm Why: The pursuit of technology freedom Stream: http://pdxlinux.org/live The world of software development rightly demands an emphasis on the new and the innovative -- on doing things differently from how they’ve been done. The assumption is that newer is (almost) always better. But if we look only to the present and the future, we risk reinventing the wheel, failing to understand that we are all built on tradition, failing to learn everything that we could from the past. This talk shows how documentarians can find inspiration in the past, build on it, and move forward. It tells some of these stories, and shows what they meant in historical context: * The pre-history and dawn of software documentation -- how technical writers were hired, how they worked, what they made, the challenges they faced, and how their solutions continue to inform the work we do today * The much longer history of teaching engineers to write documentation * Efforts to make technical writing into an independent profession Calagator Page: http://calagator.org/events/1250468578 Many will head to the Lucky Lab at 1945 NW Quimby St. after the meeting. Rideshares Available PLUG Page with information about all PLUG events: http://pdxlinux.org/ Follow PLUG on Twitter: http://twitter.com/pdxlinux PLUG is open to everyone and does not tolerate abusive behavior on its mailing lists or at its meetings. See you there! Michael Dexter PLUG Volunteer ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] How to research (<>"ask") Linux questions?
The problem with search engines is that if you aren’t knowledgable on the subject, you don’t know which questions to ask, or how to phrase them. Chicken and Egg. Case in point, one possibility to accomplish what you want: dd if=/dev/cdrom of=/path/to/dvdN.iso dd will read bits off the cdrom (dvd) and write them to the file you specifiy. I used duckduckgo, but my search query was: how to create iso from dvd linux > On Aug 4, 2015, at 7:22 AM, Richard Owlett wrote: > > Google searches can have a lot in common with turning 1000 > monkeys loose on 2000 typewriters expecting _The Decline and Fall > of the Roman Empire_. > > Asking questions on fora can get bogged down in minutia (e.g. > "when up to in alligators it's difficult to remember swamp > draining is goal"). > > Case in point: > My starting point is complete DVD sets of Debian 6, 7, and 8. > Optimizing for clock time: > A. copy each version to individual directory on "flash drive" > and/or "hard drive" > such that resulting structure will be /debianN/dvd1.iso ... > /debianN/dvdM.iso > B. create a local repository of each version in its own partition > > For my unique case, I have adequate if imperfect solution(s). > > I suspect that "How to research Linux questions" will have much > in common with various articles on "asking good questions on > Usenet". If fact this might be an expansion the most common #1 > point under "how to ask ..." --> "Do your homework." > > > ___ > PLUG mailing list > PLUG@lists.pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug -- Louis Kowolowskilou...@cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.com/ Making life more interesting for people since 1977 ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] VMPlayer host network only - fully resolved and D'OH
The VPN software we use is sanely configured and will not allow other network connections to function while in use. Once I detached from the VPN everything worked fine. Michael Rasmussen wrote: > Indeed it is the Windows host based packet filtering. > Which is managed by a 3rd Party app. think of the bing names and it will > be semi-obvious. > > Sometimes working for a bank is a bitch. > My boss didn't think we had host based firewalling. > Note: We both work in the corporate security department. > > > Michael Rasmussen wrote: >> >> chris (fool) mccraw wrote: >>> On Tue, Aug 4, 2015 at 4:05 PM, Ken Stephens wrote: >>> Michael Rasmussen wrote: > Both hosts can ping their own interface, yet neither can ping the other's > interface. >>> >>> No surprise there - you can ping any address you configure as local by >>> default :) >> >> And the sanity of "did I set up the interface?" was verified. >> >>> Check your firewall settings on both the virtual and real machines. You are probably blocking port 22 on one of them. >> >> No FW settings on the VM. This one is a clone of a production system >> that >> we ssh to as part of regular work. >> >>> >>> ...but blocking ICMP by default as he mentioned ping doesn't work? >>> That >>> seems odd and unexpected to me. >>> >>> Michael, can you tell us what the setup is on each machine (eg VM = >>> 10.1.1.1/255.0.0.0 w/route to that network via the interface, host= >>> 10.1.1.2/255.0.0.0 route - note that I am more interested in what the >>> Host >>> machine's network settings are on the private network that gets setup >>> for >>> the VM than what its "external" IP/routes are)? Also, what host passes >>> out >>> the DHCP address to the VM - that should be in the logs somewhere? (My >>> centos 7 VM puts it in /var/log/messages as 'server identifier x.y.z.q' >>> in >>> the middle of a bunch of NetworkManager output.) >> >> The DHCP server seems to be the VMWare player. >> >> Windows (host) side: >> >> Ethernet adapter VMware Network Adapter VMnet1: >> >>Connection-specific DNS Suffix . : >>Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter >> for >> VMnet1 >>Physical Address. . . . . . . . . : 00-50-56-C0-00-01 >>DHCP Enabled. . . . . . . . . . . : No >>Autoconfiguration Enabled . . . . : Yes >>IPv4 Address. . . . . . . . . . . : 192.168.118.1(Preferred) >>Subnet Mask . . . . . . . . . . . : 255.255.255.0 >>Default Gateway . . . . . . . . . : >>NetBIOS over Tcpip. . . . . . . . : Enabled >> >> Linux (VM instance) side: (this is typed as I can't cut and paste from >> there. >> >> >> ip addr show eth1 >> 2: eth1: mtu 1500 qdisc pfifo_fast >> state >> P qlen 1000 >>link/ehter 00:0c:29:e3:63:d7 brd ff:ff:ff:ff:ff:ff >>inet 192.168.118.128/24 brd 192.168.118.255 scope global eth1 >>inet6 >> >> ip route >> 192.168.118.0/24 dev eth1 proto kernel scope link src 192.168.118.128 >> >> That all looks sane to me. >> >> Curiously tcpdump shows: >> 11:32:56.130921 arp who-has 192.168.118.1 tell 192.168.118.128 >> 11:32:56.131059 arp reply 192.168.118.1 is-at 00:50:56:c0:00:01 >> >> So there's some communication on the line. The mac addr matches the >> Window's mac. >> >> Now researching Windows FW and what happens to VM connections when I've >> a >> VPN connection going. >> >> >>> In my setup, that IP is given out by my host machine - which is not >>> running >>> DHCPd, so VirtualBox is using its builtin DHCP server, and just passes >>> on >>> many the same settings (eg nameservers) as the host OS is already using >>> - >>> but this is NAT, not host-based networking, mode. I used to use the >>> Host-based networking, but lately I've fallen back to NAT which I >>> realize >>> won't work for you, but hopefully the above can give us some ideas as >>> to >>> what's wrong. In my old setup I'm pretty sure I had Host-based >>> networking >>> and still used the auto-dhcp and the default route on that VM got an >>> automatic gateway set that was the IP of the host machine (from the >>> point >>> of view of the VM). >>> ___ >>> PLUG mailing list >>> PLUG@lists.pdxlinux.org >>> http://lists.pdxlinux.org/mailman/listinfo/plug >>> >>> >> >> > > -- Michael Rasmussen Be Appropriate && Follow Your Curiosity ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] Pre-announce: 1st Thursday talk
Hello all, Jennifer Rondeau will be talking about documentation and its related processes on Thursday. I will have an announcement up ASAP. Michael Dexter PLUG Volunteer ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] VMPlayer host network only - semi resolved
Indeed it is the Windows host based packet filtering. Which is managed by a 3rd Party app. think of the bing names and it will be semi-obvious. Sometimes working for a bank is a bitch. My boss didn't think we had host based firewalling. Note: We both work in the corporate security department. Michael Rasmussen wrote: > > chris (fool) mccraw wrote: >> On Tue, Aug 4, 2015 at 4:05 PM, Ken Stephens wrote: >> >>> Michael Rasmussen wrote: >>> >>> > Both hosts can ping their own interface, yet neither can ping the >>> other's >>> > interface. >>> >> >> No surprise there - you can ping any address you configure as local by >> default :) > > And the sanity of "did I set up the interface?" was verified. > >> >>> Check your firewall settings on both the virtual and real machines. You >>> are probably blocking port 22 on one of them. > > No FW settings on the VM. This one is a clone of a production system that > we ssh to as part of regular work. > >>> >> >> ...but blocking ICMP by default as he mentioned ping doesn't work? That >> seems odd and unexpected to me. >> >> Michael, can you tell us what the setup is on each machine (eg VM = >> 10.1.1.1/255.0.0.0 w/route to that network via the interface, host= >> 10.1.1.2/255.0.0.0 route - note that I am more interested in what the >> Host >> machine's network settings are on the private network that gets setup >> for >> the VM than what its "external" IP/routes are)? Also, what host passes >> out >> the DHCP address to the VM - that should be in the logs somewhere? (My >> centos 7 VM puts it in /var/log/messages as 'server identifier x.y.z.q' >> in >> the middle of a bunch of NetworkManager output.) > > The DHCP server seems to be the VMWare player. > > Windows (host) side: > > Ethernet adapter VMware Network Adapter VMnet1: > >Connection-specific DNS Suffix . : >Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for > VMnet1 >Physical Address. . . . . . . . . : 00-50-56-C0-00-01 >DHCP Enabled. . . . . . . . . . . : No >Autoconfiguration Enabled . . . . : Yes >IPv4 Address. . . . . . . . . . . : 192.168.118.1(Preferred) >Subnet Mask . . . . . . . . . . . : 255.255.255.0 >Default Gateway . . . . . . . . . : >NetBIOS over Tcpip. . . . . . . . : Enabled > > Linux (VM instance) side: (this is typed as I can't cut and paste from > there. > > > ip addr show eth1 > 2: eth1: mtu 1500 qdisc pfifo_fast state > P qlen 1000 >link/ehter 00:0c:29:e3:63:d7 brd ff:ff:ff:ff:ff:ff >inet 192.168.118.128/24 brd 192.168.118.255 scope global eth1 >inet6 > > ip route > 192.168.118.0/24 dev eth1 proto kernel scope link src 192.168.118.128 > > That all looks sane to me. > > Curiously tcpdump shows: > 11:32:56.130921 arp who-has 192.168.118.1 tell 192.168.118.128 > 11:32:56.131059 arp reply 192.168.118.1 is-at 00:50:56:c0:00:01 > > So there's some communication on the line. The mac addr matches the > Window's mac. > > Now researching Windows FW and what happens to VM connections when I've a > VPN connection going. > > >> In my setup, that IP is given out by my host machine - which is not >> running >> DHCPd, so VirtualBox is using its builtin DHCP server, and just passes >> on >> many the same settings (eg nameservers) as the host OS is already using >> - >> but this is NAT, not host-based networking, mode. I used to use the >> Host-based networking, but lately I've fallen back to NAT which I >> realize >> won't work for you, but hopefully the above can give us some ideas as to >> what's wrong. In my old setup I'm pretty sure I had Host-based >> networking >> and still used the auto-dhcp and the default route on that VM got an >> automatic gateway set that was the IP of the host machine (from the >> point >> of view of the VM). >> ___ >> PLUG mailing list >> PLUG@lists.pdxlinux.org >> http://lists.pdxlinux.org/mailman/listinfo/plug >> >> > > -- Michael Rasmussen Be Appropriate && Follow Your Curiosity ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] VMPlayer host network only
chris (fool) mccraw wrote: > On Tue, Aug 4, 2015 at 4:05 PM, Ken Stephens wrote: > >> Michael Rasmussen wrote: >> >> > Both hosts can ping their own interface, yet neither can ping the >> other's >> > interface. >> > > No surprise there - you can ping any address you configure as local by > default :) And the sanity of "did I set up the interface?" was verified. > >> Check your firewall settings on both the virtual and real machines. You >> are probably blocking port 22 on one of them. No FW settings on the VM. This one is a clone of a production system that we ssh to as part of regular work. >> > > ...but blocking ICMP by default as he mentioned ping doesn't work? That > seems odd and unexpected to me. > > Michael, can you tell us what the setup is on each machine (eg VM = > 10.1.1.1/255.0.0.0 w/route to that network via the interface, host= > 10.1.1.2/255.0.0.0 route - note that I am more interested in what the Host > machine's network settings are on the private network that gets setup for > the VM than what its "external" IP/routes are)? Also, what host passes > out > the DHCP address to the VM - that should be in the logs somewhere? (My > centos 7 VM puts it in /var/log/messages as 'server identifier x.y.z.q' in > the middle of a bunch of NetworkManager output.) The DHCP server seems to be the VMWare player. Windows (host) side: Ethernet adapter VMware Network Adapter VMnet1: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1 Physical Address. . . . . . . . . : 00-50-56-C0-00-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.118.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Enabled Linux (VM instance) side: (this is typed as I can't cut and paste from there. ip addr show eth1 2: eth1: mtu 1500 qdisc pfifo_fast state P qlen 1000 link/ehter 00:0c:29:e3:63:d7 brd ff:ff:ff:ff:ff:ff inet 192.168.118.128/24 brd 192.168.118.255 scope global eth1 inet6 ip route 192.168.118.0/24 dev eth1 proto kernel scope link src 192.168.118.128 That all looks sane to me. Curiously tcpdump shows: 11:32:56.130921 arp who-has 192.168.118.1 tell 192.168.118.128 11:32:56.131059 arp reply 192.168.118.1 is-at 00:50:56:c0:00:01 So there's some communication on the line. The mac addr matches the Window's mac. Now researching Windows FW and what happens to VM connections when I've a VPN connection going. > In my setup, that IP is given out by my host machine - which is not > running > DHCPd, so VirtualBox is using its builtin DHCP server, and just passes on > many the same settings (eg nameservers) as the host OS is already using - > but this is NAT, not host-based networking, mode. I used to use the > Host-based networking, but lately I've fallen back to NAT which I realize > won't work for you, but hopefully the above can give us some ideas as to > what's wrong. In my old setup I'm pretty sure I had Host-based networking > and still used the auto-dhcp and the default route on that VM got an > automatic gateway set that was the IP of the host machine (from the point > of view of the VM). > ___ > PLUG mailing list > PLUG@lists.pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > > -- Michael Rasmussen Be Appropriate && Follow Your Curiosity ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
