480 reputation
427
bio website yeri.be
location Belgium
age 26
visits member for 5 years, 1 month
seen Jul 9 at 0:27

Student in system & network management


2d
awarded  Popular Question
Jul
2
awarded  Curious
Jul
2
awarded  Popular Question
Jun
28
accepted All connections to a bridged domU originate from the dom0 public IP instead of real IP
Jun
28
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
it worked -- thanks ! :)
Jun
21
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
And I shouldn't run MASQUERADE on xenbr0? The LAN IP you gave is invalid as well (it'll be used by a vif interface, so I took .254). I'll try again when I'm back (abroad right now, limited internet)
Jun
21
accepted Outlook.com DNS so slow, postfix times out
Jun
21
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
The problem is that VMs with only xenbr1 as interface (= public IP, no NAT/lan) (and I've tried to bind xenbr1 to eth0:0) cannot connect to the internet (regardless of the iptables rule).
Jun
20
revised Outlook.com DNS so slow, postfix times out
added 101 characters in body
Jun
19
answered Outlook.com DNS so slow, postfix times out
Jun
19
revised Outlook.com DNS so slow, postfix times out
edited title
Jun
19
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
For your iptables: Can't use -i with POSTROUTING
Jun
19
asked Outlook.com DNS so slow, postfix times out
Jun
15
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
edited initial post with more details about iptables.
Jun
15
revised All connections to a bridged domU originate from the dom0 public IP instead of real IP
added 2711 characters in body
Jun
14
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
It also doesn't help to run masquerading on xenbr1.
Jun
14
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
Edited my initial post; it's due to iptables.
Jun
14
revised All connections to a bridged domU originate from the dom0 public IP instead of real IP
added 505 characters in body
Jun
14
comment All connections to a bridged domU originate from the dom0 public IP instead of real IP
I've just tried this, but this didn't solve my problem. Mind you, that this is also happening on DomU's with only a public IP (not NAT'ted at all).
Jun
14
revised All connections to a bridged domU originate from the dom0 public IP instead of real IP
added 19 characters in body