Dear Lonny,
Thanks very much for responding. I'm sorry it's taken me a little while
to reply - I haven't actually received any emails from the mailing list!
I've change my settings to get all emails, rather than the daily digest,
let's hope that fixes it. I found your response on the mailing list website.
Thanks for telling me about tcpdump. Here's the output whilst the phone
is booting. The AstLinux server is 192.168.1.3, my desktop PC is
192.168.1.2 (which I've excluded as I'm running PuTTY from it) and the
phone is 192.168.1.12:
swm-pbx ~ # tcpdump -n -e 'host (192.168.1.3 or 192.168.1.12) and not
192.168.1.2'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
17:01:09.509007 00:50:7f:e4:21:08 > ff:ff:ff:ff:ff:ff, ethertype ARP
(0x0806), length 60: Request who-has 192.168.1.12 tell 192.168.1.1,
length 46
17:01:12.509986 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.12 tell 0.0.0.0, length 42
17:01:13.009867 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.12 tell 192.168.1.12, length 42
17:01:13.672863 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.3 tell 192.168.1.12, length 42
17:01:15.668643 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.3 tell 192.168.1.12, length 42
17:01:17.668695 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.3 tell 192.168.1.12, length 42
17:01:19.668776 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.3 tell 192.168.1.12, length 42
17:01:21.668849 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.3 tell 192.168.1.12, length 42
17:01:54.105594 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.12 tell 0.0.0.0, length 42
17:01:54.608034 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Reply 192.168.1.12
is-at 00:04:f2:25:e7:27, length 42
17:01:54.609002 00:04:f2:25:e7:27 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 60: vlan 12, p 0, ethertype ARP, Request who-has
192.168.1.12 tell 192.168.1.12, length 42
I then tried to ping the phone from the AstLinux server:
17:03:34.339498 00:01:80:66:cd:cc > ff:ff:ff:ff:ff:ff, ethertype ARP
(0x0806), length 42: Request who-has 192.168.1.12 tell 192.168.1.3,
length 28
17:03:34.339991 00:04:f2:25:e7:27 > 00:01:80:66:cd:cc, ethertype 802.1Q
(0x8100), length 68: vlan 12, p 2, ethertype ARP, Reply 192.168.1.12
is-at 00:04:f2:25:e7:27, length 50
17:03:35.342383 00:01:80:66:cd:cc > ff:ff:ff:ff:ff:ff, ethertype ARP
(0x0806), length 42: Request who-has 192.168.1.12 tell 192.168.1.3,
length 28
17:03:35.342783 00:04:f2:25:e7:27 > 00:01:80:66:cd:cc, ethertype 802.1Q
(0x8100), length 68: vlan 12, p 2, ethertype ARP, Reply 192.168.1.12
is-at 00:04:f2:25:e7:27, length 50
17:03:36.344382 00:01:80:66:cd:cc > ff:ff:ff:ff:ff:ff, ethertype ARP
(0x0806), length 42: Request who-has 192.168.1.12 tell 192.168.1.3,
length 28
17:03:36.344785 00:04:f2:25:e7:27 > 00:01:80:66:cd:cc, ethertype 802.1Q
(0x8100), length 68: vlan 12, p 2, ethertype ARP, Reply 192.168.1.12
is-at 00:04:f2:25:e7:27, length 50
So it looks to me as though, for whatever reason, my AstLinux server is
ignoring ARP requests from the phone and then also ignoring ARP
responses from the phone. Or have I accidentally excluded some packets
with my criteria?
I haven't used VLANs before. That doesn't mean I can't now! Won't I
still have the same problem as above?
My network setup is as follows - hopefully the ASCII art will be
faithfully rendered by the mailing list:
Wireless Access Point Router
192.168.1.9 192.168.1.1
| |
| |
Netgear FS726TP PoE Switch --------- Netgear GS724T Switch ---------
Netgear GS110TP PoE Switch
| | | |
| | | |
PolyCom SoundPoint IP 330 Phone AstLinux Server Desktop
PC Another phone
192.168.1.12 (dynamic IP) 192.168.1.3 192.168.1.2
eventually
(Total of 4 phones eventually)
Best wishes,
Nick
> Hi Nick,
>
> This could well be a basic networking issue as you stated...
>
> Personally, if you have a single interface AstLinux box I would generally
> recommend using VLAN's for the phones behind AstLinux so the AstLinux DHCP
> server is used to configure the IP Phones. If you do not have a managed
> switch that supports VLAN's, or are not comfortable with VLAN's, then we have
> to go back to the basics. But with VLAN's your AstLinux box with one
> interface can be viewed as a "router-on-a-stick" where the untagged packets
> (ex. eth0) act as the external interface connected to your private network
> and your phones can be configured as an internal interface on AstLinux using
> a VLAN (ex. eth0.20). The phones often use a PoE switch, separate from your
> main switch, which can manage all the internal VLAN interfaces AstLinux can
> provide. You may also want a data VLAN (ex. eth0.10). Each VLAN interface
> would be a unique private network.
>
> Note: If you have not used VLAN's before, you don't have to use them, and
> getting your head around using VLAN's can be tricky at first.
>
> Can you provide your basic network layout, ASCII drawings are fine. Showing
> the private IP address can be helpful as well.
>
> Given the single interface, my hunch is the AstLinux external interface is on
> the same private subnet as your IP phones, and the DHCP server is not
> AstLinux but rather some upstream router and your problems begin there.
>
> Tip: rather than using wireshark,
> "tcpdump"https://danielmiessler.com/study/tcpdump/ is available on AstLinux,
> a worthy skill to have.
>
> Lonnie
>
>
> On Oct 18, 2015, at 11:26 AM, Nicholas Mace <nick@...> wrote:
>
> > Hello. I'm having a problem setting up an AstLinux server and I would be
> > very grateful if anyone out there could help. To be honest, I think my
> > problem is a basic networking issue but I thought I'd start with this
> > mailing list.
> >
> > I have some PolyCom SoundPoint IP 330 phones. When I plug them in, they
> > successfully get an IP address from my router and they certainly appear
> > to receive DHCP option 66 to point them to the AstLinux server, but they
> > fail to connect to the server. I can browse to the phone's webpage from
> > my desktop PC (Windows 7) and I can ping the phones from my desktop PC.
> > I've tried pinging and wget from the AstLinux server, but I get nothing.
> > The arp table shows:
> > ? (192.168.1.12) at <incomplete> on eth0
> > I'm doing all this through shh (PuTTY) running on my desktop PC, so my
> > desktop can connect to the AstLinux server. My AstLinux server can
> > successfully ping both my desktop PC, my wireless access point and the
> > BBC website. I've used Wireshark on my desktop to watch the arp packets:
> > the AstLinux server certainly sends the request; I can't see the
> > response, but that's presumably because the switch sends it out only on
> > the port that the AstLinux server is connected to.
> >
> > The AstLinux server is built from a low-power Core 2 Duo micro-ATX board
> > with networking integrated into the chipset. There's only 1 ethernet
> > port. I had to manually enable the sky module to get networking going
> > initially.
> >
> > Anyone got any ideas? Many thanks.
> >
> > Nick
------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
