> On 7 Nov 2021, at 17:11, Sam Varshavchik wrote:
>
> I wrote:
>
>> I upgraded a dual-homed server: one connection to the Internet, one
>> connection to my LAN (all IPV4 connections):
>>
>> NAT is no longer working:
>>
>> $ traceroute 8.8.8.8
>> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max,
On 08/11/2021 01:11, Sam Varshavchik wrote:
I wrote:
I upgraded a dual-homed server: one connection to the Internet, one connection
to my LAN (all IPV4 connections):
NAT is no longer working:
$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 shorty.email-s
On Sun, Nov 07, 2021 at 04:31:41PM -0500, Sam Varshavchik wrote:
> Matthew Miller writes:
>
> >On Sun, Nov 07, 2021 at 12:11:18PM -0500, Sam Varshavchik wrote:
> >> I don't see this listed under "Common Issues". I think it should be.
> >
> >To nominate a bug for Common Issues (in the Fedora bugzil
Matthew Miller writes:
On Sun, Nov 07, 2021 at 12:11:18PM -0500, Sam Varshavchik wrote:
> I don't see this listed under "Common Issues". I think it should be.
To nominate a bug for Common Issues (in the Fedora bugzilla at
bugzilla.redhat.com), add the "CommonIssues" keyword and QA will triage i
On Sun, Nov 07, 2021 at 12:11:18PM -0500, Sam Varshavchik wrote:
> I don't see this listed under "Common Issues". I think it should be.
To nominate a bug for Common Issues (in the Fedora bugzilla at
bugzilla.redhat.com), add the "CommonIssues" keyword and QA will triage it.
Or follow the procedure
I wrote:
I upgraded a dual-homed server: one connection to the Internet, one
connection to my LAN (all IPV4 connections):
NAT is no longer working:
$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 shorty.email-scan.com (192.168.0.1) 1.882 ms 1.818 ms 1
