[qubes-users] HCL - HP Elitebook 8570p

[Jos Bredek]

Works 95% out of the box. Only wireless drivers (bc43) have to be 
installed manually.


Sleep works

For Windows7 hvm, cirrus entry in video section cfg file needed.

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/01b3caf0d06fadabaf28aa914a349168%40mailbox.nederhost.net.
For more options, visit https://groups.google.com/d/optout.
---
layout:
  'hcl'
type:
  'notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  ''
brand: |
  Hewlett-Packard
model: |
  HP EliteBook 8570p
bios: |
  68ICF Ver. F.66
cpu: |
  Intel(R) Core(TM) i7-3540M CPU @ 3.00GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Intel Corporation 82579LM Gigabit Network Connection (rev 04)
  Broadcom Limited BCM43228 802.11a/b/g/n
memory: |
  8055
scsi: |
  MTFDDAK256MAM-1K Rev: 08TH
  CDDVDW SN-208DB  Rev: HH01

versions:

- works:
'yes'
  qubes: |
R3.2
  xen: |
4.6.3
  kernel: |
4.4.31-11
  remark: |
Wireless bc43 legacy drivers needed. For Windows 7 installation, cirrus 
video card  entry in cfg file needed.
  credit: |
Jos Bredek
  link: |
FIXLINK

---

[qubes-users] Networking & firewall

[Jos Bredek]

Hello there,

i'm relatively new to the qubes environment. So far, i'm really excited. I just 
love the concept!

Anyhow, today i stubmled into a problem; using my chromecast from one of my 
vm's within in qubes.

As a network-technician, my first thought.. this cant be hard. Boy, was i 
wrong. After quite some reading, i'm still puzzled. I've noticed that the 
netwerking & firewall document has the status TODO. Maybe something i can lend 
a little help with?

I've read the following posts:
https://groups.google.com/forum/#!searchin/qubes-users/inter-vm|sort:relevance/qubes-users/lA2SgPcV9fU/U969uapYAAAJ
https://www.qubes-os.org/doc/firewall/
http://theinvisiblethings.blogspot.nl/2011/09/playing-with-qubes-networking-for-fun.html
 (is this still valid?).

I get the general concept. 
- appVM's are connected to sys-firewall
- Sysfirewall is attached to sys-net
- no bridging involved, all routing.

But then:
- why are there subnets involved of 255.255.255.255?
- how much NATting is going on?
- what role does proxy arp play? Is it still used in 3.2?

Of course i can use wireshark and tcp dump to sort things out... but just maybe 
there is a good pointer to some other documentation? 

Can anyone point out some more reading material? If any?

Cheers!
Jos

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1e6e45a2-ec60-4d74-8af6-cfec00d86084%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.