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 <n...@swm.me.uk> 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.

Reply via email to