Re: Bind9 local DNS not forwarding query to public DNS

Muhammad Yousuf Khan wrote: > Need your experience advice, We have a BIND9 DNS server that operates both > privately and publicly for the domain example xyz.com. I use the private > DNS for certain secure nodes on our local network. I want all VPN users to > be able to resolve these secure nodes u

Re: Bind9 local DNS not forwarding query to public DNS

On 12/03/2024 12:48, Muhammad Yousuf Khan wrote:   Dear All, Need your experience advice, We have a BIND9 DNS server that operates both privately and publicly for the domain example xyz.com . I use the private DNS for certain secure nodes on our local network. I want all VPN

Bind9 local DNS not forwarding query to public DNS

Dear All, Need your experience advice, We have a BIND9 DNS server that operates both privately and publicly for the domain example xyz.com. I use the private DNS for certain secure nodes on our local network. I want all VPN users to be able to resolve these secure nodes using our local DNS, which

Re: upgrade to bookworm broke ssh x11 forwarding

On Mon, Nov 13, 2023 at 11:10:17AM +0100, Vincent Lefevre wrote: [...] > This is what I've done for my old laptop, but the dropbear package > is *not* needed for that! You just need the dropbear-initramfs > package [...] Aha -- now I know the full story. Thanks, Vincent (and all the other smart

Re: upgrade to bookworm broke ssh x11 forwarding

On 2023-11-10 15:32:53 +, fxkl4...@protonmail.com wrote: > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > >>> No, this is not a normal phenomenon for bookworm upgrades. I've

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri, Nov 10, 2023 at 01:01:28PM -0500, Dan Ritter wrote: > to...@tuxteam.de wrote: [...] > > Wait a minute: dropbear is supposed to run in the initramfs, while > > sshd will be active afterwards, after pivot-root and all that, right? > > > > Then I don't quite get why they should collide at

Re: upgrade to bookworm broke ssh x11 forwarding

to...@tuxteam.de wrote: > On Fri, Nov 10, 2023 at 03:32:53PM +, fxkl4...@protonmail.com wrote: > > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > > >>> No, this is not

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri, Nov 10, 2023 at 03:32:53PM +, fxkl4...@protonmail.com wrote: > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > >>> No, this is not a normal phenomenon for bookworm upgr

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri 10 Nov 2023 at 15:32:53 (+), fxkl4...@protonmail.com wrote: > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > >>> No, this is not a normal phenomenon for bookworm upgrad

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri, 10 Nov 2023, Vincent Lefevre wrote: > On 2023-11-10 10:57:21 +0100, Michael wrote: >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: >>> No, this is not a normal phenomenon for bookworm upgrades. I've never >>> heard of it happening to anyone before. >> >> i disagree. i h

Re: upgrade to bookworm broke ssh x11 forwarding

On 2023-11-10 10:57:21 +0100, Michael wrote: > On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > > No, this is not a normal phenomenon for bookworm upgrades. I've never > > heard of it happening to anyone before. > > i disagree. i had the same problem b/c i also had dropbear insta

Re: upgrade to bookworm broke ssh x11 forwarding

On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: No, this is not a normal phenomenon for bookworm upgrades. I've never heard of it happening to anyone before. i disagree. i had the same problem b/c i also had dropbear installed. for some reason the dropbear daemon is started f

Re: upgrade to bookworm broke ssh x11 forwarding

lseye to bookworm with no problems > >>> when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails > >>> > >>> debug1: Requesting X11 forwarding with authentication spoofing. > >>> debug1: Sending environment. > >>> debug1: S

Re: upgrade to bookworm broke ssh x11 forwarding

-X/-Y to the bookworm machine x11 forwarding fails >>> >>> debug1: Requesting X11 forwarding with authentication spoofing. >>> debug1: Sending environment. >>> debug1: Sending env LANG = en_US.UTF-8 >>> debug1: Sending env LC_ALL = en_US.UTF-8 >>>

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, 9 Nov 2023, Greg Wooledge wrote: > On Thu, Nov 09, 2023 at 04:59:32PM +, fxkl4...@protonmail.com wrote: >> now it makes a bit more sense >> sshd isn't running >> for some reason the upgrade switched to dropbear >> is this a new thing for bookworm >> is there a reason i shouldn't disabl

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, Nov 9, 2023 at 11:43 AM Greg Wooledge wrote: > > On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: > > i upgraded from bullseye to bookworm with no problems > > when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails > > &g

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, Nov 09, 2023 at 04:59:32PM +, fxkl4...@protonmail.com wrote: > now it makes a bit more sense > sshd isn't running > for some reason the upgrade switched to dropbear > is this a new thing for bookworm > is there a reason i shouldn't disable dropbear and use sshd No, this is not a normal

Re: upgrade to bookworm broke ssh x11 forwarding

-Y to the bookworm machine x11 forwarding fails >>> >>> debug1: Requesting X11 forwarding with authentication spoofing. >>> debug1: Sending environment. >>> debug1: Sending env LANG = en_US.UTF-8 >>> debug1: Sending env LC_ALL = en_US.UTF-8 >>> X11 forwa

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, 9 Nov 2023, Greg Wooledge wrote: > On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: >> i upgraded from bullseye to bookworm with no problems >> when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails >> >> debug1: Req

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: > i upgraded from bullseye to bookworm with no problems > when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails > > debug1: Requesting X11 forwarding with authentication spoofing. >

upgrade to bookworm broke ssh x11 forwarding

i upgraded from bullseye to bookworm with no problems when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails debug1: Requesting X11 forwarding with authentication spoofing. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending env LC_ALL = en_US.UTF-8

Re: OT: Forwarding and top posting (was: Re: OT: Pedantic, yet wrong)

Hello, On Thu, Jun 22, 2023 at 04:24:47PM -0700, Manphiz wrote: > Personally I don't have a strong preference either way, but would like > to hear more opinions on this. The complaint about a top-posted forwarded message just because it had a contextual hint at the top, seemed excessive to me. I

OT: Forwarding and top posting (was: Re: OT: Pedantic, yet wrong)

ep prior content, I click "Reply", copy the content to the > clipboard, create a new message, paste, and choose Edit -> Rewrap. This > produces a new thread with proper indentation of prior content. Perhaps your > mail client has a similar capability. > > > HTH, > >

Re: FirewallD Masquerading and route forwarding

set to use zone drop and my inside facing zone is > set to use zone trusted. > > # enable routing > echo 1 > /proc/sys/net/ipv4/ip_forward > > # verify IP forwarding is enabled. > cat /proc/sys/net/ipv4/ip_forward > 1 > > # Configure Masquerade zone > firewall-cm

FirewallD Masquerading and route forwarding

pv4/ip_forward # verify IP forwarding is enabled. cat /proc/sys/net/ipv4/ip_forward 1 # Configure Masquerade zone firewall-cmd --zone=drop --add-masquerade --permanent firewall-cmd --reload # check masquerade configuration firewall-cmd --zone=drop --query-masquerade yes # Ping Test Internet facing

SOLVED Re: Forwarding over wireguard

On Wed, 8 Dec 2021 13:30:45 -0700 Charles Curley wrote: > I have a wireguard setup that lets me ping from either endpoint to the > other. Using the client, I would like to address hosts on the home > (server's) network by their local IP addresses. > > On the client, I can ping the other end of t

Re: Forwarding over wireguard

irbr0 192.168.124.0 jhegaala.locald 255.255.255.0 UG0 0 0 enp3s0 root@hawk:/etc/wireguard# > > Is it forwarding IPv4 packets for anything else, or is this the > first time it's been a router? Not the first time. It forwards packets for 192.168.122.0/24, a vir

Re: Forwarding over wireguard

g0. What does the home server's routing table look like? Is it forwarding IPv4 packets for anything else, or is this the first time it's been a router? Does it have any firewall policies or rules? -dsr-

Forwarding over wireguard

I have a wireguard setup that lets me ping from either endpoint to the other. Using the client, I would like to address hosts on the home (server's) network by their local IP addresses. On the client, I can ping the other end of the tunnel, but not any local addresses. On the client: root@iorich:

SSH agent forwarding (was: weird behaviour of quotes in dash variable assignments)

er ssh-agent and SSH agent forwarding. These allow you to access your version control server over SSH from remote hosts by using your workstation credentials; no credentials required on the remote host: https://dev.to/levivm/how-to-use-ssh-and-ssh-agent-forwarding-more-secure-ssh-2c32 Davi

Automating email forwarding using kmail 1.13.7 (on Wheezy)

I'd consider trying it behind kmail (that is, if it is possible, setting it up to pick out certain emails from a kmail mbox and forwarding those -- see below). Goal: I get some emails that I want to forward to a select group of friends and relatives on a regular basis (at least daily).

Re: Forwarding to report-listspam.d.o vs bounce [was: Kind reminder: please don't reply to and/or quote spam, ever]

to...@tuxteam.de wrote: > On Sun, Apr 19, 2020 at 01:27:40PM +0200, Sven Hartge wrote: >> Andrei POPESCU wrote: >>> As far as I know "forwarding as attachment" does not affect the >>> original message (though this may depend on the client), however it >>

Forwarding to report-listspam.d.o vs bounce [was: Kind reminder: please don't reply to and/or quote spam, ever]

o be confirmed) is "remailing" and > >>> it involves resending the message (mostly untouched) to another > >>> address. > >> > >> Ah, I see. I was betting on "forwarding", but later it occurred to me > >> that this would wrap

Forwarding reply [Re: Debian Format Disk]

On 08/17/2019 08:57 AM, Finariu Florin wrote: > Hi, > Is Debian 10 > Cinnamon. > Thank you! Please bottom post. Please reply to list. I can not confidently answer your question as I use neither that release nor Desktop. > > On Saturday, August 17, 2019, 09:12:11 a.m. GMT-4, Richard Owlett >

Re: just mail forwarding to smart mailer

On Sb, 13 apr 19, 10:14:04, Bonno Bloksma wrote: > I am looking for an "easy light weight just empty the local queue and > send it to the smart host" setup. > I don't mind experimenting and it doesn not need to be Exim but the > info I get Googling is just too diverse and does not get me much >

Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch

On 6/5/19 10:26 PM, Simon S wrote: > I think i found the culprit: > > I use the debian apt repo for machinekit and the rt kernel: > deb [arch=armhf] http://repos.rcn-ee.com/debian/ stretch main > > This repo installs libGL.so.1.0.0 instead of libGL.so.1.2.0. > I forced to use the default debian a

Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch

I think i found the culprit: I use the debian apt repo for machinekit and the rt kernel: deb [arch=armhf] http://repos.rcn-ee.com/debian/ stretch main This repo installs libGL.so.1.0.0 instead of libGL.so.1.2.0. I forced to use the default debian apt source repo and purged all libgl stuff from t

Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch

Am Sonntag, 2. Juni 2019 15:00:05 UTC+2 schrieb Simon S: > Hi, > > I have a weird problem with opengl forwarding via ssh. > I am running debian jessie on my BeagleBone Black (armhf) that I use for my > CNC machine by running machinekit. > Everything works as expected, I even g

Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch

Hi! Thanks for testing it out! I was wondering if it had to do with an user beeing logged in to lxde. I think autologin might be enabled on the jessie system. Unfortunately this does not help. Still the same problem on stretch. I have some additional info. Without exporting the inderect renderin

Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch

Simon, on 2019-06-02: > The following test setup: > (A) linux machine running ubuntu (Nvidia GPU) > (B) BBB running jessie > (C) BBB running stretch > > I connect from (A) -> (*) by ssh -X x@host > > When I connect from (A) to (B): > > export LIBGL_ALWAYS_INDIRECT=1; glxinfo|head > name of display

OpenGL forwarding via ssh session: works on jessie, does not work on stretch

Hi, I have a weird problem with opengl forwarding via ssh. I am running debian jessie on my BeagleBone Black (armhf) that I use for my CNC machine by running machinekit. Everything works as expected, I even got indirect opengl rendering working when I connect to the BBB using windows. Now I

Re: ssh local port forwarding stopped working

ht VNC viewer. Since I can connect to the remote workstations from the VM, the problem cannot be with their service setup. And since the problem isn't resolved by using a different VNC viewer from my local workstation, the problem can't be the VNC client. This just leaves the ssh tunnel -

Re: ssh local port forwarding stopped working

connect to the remote workstations from the VM, the problem > cannot be with their service setup. And since the problem isn't resolved > by using a different VNC viewer from my local workstation, the problem > can't be the VNC client. This just leaves the ssh tunnel - specifically > the port forwarding - as the only common element. > >

ssh local port forwarding stopped working

't resolved by using a different VNC viewer from my local workstation, the problem can't be the VNC client. This just leaves the ssh tunnel - specifically the port forwarding - as the only common element.

Re: just mail forwarding to smart mailer

On 2019-04-16, Bonno Bloksma wrote: > Hi, > >>> > I am looking for an "easy light weight just empty the local queue >>> > and very very very easy thing: https://wiki.debian.org/sSMTP >> >> Note that sSMTP does not perform server certificate verification, thus >> allowing, e.g., credential steali

RE: just mail forwarding to smart mailer

Hi, >> > I am looking for an "easy light weight just empty the local queue >> > and very very very easy thing: https://wiki.debian.org/sSMTP > > Note that sSMTP does not perform server certificate verification, thus > allowing, e.g., credential stealing via MITM attacks. Furthermore, it > negle

Re: just mail forwarding to smart mailer

On Tue, 16 Apr 2019 13:53:05 + Bonno Bloksma wrote: > Hi, > > >> > I am looking for an "easy light weight just empty the local queue > >> > and very very very easy thing: https://wiki.debian.org/sSMTP > > > > Note that sSMTP does not perform server certificate verification, thus > > allowi

Re: just mail forwarding to smart mailer

On Sun, 14 Apr 2019 22:17:44 +0900 황병희 wrote: > > I am looking for an "easy light weight just empty the local queue and > > Very very very easy thing: https://wiki.debian.org/sSMTP Note that sSMTP does not perform server certificate verification, thus allowing, e.g., credential stealing via MIT

Re: just mail forwarding to smart mailer

On Mon, 15 Apr 2019 18:42:57 +0200 Wim wrote: > Hi Bonno, > > On Sunday, 14 April at 08:00, Bonno Bloksma wrote: > > > > > All along I just installed the standard system on a Debian machine. Created > > an alias for the root user with the email address of our servicedesk to > > have it send

Re: just mail forwarding to smart mailer

Hi Bonno, On Sunday, 14 April at 08:00, Bonno Bloksma wrote: > > All along I just installed the standard system on a Debian machine. Created > an alias for the root user with the email address of our servicedesk to have > it send any mails to my servicedesk account and that was it. > The last

Re: just mail forwarding to smart mailer

> I am looking for an "easy light weight just empty the local queue and Very very very easy thing: https://wiki.debian.org/sSMTP Sincerely, Byung-Hee from South Korea. -- ^고맙습니다 _地平天成_ 감사합니다_^))//

Re: just mail forwarding to smart mailer

Hi. On Sat, Apr 13, 2019 at 10:14:04AM +, Bonno Bloksma wrote: > I am looking for an "easy light weight just empty the local queue and send it > to the smart host" setup. apt install nullmailer Reco

Re: just mail forwarding to smart mailer

Bonno Bloksma wrote: > Hi, > > All along I just installed the standard system on a Debian machine. > Created an alias for the root user with the email address of our > servicedesk to have it send any mails to my servicedesk account and that > was it. The last Debian installations no longer have a

just mail forwarding to smart mailer

Hi, All along I just installed the standard system on a Debian machine. Created an alias for the root user with the email address of our servicedesk to have it send any mails to my servicedesk account and that was it. The last Debian installations no longer have a default mailserver installed an

Re: IPv6 router is not forwarding packets

On 07.01.19 23:06, Rainer Dorsch wrote: > "Configure the IPv6 router so that it requests its own prefix from the > FRITZ!Box > using IPv6 prefix delegation and that it announces its routing information to > the FRITZ!Box via router advertisement." > > https://en.avm.de/service/fritzbox/fritzbo

Re: IPv6 router is not forwarding packets

Hi Ulf, many thank again for your reply. Am Sonntag, 6. Januar 2019, 21:40:21 CET schrieb Ulf Volmer: > Yes, looks weird. I have no idea why this happens. > > Just one point, the response times of hop 3 in your second traceroute > are quite low (instead of hop 2 in the first one). Are you sure t

Re: IPv6 router is not forwarding packets

On 06.01.19 21:29, Rainer Dorsch wrote: > rd@home:~$ traceroute6 2a03:4000:6:52b6:: > traceroute to 2a03:4000:6:52b6:: (2a03:4000:6:52b6::), 30 hops max, 80 byte > packets > 1 fritz.box (2a02:8070:898f:e400:e228:6dff:fe43:5776) 0.723 ms 0.608 ms > 0.710 ms > 2 2a02:8070:8900::1 (2a02:8070

Re: IPv6 router is not forwarding packets

> > Things are getting weirder now... :-/ Just looking at the differences between the traceroutes from home (stretch router) and mohot (endpoint): rd@home:~$ traceroute6 2a03:4000:6:52b6:: traceroute to 2a03:4000:6:52b6:: (2a03:4000:6:52b6::), 30 hops max, 80 byte packets 1 fritz.box (2a02:8

Re: IPv6 router is not forwarding packets

Hi Pascal, Ulf, and Georgi, many thanks for your replies, they brought me at least one step further :-) Am Sonntag, 6. Januar 2019, 20:54:43 CET schrieb Ulf Volmer: > On 06.01.19 20:47, Rainer Dorsch wrote: > > does not do automatic stuff. But after a reboot I still get > > > > root@mohot:~# ip

Re: IPv6 router is not forwarding packets

On 06.01.19 20:47, Rainer Dorsch wrote: > does not do automatic stuff. But after a reboot I still get > > root@mohot:~# ip -6 a show eth0 > 2: eth0: mtu 1500 state UP qlen 1000 > inet6 2a02:8070:898f:e400:d263:b4ff:fe00:4dd1/64 scope global dynamic > mngtmpaddr >valid_lft 7126sec p

Re: IPv6 router is not forwarding packets

On 06.01.19 20:33, Pascal Hambourg wrote: > Le 06/01/2019 à 20:23, Rainer Dorsch a écrit : >> Isn't the /64 the prefix length and longer prefixes than 64 are not >> supported in >> ipv6? > > IPv6 supports any prefix size. Only SLAAC (autoconfiguration using RA's) > requires /64. Usually he will g

Re: IPv6 router is not forwarding packets

Am Sonntag, 6. Januar 2019, 20:29:27 CET schrieb Pascal Hambourg: > You should start with a fully static setup on the host, fix routing, and > when done you can try to setup SLAAC/DHCPv6. I agree. I thought that iface eth0 inet6 manual does not do automatic stuff. But after a reboot I still get

Re: IPv6 router is not forwarding packets

Le 06/01/2019 à 20:23, Rainer Dorsch a écrit : Am Sonntag, 6. Januar 2019, 19:49:13 CET schrieb Pascal Hambourg: BTW, I am a bit surprised by the upstream setup. It wastes a full /64 just for one address. Do yo mean the 2a02:8070:898f:e400:d263:b4ff:fe00:325c/64 in Yes. Isn't the /64 the

Re: IPv6 router is not forwarding packets

On 1/6/19 9:23 PM, Rainer Dorsch wrot> Isn't the /64 the prefix length and longer prefixes than 64 are not supported in > ipv6? > For IPv6 there are two methods for IP address distribution - Router Advertisement and DHCPv6. Router Advertisement doesn't support prefixes longer than /64. On the o

Re: IPv6 router is not forwarding packets

Le 06/01/2019 à 19:59, Rainer Dorsch a écrit : Am Sonntag, 6. Januar 2019, 19:32:46 CET schrieb Ulf Volmer: I'm confused that you have uplink and downlink addresses configured on the client. Anyway, can you also post 'ip -6 r' from the client? I have not explicitly configured the addresses, b

Re: IPv6 router is not forwarding packets

Am Sonntag, 6. Januar 2019, 19:49:13 CET schrieb Pascal Hambourg: > Le 06/01/2019 à 19:32, Ulf Volmer a écrit : > > On 06.01.19 18:36, Rainer Dorsch wrote: > >> inet6 2a02:8070:898f:e400:d263:b4ff:fe00:4dd1/64 scope global dynamic > >> mngtmpaddr>> > >>valid_lft 7030sec preferr

Re: IPv6 router is not forwarding packets

; > > > for prefix delegation, I followed the Debian wiki > > > > https://wiki.debian.org/IPv6PrefixDelegation > > > > And routing information: > > root@home:/etc# ip -6 r > > 2a02:8070:898f:e400::/64 dev eth0.1 proto kernel metric 256 expires > > 6974sec pref

Re: IPv6 router is not forwarding packets

Hi Ulf, Am Sonntag, 6. Januar 2019, 19:32:46 CET schrieb Ulf Volmer: > On 06.01.19 18:36, Rainer Dorsch wrote: > > Endpoint: > > - > > rd@mohot:~$ ip addr show dev eth0 > > 2: eth0: mtu 1500 qdisc pfifo_fast state > > UP group default qlen 1000 > > > >link/ether d0:63:b4:00:4d:d1 brd

Re: IPv6 router is not forwarding packets

Le 06/01/2019 à 19:32, Ulf Volmer a écrit : On 06.01.19 18:36, Rainer Dorsch wrote: inet6 2a02:8070:898f:e400:d263:b4ff:fe00:4dd1/64 scope global dynamic mngtmpaddr valid_lft 7030sec preferred_lft 3430sec inet6 2a02:8070:898f:e4f8:d263:b4ff:fe00:4dd1/64 scope global dynamic mngt

Re: IPv6 router is not forwarding packets

t@home:/etc# ip -6 r 2a02:8070:898f:e400::/64 dev eth0.1 proto kernel metric 256 expires 6974sec pref medium 2a02:8070:898f:e4f8::/62 dev eth0.7 proto kernel metric 256 pref medium (...) IPv6 forwarding is enabled: root@home:/etc# cat /proc/sys/net/ipv6/conf/all/forwarding 1 root@home:/etc# cat

Re: IPv6 router is not forwarding packets

On 06.01.19 18:36, Rainer Dorsch wrote: > Endpoint: > - > rd@mohot:~$ ip addr show dev eth0 > 2: eth0: mtu 1500 qdisc pfifo_fast state UP > group default qlen 1000 >link/ether d0:63:b4:00:4d:d1 brd ff:ff:ff:ff:ff:ff >inet 192.168.7.31/24 brd 192.168.7.255 scope global eth0 >

IPv6 router is not forwarding packets

6:: is address debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to 2a03:4000:6:52b6:: [2a03:4000:6:52b6::] port 22. IPv6 forwarding is enabled on the home (stretch router): # cat /proc/sys/net/ipv6/conf/all/forwarding 1 # For me it seems that home is dropping the request, if that is th

Re: SSH & X11 forwarding

Am 23. Nov, 2018 schwätzte Martin so: moin moin, please don't 'xhost +', that should not be needed. The application being tunneled comes from localhost, so you shouldn't need any xhost adjustment. ciao, der.hans Hi list members, I have not used X11 over ssh for years now. But today is the

Re: Got it: SSH & X11 forwarding

On Fri, Nov 23, 2018 at 03:16:31PM +0100, Martin wrote: > Stupid as it can be: X is running with -nolisten. > > Thanks good it's Friday, cheers. > If you are not logging in with 'ssh -X ' or 'ssh -Y ....' then you are not X forwarding over ssh. In part

Got it: SSH & X11 forwarding

Stupid as it can be: X is running with -nolisten. Thanks good it's Friday, cheers.

Re: SSH & X11 forwarding

part. You definitely do not need to run X server at the host to which ssh connnects to, X11 Forwarding works perfectly via IPv6, and you definitely do not need to set $DISPLAY by hand in the ssh connection. > What did I miss? A wild guess - installing xauth. And running sshd -Xv. Reco

Re: SSH & X11 forwarding

Le 23-11-2018, à 14:48:09 +0100, Martin a écrit : Hi list members, I have not used X11 over ssh for years now. But today is the day! And it does not work The remote console tells me 'Xt error: Can't open display: :0'. X11Forwarding is enabled on client and server, 'xhost +' on the client,

Re: SSH & X11 forwarding

Am Freitag, 23. November 2018, 14:48:09 CET schrieb Martin: Hi Martin, did you try ssh -X -l yourusername 192.168.what_ip.whatever? This should work by default. Any graphical application should then show on your client (as fas as you have linux on it at all). Running this from Windows, you ne

SSH & X11 forwarding

Hi list members, I have not used X11 over ssh for years now. But today is the day! And it does not work The remote console tells me 'Xt error: Can't open display: :0'. X11Forwarding is enabled on client and server, 'xhost +' on the client, DISPLAY is set. IPv6 is disabled on both ends with s

X11 Forwarding and inet6 support on loopback (Was: Micro-report: using Stable without systemd)

owing problem was referred to, which somehow, is network specific: https://lists.debian.org/debian-user/2018/09/msg00836.html Digging more in that issue shows that, somehow, the forwarding expects the loopback address to be reachable in inet6. Indeed the following command, run on SSH serve

Re: SSH X forwarding going awry FIXED (Was: Why does Debian allow all incoming traffic by default)

On Sunday 23 September 2018 16:55:39 Joe wrote: > On Sun, 23 Sep 2018 09:55:48 -0400 > > Gene Heskett wrote: > > synaptic-pkexec still doesn't. > > > > > > > > So I'm still restricted to doing updates with apt. > > not a show stopper, but the rock64 can do that 20x faster. > > I vaguely recall ha

Re: SSH X forwarding going awry FIXED (Was: Why does Debian allow all incoming traffic by default)

On Sun, 23 Sep 2018 09:55:48 -0400 Gene Heskett wrote: > synaptic-pkexec still doesn't. > > > So I'm still restricted to doing updates with apt. > not a show stopper, but the rock64 can do that 20x faster. > I vaguely recall having trouble with this on sid years ago, and completely failing

Re: SSH X forwarding going awry FIXED (Was: Why does Debian allow all incoming traffic by default)

o both IPv4 and v6 interfaces. When v6 > links are unavailable, for /some reason/ (I don't recall the > details), X forwarding attempts are prevented, but normal SSH > continues as usual (with a warning about X11 forwarding having > failed to start). > > To fix this, two d

SSH X forwarding going awry (Was: Why does Debian allow all incoming traffic by default)

ledged with the courtesy of even a > reply with a link to a tut. If this can help, since Debian Jessie, SSH server is configured by default to listen to both IPv4 and v6 interfaces. When v6 links are unavailable, for /some reason/ (I don't recall the details), X forwarding attempts are pr

Keyboard woes with X forwarding

Hello My main PC runs Debian Jessie and supports 2 virtual Windows machines using VirtualBox. On the Windows machines I run Logmein which allows me to access the Windows machines from my Android tablet when on the road. I have installed Xming on the VMs and sometimes use SSH with X forwarding

Re: root@localhost mail not forwarding in Exim

Yes, this indeed was the problem! For some reason the mail was being sent to "user" even though I had no user named that. Thanks a bunch! I have had this problem for quite a while and never could figure out how to fix it. On Thu, Mar 2, 2017 at 5:34 AM, Bonno Bloksma wrote: > Hi, > > >[]

RE: root@localhost mail not forwarding in Exim

Hi, >[] > so, if I want to use mail.example.com as my fqdn, and the old fqdn was > something.else and r...@something.else was redirecting mail to > m...@something.else ... then what do I need to change in Exim to make this > happen? Is it maybe the aliases setting? Probably you edited the

Re: root@localhost mail not forwarding in Exim

Have you tried sudo dpkg-reconfigure exim4-config Which Settings you have there? Am 01.03.2017 um 21:40 schrieb Jiangsu Kumquat: > I changed my server name and fqdn and now the mail to root@localhost is > bouncing. > > I went into every file that had the old name and changed it to the new name

root@localhost mail not forwarding in Exim

I changed my server name and fqdn and now the mail to root@localhost is bouncing. I went into every file that had the old name and changed it to the new name but it still doesn't work. I did "grep -r something.else /etc" to find all the files. so, if I want to use mail.example.com as my fqdn, and

root@localhost mail not forwarding in Exim

I changed my server name and fqdn and now the mail to root@localhost is bouncing. I went into every file that had the old name and changed it to the new name but it still doesn't work. I did "grep -r something.else /etc" to find all the files. so, if I want to use mail.example.com as my fqdn, and

Solved: Re: Icedove Mail Forwarding Problem - Thanks for the Solution

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/21/2015 10:55 AM, Thomas H. George wrote: [...] >> Thanks I just tested Shift-Forward and it worked like a charm. >> With this problem solved Icedove works perfectly for me. Great! Nice to hear. Regards, Ralph -BEGIN PGP SIGNATURE- Ve

Re: Icedove Mail Forwarding Problem

On Sat, Jun 20, 2015 at 03:48:45PM -0400, Ralph Katz wrote: > Perhaps you are forwarding email with inline links to images > instead of the actual image data itself? Are there not some horrible M$-specific ways of "attaching" images to some email messages? These seem to

Re: Icedove Mail Forwarding Problem

to relate to this. Perhaps you are forwarding email with inline links to images instead of the actual image data itself? Or your defaults are Compose in text while you are attempting to forward html email with images? In the latter case, Shift-Forward will bring up the compose window for html

Icedove Mail Forwarding Problem

When I try to forward an email containing images Icedove does not send the images just some text about the images. Is there a setting I have wrong? Nothing I find in preferences seems to relate to this. There is a hack: Icedove will convert the email to a pdf file which can be attached to a m

Re: IP Forwarding to Windows machine

Nemeth Gyorgy a écrit : >> > Yes, it can work as a short go-nogo test. But the suggestion was not > mentioned it, that it is only for that. And it is very likely that when > the OP tries this and it 'works' (I mean the Windows machine behind the > Linux works well), then the rules will remain. I w

Re: IP Forwarding to Windows machine

I adopted Mr. Gyorgy's suggested iptables rules with only a couple of additions based on nmap's report that port 411 was open because it passed with flying colors nmaps tcp and udp scan of the first 1056 ports, grc.com tests and pcflank.com tests. For a single user system running no service

Re: IP Forwarding to Windows machine

2014-08-10 22:30 keltezéssel, Joe írta: > Why is it unresolvable? A DROP/REJECT policy is fail-safe, ACCEPT > isn't. If the rest of the rules are correct, (and more importantly, > guaranteed always to stay that way in the face of editing, sometimes > rushed) an ACCEPT policy is redundant, and if th

Re: IP Forwarding to Windows machine

On Tue, Aug 12, 2014 at 5:19 AM, Joe wrote: > On Tue, 12 Aug 2014 04:53:51 -0400 > Tom H wrote: >> >> And you've proven my point... > > Agreed, I just can't see why there is any controversy. You misunderstand. The fact that you can't accept that there may be others who have good reason (whatever

Re: IP Forwarding to Windows machine

On Tue, 12 Aug 2014 04:53:51 -0400 Tom H wrote: > > And you've proven my point... > > Agreed, I just can't see why there is any controversy. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian

Re: IP Forwarding to Windows machine

On Sun, Aug 10, 2014 at 4:30 PM, Joe wrote: > On Sun, 10 Aug 2014 16:07:01 -0400 > Tom H wrote: >> On Sun, Aug 10, 2014 at 2:24 PM, Nemeth Gyorgy >> wrote: >>> 2014-08-10 11:33 keltezéssel, Pascal Hambourg írta: sysctl -w net.ipv4.ip_forward=1 iptables -t nat -P ACCEPT iptabl

  1   2   3   4   5   6   7   8   9   >