similar to: Problem with Internal accessing internal via web

Hello, I cannot establish Xserver connection via wireless subnet, while telnet is working fine. There was a similar problem before in Shorewall over IPSEC that Tom had fixed. Also, ping is working, but traceroute is not. Finally, PuTTY gets a connectivity error after couple minutes of inactivity over wireless when connected to the firewall/gateway. Wireless is configured per instructions in

This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh

someone recommended that i should give br0 the same hardware address as eno2. I did that, and restarted the vm, and it still does not work. Here is my current host interface config: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

Dear CentOS-Community, we are facing the following issue: A secondary ip address seems to be automatically added to a nic which causes several issues in our setup. This server is equipped with four nics which are currently in use: # nmcli con show NAME????? UUID????????????????????????????????? TYPE????? DEVICE eno2????? cb6fcb54-be52-4ab6-8324-88091a0ea1a0? ethernet? eno2 eno4?????

Network Configuration issues I''ve been working on this for 2 days PLEASE HELP! I am having the following issues with network configuration and I cannot ping the external interface to begin troubleshooting the network configuration. I know that the ISP''s router is configured correctly since I have attached it to a small Linksys firewall and was able to ping the 66.240.207.226

Hi Parke, Thanks, no I had not run those commands, but after doing so, my VPN address is not visible. See below: nsasia at db2:/etc/tinc$ sudo systemctl enable tinc at VPN1 Created symlink /etc/systemd/system/tinc.service.wants/tinc at VPN1.service → /lib/ systemd/system/tinc at .service. nsasia at db2:/etc/tinc$ systemctl start tinc at VPN1 ==== AUTHENTICATING FOR

Hi, see the log below root at AsteriskSlave:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: p3p1: <BROADCAST,MULTICAST> mtu

Hi, I would like to run a network firewall as a VM on a KVM host. There are ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. To save myself from configuring all VLANs on the KVM host, I'd like to hand the entire

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

Hi I am using Shorewall with a bridged Firewall using the "bridging utils" from Debian. eth0 is connected to the router and eth1 is connected to the local lan. eth0 and eth1 are both assigned zero addresses and br0 is assigned the Firewall server address of 192.168.0.1 I should point out that Shorewall is working fine in Bridge mode, but I have hit some problems while evaluating

Goodday, First my network layout: dsl router (10.0.0.99) | server (eth0 10.0.0.1, eth1 10.0.1.10) | 3 times windows machine (10.0.1.2, 10.0.1.3, 10.0.1.4) (all with proxy settings 10.0.1.10:8080) Now on the server is mandrake 10 installed with shorewall as firewall. And a apache webserver (and no ftp server). When i turned internet sharing on it started squid which added a line in the

Laine wrote: > -----Original Message----- > From: sendmail [mailto:justsendmailnothingelse@gmail.com] On Behalf > Of Laine Stump > Sent: Monday, March 16, 2015 4:12 PM > To: libvirt-users@redhat.com > Cc: Lentes, Bernd > Subject: Re: [libvirt-users] still possible to use traditional bridge network > setup ? > > On 03/16/2015 10:08 AM, Lentes, Bernd wrote: > >

Hello, I''m trying to configure my desktop as a bluetooth network access point for my ipaq (as explained in http://www.stolk.org/debian/bluetooth.html). I''m running shorewall version 2.2.1 on debian testing with a local network via eth0 and internet access via eth1. I''ve created a bridge br0 for eth0 and bnep0 and activated bridging in shorewall. dhcpd is listening

Hi all, I have done some tests for the new attributes "check" and "type", could you please help to have a check? And I have some questions about the patch, please help to have a look, Thank you! The questions: 1. in step 4 below, the error message should be updated: Actual results: XML error: invalid mac address **check** value: 'next'. Valid values are

I just see warning? 2016-08-29 11:30 GMT-03:00, Telium Technical Support <support at telium.ca>: > This shows that asterisk's IAX is already bound to all adapters - so that's > good. Symptomatically does your IAX stop working? Or do you just see a > warning? > > -----Original Message----- > From: asterisk-users-bounces at lists.digium.com >

Hello everybody. I could not find an answer to my problem in the archive. (But that may just be me :-) ) I have a problem with proxy arp and connection from loc (localnet) and from the firewall. Works fine from internet to dmz / proxy arp and vise versa. I have a feeling the solution is simple, but I''m no guru in Linux routing etc. The problem seems to be the routing setup. loc -

18. Juli 2017 16:45, "Michal Privoznik" <mprivozn@redhat.com> schrieb: > On 07/18/2017 04:31 PM, c.monty@web.de wrote: > >> Hello! >> >> I have upgraded all libvirt packages to version 3.5.0-655.1 and restarted host. > > That wasn't necessary. It's not Windows ;-) > >> This is the current default network config: >> ld4004:~

Having a problem with the 3 interface setup. I can get DMZ hosts, and FW to see internet, but anything on LOC interface is unable to get out. My first post to the list didn''t have the information needed, sorry for that, but thank you for pointing me to more resources. I''ve looked at the problem myself some more, but am still stuck. Shorewall Version: 2.2.1 ip addr show 1:

Oh! In that case ignore it. Asterisk won't rebind the adapter if you've only changed parameters. The message is misleading -----Original Message----- From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Vitor Mazuco Sent: Monday, August 29, 2016 10:41 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: