Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #256999
| From | Tim Woodall <debianuser@woodall.me.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: ICMP router advertisement (ipv4) |
| Date | 2023-04-10 07:00 +0200 |
| Message-ID | <GiRNf-10Ii-1@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <GiF9n-SNn-9@gated-at.bofh.it> <GiJ3j-VdJ-3@gated-at.bofh.it> <GiQ4N-ZH6-1@gated-at.bofh.it> <GiQet-ZMb-5@gated-at.bofh.it> <GiRDz-10EH-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 10 Apr 2023, Tim Woodall wrote: > On Mon, 10 Apr 2023, Jeremy Ardley wrote: > >> >> On 10/4/23 11:02, Tim Woodall wrote: >>> My firewall has a single /128 acquired via SLAAC and the RA from the >>> router. My entire network is masqueraded through that single IP. >>> >>> >> What does the RA contain? Typically on connection to an IPv6 capable ISP >> you will get assigned a single /128 from their range and granted a complete >> routable range at least /64 for you to use. >> >> The interface between the router and the ISP will typically use the router >> fe80 to connect upstream but it will also have the /128 to use. The router >> should be able to route the /64 without NAT. If it can't then time for a >> new router. >> >> > > I want to be able to put a firewall in front of the router. But there's > no way to get any traffic out of the router and into my network other > than that addressed to my firewalls /128 > > The router doesn't even attempt to see if a host exists if a packet to a > new ip arrives. And it doesn't forward packets from new ips either, it just silently drops them. I don't know how the router learns ips but I suspect it's something to do with DAD,
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-09 09:40 +0200
Re: ICMP router advertisement (ipv4) Michel Verdier <mv524@free.fr> - 2023-04-09 10:40 +0200
Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-09 17:30 +0200
Re: ICMP router advertisement (ipv4) Michel Verdier <mv524@free.fr> - 2023-04-09 21:40 +0200
Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 05:10 +0200
Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-10 05:20 +0200
Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 06:50 +0200
Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-10 07:00 +0200
Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 20:30 +0200
Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-11 00:40 +0200
Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-11 05:50 +0200
Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-11 06:10 +0200
Re: ICMP router advertisement (ipv4) debian-user@howorth.org.uk - 2023-04-11 10:30 +0200
Re: ICMP router advertisement (ipv4) Anssi Saari <as@sci.fi> - 2023-04-11 13:30 +0200
Re: ICMP router advertisement (ipv4) Dan Ritter <dsr@randomstring.org> - 2023-04-11 15:50 +0200
Re: ICMP router advertisement (ipv4) Anssi Saari <as@sci.fi> - 2023-04-12 08:50 +0200
Re: ICMP router advertisement (ipv4) Dan Ritter <dsr@randomstring.org> - 2023-04-12 12:40 +0200
Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 07:00 +0200
csiph-web