On 5/29/19 2:15 PM, unman wrote:
On Wed, May 29, 2019 at 04:48:12AM -0700, ronp...@riseup.net wrote:
On 2019-05-28 23:36, unman wrote:
On Tue, May 28, 2019 at 07:29:31AM -0700, ronp...@riseup.net wrote:
On 2019-05-28 13:15, 'awokd' via qubes-users wrote:
ronp...@riseup.net:
On 2019-05-28 12:10, 'awokd' via qubes-users wrote:
ronp...@riseup.net wrote on 5/28/19 11:57 AM:
Re Qubes 4.0.
I have a openbsdVM but am unable to connect to internet. I'm using ip
adresses from qubes manager i.e ip=10.137.0.28 netmask=255.255.255.255
gateway=10.137.0.6 dns=10.139.1.1 & 10.139.1.2.
I'm able to ping 10.137.0.28 and 10.137.0.6 but unable to ping say
google.com.
I've tried without success copying the output from the command
"ifconfig" & "route show" - maybe someone can give me advice on how to
post the output to this forum?
Try making your netmask 255.255.255.0. You need to have Qubes Tools
running for clipboard integration, so you might only be able to post
screenshots if necessary.
Thanks for your prompt reply. I have tried netmask 255.255.255.0 - but
no success.
As you suggested, attached is a screenshot of the command "ifconfig"
Screenshot looks fine. "Route show" says your default route is to
10.137.0.6? Maybe reboot the HVM for good luck, if you haven't since
the subnet mask update. Seems like you're almost there since you can
ping 10.137.0.6.
As you suggested, I rebooted but it complained about netmask
255.255.255.0 and refused to ping anything.
I tried reverting to netmask 255.255.255.255 and now cannot ping
10.137.06
I'm adjusting these settings in /etc/hostname.xnf0 which now reads inet
10.137.0.28 255.255.255.255 10.137.0.6 Does that look right to you?
After changing these setting i run "sh /etc/netstart" Which I think is
equivalent to rebooting?
man hostname.if
man myname
Keep the 255.255.255.0 netmask
Put 10.137.0.6 in /etc/mygate
Thanks Unman for your latest input. I did as you suggested but am still
unable to ping the gateway (10.137.0.6).
My network settings now look like this: /etc/hostname.xnf0 = "inet
10.137.0.28 255.255.255.0"; /etc/mygate = "10.137.0.6"; /etc/resolv.conf
= "search my.domain nameserver 10.139.1.1 nameserver 10.139.1.2 lookup
file bind".
Thinking I'd maybe corrupted some other file, I created a new openbsdVM
and input the network settings during the setup procedure. However I got
exactly the same result - unable to ping the gateway.
Any further troubleshooting suggestions would be much appreciated?
Check the route on the netvm.
You likely have two routes back to the 10.137.0.28 address. Delete one.
SOLVED
I had mirage-firewall set as the default netvm. I changed the openbsdVM
firewall to sys-firewall and the network now works fine.
Thanks for your help
--
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/939835b8-8474-8439-0ca1-1f166f9d7496%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
