No Internet through sys-net and sys-firewall in qubes 4.0

33 views
Skip to first unread message

Taehwan Kim

unread,
Feb 6, 2020, 12:45:40 PM2/6/20
to qubes-users
Hi all.
I need your help.

I just did cleaned up dnf package and rm -rf /var/log in fedora-30 template which sys-net and sys-firewall using for template last night.
But my qubes not connecting internet through sys-firewall and tried netvm with sys-net in other appVM but no internet.
Only in sys-net internet is working. So I checked..

In sys-net
ip addr | grep -i cast

2: wls7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 <--- this is wifi connection
3: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 <--- this is wired connection
4: vif16.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 32 <-- I think this is sys-firewall connected to sys-net

in sys-firewall
ip addr | grep -i cast

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
3: vif18.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 32

I have no idea how to find a problem for this. If sys-firewall has some problem, internet must be working when I use sys-net for net vm for appVM..
But I switched to sys-net as netvm for appvm, Internet is not working.
So I think I have a problem with sys-net maybe..

Can you help me? :(

awokd

unread,
Feb 9, 2020, 8:51:49 AM2/9/20
to qubes...@googlegroups.com
Taehwan Kim:

> In sys-net

> 4: vif16.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 32 <-- I think this is sys-firewall connected to sys-net
>
> in sys-firewall
> ip addr | grep -i cast
>
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
> default qlen 1000
> 3: vif18.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 32

Yes, that vif interface should be UP on both. Check sudo journalctl in
sys-net to see if any related errors are logged. Might try creating a
new sys-net from scratch to see if that helps (make a new AppVM with
"provides network" checked, set to HVM, attach your NIC(s)).

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
Reply all
Reply to author
Forward
0 new messages